Microsoft Dynamics 365 | Integration, Dataverse...

Dual-Write - Empty Lookup field - Null

(6) Share

Report

Posted on by Y_A

447

Hi all,

I have an F&O (FSCM) environment and a D365 Sales (Dataverse) environment linked with Dual Write.

The Accounts table in Dataverse and the Customers table in FO are syncing to each other via DW.

In both Dataverse and FO, I have a custom table called Mandates which is also synced via Dual Write.

In the Accounts Table, I have a look up field called Mandate ID which is a a look up to the mandates table. The same is in FO in the customer card.

When the mandate field in the customer record in FO is updated (i.e. assign it a value the first time or update the value of the field), DW works well i.e. the change is successfully reflected in dataverse.

The problem is when the mandate field in the customer in FO has a value and the user blanks it out i.e. clears the value of the field. This change is not being reflected in Dataverse via DW.

How can we pass a null value via DW in order to clear out (empty) the field in the Dataverse record (Account)?

Any help would be greatly appreciated!

Thanks in advance!

Categories:

Dynamics 365 general

Power Platform integration

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

ArchitectMadhan 458 on at

Like (0)

Report
Copy link

Link copied!
Hi,

This issues seems to be common, but please check whether you are following the below steps:

Check Dual Write Mapping: Ensure that the field mappings between Dynamics 365 F&O and Dataverse are correctly set up to handle null values. You might need to adjust the mapping settings to allow null values to be synchronized.

Modify Data Events: In some cases, you may need to modify the data events in Dynamics 365 F&O to explicitly handle null values. This can involve customizing the data entity to ensure that null values are correctly passed through the integration.

Use Custom Logic: Implement custom logic in the Dual Write integration to handle null values. This can be done by creating a custom plugin or workflow in Dataverse that listens for changes and updates the corresponding field to null when necessary.

Review Error Logs: Check the Dual Write error logs to see if there are any errors or warnings related to the null value synchronization. This can provide insights into what might be going wrong and help you troubleshoot the issue.

Consult Documentation: Refer to the official Dual Write documentation for detailed guidance on handling null values and other synchronization scenarios

If you find this solution useful, please like it and accept it as answer.

-ArchitectMadhan

Was this reply helpful? Yes No
DGA205 61 on at

Like (0)

Report
Copy link

Link copied!

Hi, I have the same issue. When the field is nulled in FO, in Dataverse ignore the change.

For the point 1, where I might need to adjust the mapping settings to allow null values to be synchronized??

Was this reply helpful? Yes No
Bilal Hussain 67 on at

Like (0)

Report
Copy link

Link copied!

@DGA205 did you manage to resolve it? we are having the similar problem and would like to see how did you fix it?

Was this reply helpful? Yes No