Monsieur Winner

MS D365FO || Monsieur D365FO

Technical

Warning:[DWCE0001] Export was skipped. Max lookup count supported in Initial Sync stage is 10. Current lookup count 11.

Via dual write, while copying data from the Dataverse to Dynamics 365FO via initial sync and I go this error:

 

Warning:[DWCE0001] Export was skipped. Max lookup count supported in Initial Sync stage is 10. Current lookup count 11. Lookup fields:

transactioncurrencyid.isocurrencycode,

msdyn_customergroupid.msdyn_groupid,

msdyn_billingaccount.accountnumber,

msdyn_paymentday.msdyn_name,

msdyn_customerpaymentmethod.msdyn_name,

msdyn_paymentschedule.msdyn_name,

msdyn_paymentterm.msdyn_name,

msdyn_vendor.msdyn_vendoraccountnumber,

primarycontactid.msdyn_contactpersonid,

msdyn_salestaxgroup.msdyn_name,

msdyn_company.cdm_companycode.

To fix the issue refer to https://docs.microsoft.com/en-us/powerapps/developer/data-platform/webapi/retrieve-related-entities-query

 

After few checks here and there, it turns out that, there is a limitation when copying data from Dataverse. The entity must not have a table map lookups more than 10 as stated on MS Learn

 

Resolution:

Like the error message says, we need to remove one mapping ( a non-mandatory one). So what I did was to delete the Payment day mapping, did initial Sync successfully then re-added the field mapping.

 

 

 

Komi Siabi

Komi Siabi is a Bilingual D365FO Solution architect who loves sharing his knowledge as he works on Both Francophone and Anglophone projects around the globe. He enjoys doing some tiktok videos in his leisure time.

0 thoughts on “Warning:[DWCE0001] Export was skipped. Max lookup count supported in Initial Sync stage is 10. Current lookup count 11.

  • Your comment is awaiting moderation.

    Exceptional post however , I was wondering if you could write a litte more on this topic? I’d be very grateful if you could elaborate a little bit further. Cheers!

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *