duplicate records in SF to D365 import

  • 51Views
  • Last Post 04 August 2021
Jim Huebner posted this 30 July 2021

We have configured Salesforce to D365 packages and after several weeks of effort are still receiving numerous errors, from timeouts, to duplicates, etc. We have a go-live scheduled in 3 weeks, but have been plagued by errors, even after tremendously simplifying the tasks and packages. 

We were hoping to create a single migration package as per the SF - D365 Gallery example. However, due to errors and timeouts, we've had to break out each entity into a separate package, and are still getting errors, duplicates, and timeouts. The total records per table are ypically only about 5-15K, except for products table of ~76K which has run successfully. Our experience with Skyview has not been exceptional. We're wondering how we can improve our experience. We're using the new runtime. Would the old runtime be more reliable?

We have configured a D365 field as a SFId which persists the SF record ID for ongoing upserts according to the example in your documentation. This seems to work for most entities, but we've had numerous instances where thousands of duplicates are created. These are created both on initial runs (no existing D365 records) as well as updates to existing records.

Another issue is that upon failure there's no log of succesful records even tho we can see they've been created.

For example, we've tried several runs on "Opportunities". 

- 63577429 failed after 3+ hours with a 401 error. We are not experiencing this across the board...Accounts general run fine, although we've had duplicates once. Campaigns are fine. Contacts ran fine one time, then ongoing errors of various sorts. So the timeout errors are very random. Some jobs can run for 16 hrs, some timeout after only 2 hrs.

- 63605194 I believe created about 3K records, and failed after less than 3 hours with

An error occurred while receiving the HTTP response to https://udtd365.crm.dynamics.com/XRMServices/2011/Organization.svc/web. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.

- 63636955 is still running after several hours, creating 16,857 entries, with 13878 duplicates and only 993 unique records. 

Olena Romanchuk posted this 04 August 2021

Hello Jim, 

We have replied to your by email.
Should you have any questions, please contact us.