Microsoft Dynamics 365 | Integration, Dataverse...

Couldn't resolve the guid for the field: msdyn_paymentdayname.msdyn_name

(3) Share

Report

Posted on by PS-30051345-0

Hi community,

I ran the terms of payment entity with initial sync in dual write, and I got this warning: Couldn't resolve the guid for the field: msdyn_paymentdayname.msdyn_name. The lookup value was not found: 15th. Lookup parententity: msdyn_paymentdays, lookup result: .. Try this URL(s) to check if the reference data exists: https://org21c47333.crm.dynamics.com/api/data/v9.0/msdyn_paymentdays?$select=msdyn_name,msdyn_paymentdayid&$filter=msdyn_name eq '15th'
I already ran related table payment schedule and payment day with initial sync from finance and operations

Is there any way to fix it?

Categories:

Dynamics 365 general

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

André Arnaud de Cal... 303,674 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,

There can be two root causes for this issue. Either it is a table permissions issue or the initial sync is executed in the wrong order, where the payment days aren't synced yet. The field value has a dependency on a related table.

Was this reply helpful? Yes No
Suggested answer

Aymen CHELBI 586 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!
Hello,

Based on Microsoft’s guidance for similar cases (such as Vendors V2 and Customers V3 circular/self-referencing lookups), here is the procedure that fixed the issue: Troubleshoot issues during initial synchronization - Finance & Operations | Dynamics 365 | Microsoft Learn

Open the Terms of Payment dual-write mapping.

On the Table mappings tab, delete the PaymentDayName / msdyn_paymentdayname lookup column from the mapping.

Save the mapping.

In Finance and Operations, go to Data management > Data tables, select the Terms of Payment table, and disable Change Tracking.

Run the initial sync for the Terms of Payment mapping. It should complete successfully without lookup errors.

Add the PaymentDayName / msdyn_paymentdayname column back to the mapping and save.

Run the initial sync again so that the lookup value is correctly synchronized now that the reference data exists in Dataverse.

Re-enable Change Tracking for the Terms of Payment table.

After following these steps, the lookup value “15th” was correctly resolved and the initial synchronization completed successfully.

I hope this helps anyone facing the same issue.

Kind regards.

Was this reply helpful? Yes No