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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

Clarification on Change Tracking at the Data Entity Level

(0) ShareShare
ReportReport
Posted on by 276

Hi team,

 

In Could you please explain a real-world scenario of how the change tracking mechanism works at the data entity level in D365FO?

 


Also, is change tracking used only for export operations, or can it be used in other scenarios as well?

 

Pls advise, thanks.

Categories:
  • Suggested answer
    Subra Profile Picture
    2,686 Super User 2026 Season 2 on at

    Hi @CU29091230-0 

    A real-world example is synchronizing customer data from D365FO to an external CRM system. Rather than exporting all 100,000 customers every night, the integration can retrieve only the customer records that were added, updated, or deleted since the previous synchronization.

    When you say about the export are you specific to DMF?

    Thanks,
    Subra

    If this helped, please mark it as "Verified" for others facing the same issue

     

  • CU29091230-0 Profile Picture
    276 on at

    Yes specific to DMF

     

    Is Incremental push and Change tracking both are working together?

     

    Pls advise thanks 

  • Suggested answer
    Subra Profile Picture
    2,686 Super User 2026 Season 2 on at

    Hi @CU29091230-0 

    I hope we have used only for export.

    Yes, both increment and change tracking that work together.

    Thanks,
    Subra

  • CU29091230-0 Profile Picture
    276 on at

    Hi Subra,

     

    As mentioned “ Rather than exporting all 100,000 customers every night, the integration can retrieve only the customer records that were added, updated, or deleted since the previous synchronization.”

     

    So, if I understand correctly, suppose that since the last synchronization, 

    5 new customers have been added, 

     

    3 customers have been deleted, and 

     

    20 existing customers have been updated.

     

     

    During the next customer export process, how many records would be processed by the change tracking mechanism?

     

     

    Could you please clarify how newly added, updated, and deleted records are handled in this scenario?

     

    Pls advise, thanks 

  • Subra Profile Picture
    2,686 Super User 2026 Season 2 on at

    Hi @CU29091230-0 

    Increment push will export all the new records (5) and updated records(20) for the deletion depends upon the configuration which has been used and it will export all the deletion records as well for the change tracking.

    Thanks,
    Subra

  • Verified answer
    Anitha Eswaran Profile Picture
    490 on at

    In the above case, 20 updated customers/ 5 new customers/ 3 deleted customers will be included if you are exporting. Note that the record deletion is tracked only for the root datasource in the entity. 

  • CU29091230-0 Profile Picture
    276 on at

    Sorry Anitha, the deletion part I not understand.

     

    Could you please elaborate. thanks

  • CU29091230-0 Profile Picture
    276 on at

    Thanks Daniel.

     

    But sorry not understand. Still confused..

     

  • CU29091230-0 Profile Picture
    276 on at

    Hi all,

     

    I do researched and posted the scenario based on the above example. 

     

    I would like to focus on two change tracking options in D365FO: Primary table and Entire entity.

     

     

    1. Change tracking set to “Primary table”

    Scenario 1: Initial export Suppose I have 100 customer records and no previous export has been performed. The initial export will include all 100 customers.

     

     

    Scenario 2: New customers added Suppose I add 5 new customers after the initial export. During the second export, change tracking will identify and export only those 5 new customer records.

     

    Scenario 3: Customer addresses updated Suppose I update the addresses of 3 customers. Since the address information is stored in a separate table, LogisticsPostalAddress these changes will not be tracked when change tracking is configured for the primary table, provided the address table is not the entity's primary data source.

     

     

    2. Change tracking set to “Entire entity”

    In this case, change tracking considers changes across the entity's relevant data sources.

     

     

    Scenario 1: New customers and address updates Suppose that after the initial export:

    • 5 new customers are added.

    • The addresses of 20 existing customers are updated.

     

    During the next export, change tracking should identify the 5 new customers and the 20 customers whose addresses have changed both.

     

     

    My understanding is that if we select “Entire entity” instead of “Primary table” as the change tracking system, both newly inserted records and updated records across the relevant data sources of the entity will be identified during the next export.

     

     

    ***I will discuss the deletion scenario separately.

     

     

    Could you please confirm whether my understanding of these two change tracking options is correct?

     

    Pls advise, thanks 

     

     

  • Verified answer
    Anitha Eswaran Profile Picture
    490 on at

    Your understanding is generally correct. But there is an important nuance regarding the ‘Entire entity’ - it does not automatically mean every table joined to the entity is tracked in all situations. It depends on whether the underlying table supports the CT, correct table relations in the entity, etc., So if you just add a table to the entity with incorrect or missing relation, the changes are not exported.

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

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

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

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 266 Super User 2026 Season 2

#2
Aayush Tiwari Profile Picture

Aayush Tiwari 217

#3
Subra Profile Picture

Subra 164 Super User 2026 Season 2

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans