Upsert Operation Error

  • 58Views
  • Last Post 2 weeks ago
0
votes
brendan dunleavy posted this 3 weeks ago

I am trying to run the upsert operation in an import package to update data from Salesforce to MS Dynamics.

So I have specified a Target Lookup on the Id based on another unique field, as follows:

When I run the package I get an error saying: 

Package failed: The 'accountid' column has DbType 'String', which is different from the target column DbType 'Guid'.

Strange, since the data type I specified is the same field of type GUID.

Run ID: 125592225

 

Am I missing something? Kindly advise,

Thank you

Order By: Standard | Newest | Votes
0
votes
Serhii Muzyka posted this 3 weeks ago

 Hi,

 

Thank you for contacting Skyvia Support.

 

We just reproduced your situation and the error didn't repeat.

I will push this situation to our development team and will get back to you with the result soon.

At this moment, could you try to create a new package and run it again.

 

Let us know if the issue repeats.

 

Best regards,

Serhii

0
votes
brendan dunleavy posted this 2 weeks ago

I just re-ran the same package and the issue happend again.

If I clone as a new package, then won't I lose the date/time since the last run? I only need to upsert the changes since the last run.

Thanks.

 

0
votes
Serhii Muzyka posted this 2 weeks ago

Hi Brendan,

 

Thank you for your response.

 

Could you try to remove your mapping by changing to another object and then select it back as it was? Run your package and let us know the result.

 

Thank you in advance and looking forward to hearing from you.

 

Best regards,

Serhii

0
votes
brendan dunleavy posted this 2 weeks ago

Thanks for coming back to me.

I did as you have suggested and that seemed to run fine for 3 minutes showing success rows, but then the issue happened again during the run.

Run ID: 125944405

0
votes
Serhii Muzyka posted this 2 weeks ago

Hi,

 

Thank you for your response.

 

Could you please now create a new package and run it? With the new package, you will not lose the date/time since the last run of the main one. The Updated filter imports both records that were created and records that were modified since the previous package run. 

 

Let us know the result.

 

Thank you in advance and looking forward to hearing from you.

 

Best regards,

Serhii

0
votes
brendan dunleavy posted this 2 weeks ago

I cloned the package as you said and ran it, its says succesful, however 0 rows were imported.

I am sure that there were changes/new records at source since the last run 2 weeks ago.

Can you kindly advise?

Run ID: 126434624

Thanks

0
votes
Serhii Muzyka posted this 2 weeks ago

Hi,

Thank you for your response.

 

Please note that when you cloned your package, the Updated filter remained. The Updated filter imports both records that were created and records that were modified since the previous package run. 

 

Because your package wasn't executed before, you didn't get any rows. If you run your package now, you will get the records that were modified since the previous package ran(ID126434624).

We will investigate the error that happened in the old package and will try to fix it so it will not repeat in the future. At this time, we recommend using your cloned package. To get the missed data, please remove the filter, run your package, Upserting all the data, and after that, enable the Updated filter again.

 

 

Sorry for the inconvenience.

Should you have other questions, don't hesitate to reach out.

 

Best regards,

Serhii

0
votes
brendan dunleavy posted this 2 weeks ago

We already did a full migration with the old package, and that is what we need now ("Updated"), to upsert the changes only since the first run.

Preferably we'd like to avoid doing another full data migration run to resolve the upsert issue. This is because we have 5 other packages that complete the data migration and the total execution time was about 24 hours.

Thanks

 

 

 

0
votes
Serhii Muzyka posted this 2 weeks ago

Hi,

 

Thank you for your response.

 

The other option is to use the copy package, adding filtering by CreatedDate where the date will be the date your old package was run last. 

Please set up filters like shown on the screenshots and run your new package. Note: For this run, you have to remove Updated State Filter.

After this run, you can set the Updated state filter back and continue using your package as before.

 

 

We are really sorry for the inconvenience.

 

Should you have other questions, don't hesitate to reach out.

 

Best regards,

Serhii

Close