web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Dual-write Initial Sync Warning : Max lookup count

(0) ShareShare
ReportReport
Posted on by 901

Hi guys,

While Initial Sync Dual-Write from F&O to Dataverse, I got this message :

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

I noticed the warning also include an advice to look for Microsoft Docs -> To fix the issue refer to https://docs.microsoft.com/en-us/powerapps/developer/data-platform/webapi/retrieve-related-entities-query

But sadly, I don't know what is the meaning of all that. Not sure what to do after that.

Would you mind to explain a bit what is that all about and how to resolve it ?

I have the same question (0)
  • WillWU Profile Picture
    22,361 on at

    Hi Tony,

    This issue seems to be related to a limitation of Dataverse, suggest you to go to the Power Apps forum for more help:

    powerusers.microsoft.com/.../PowerApps1

  • Suggested answer
    TracyXing Profile Picture
    on at

    There is a workaround:

    Split the initial sync in to 3 steps.

    In the first step, remove some of the lookup fields from the dual-write entity map that are not mandatory and bring the number of lookups to 10. Once the lookup fields are removed, save the map and do the initial sync. Once the initial sync for the first step is successful, add the remaining lookup fields and remove the lookup fields that got initial synced in first step. Once again make sure the number of lookup fields is 10. Save the map and run the initial sync. Repeat these steps to make sure all the lookup fields are initial synced. Now add all the lookup fields back to the map, save the map and run the map with skip initial sync. This will enable the map for live sync mode.

  • Tony zhong Profile Picture
    901 on at

    Hi Tracy,

    This is sound like a great idea. I would like to do that. But first may I know, in the last step you're mentioned, how to change Master to initial Sync to Finance and Operation, because normally it is defaulted to Dataverse, and I should click Initial sync in order to change it to FinOps.

    pastedimage1627552687350v1.png

    Thanks

  • Suggested answer
    TracyXing Profile Picture
    on at

    The last step means just skip initial sync and make the dual write entity is running, as we have done initial sync in previous steps.   Master to initial Sync is just a setting for initial sync.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 451 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 428 Super User 2025 Season 2

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 239 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans