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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Dual-Write Change Trac...
Finance | Project Operations, Human Resources, ...
Answered

Dual-Write Change Tracking question

(0) ShareShare
ReportReport
Posted on by Volodymyr Pavlovskyi 65

Hi Community,

We have created a copy of SalesOrderHeaderV2Entity data entity. Also we added new field to CustTable NoYes type OROMappedToDataverse.

Data Entity only exports sales orders from the selected customers based on filter OROMappedToDataverse set to Yes.

I have mapped SalesOrderHeaderV2Entity in F&O to Dataverse using Dual-Write . 

We use change tracking here, when we add a new Sales Order Dataverse also adds that order to the Dataverse - so it works well.

But we have one problem : When we enable some old customer setting field OROMappedToDataverse system do not export all it related sales orders (which already exists in a system).

Even when CustTable is added in a defaultCT() method to the query of data entity system does not export already existed sales order when we enable new customer.

How can I trigger F&O to export old sales orders. 

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

    Hi partner,

    You could try using X++ code to update the old customer in batch.

  • AnithaEswaran Profile Picture
    AnithaEswaran 2,032 on at

    Hi Volodymyr ,

    In order to export data for dual write, there should be some trigger (changes) in the FO records, so the record is exported.

    Can you try 'initial Data sync' which brings the old records present in the system ?

    Also try adding a 'Query' to mention your filter field in Dual write mapping .

  • Verified answer
    Volodymyr Pavlovskyi Profile Picture
    Volodymyr Pavlovskyi 65 on at

    Problem is resolved.

    The issue was as I discribed: after initial sync DualWrite only process one record

    - either insert, delete, update (CRUD). If during Init-Sync system filtered out some records(for example we had some range in Query ) then we cannot get sync these record later.

    Let's say we added has some parameter in System Parameters - SalesStatus, we set it to Invoiced and only Invoiced sales orders ecported during Init-Sync.

    Later on if we decide to change our parameter from Invoiced to Delivered(for example) then nothing happens. Even if we change DefaultCT. Already existed sales order would never get exported.

    However I found the solution: we can call method ForceSyncRecordsToCDS from system class DualWriteOutbound , and provide a list of records from SalesTabke we want to force to sync.

    So when user changes paramere we tell the system to force export of all Delivered sale orders.

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

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

#1
Martin Dráb Profile Picture

Martin Dráb 664 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

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

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 303 User Group Leader

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans