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 / Microsoft Dynamics AX (Archived) / Change Tracking on SQL...
Microsoft Dynamics AX (Archived)

Change Tracking on SQL with AX and AX synchronization

(0) ShareShare
ReportReport
Posted on by PA-22040759-0 6,194

I have been told two facts about change tracking which I have a bit of a hard time fully believing, or understanding if you will.

  1. When synchronizing AX, the change trackings settings on SQL is cancelled and you have to reapply these.
  2. Because the change tracking settings are cancelled, all recorded changes are lost.

Can anyone with Change Tracking experience in connection with AX verify these claims? If the second claim is correct, how do you ensure that for example Master Data Management has syncronized all changes before this happens?

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    Hi,

    I'm not very familiar with Master Data Management but we have several environments with Management Reporter 2012 that is also using SQl Server Change Tracking. We synchronize Data Dictionary each time when we bring new release and neither the tracking settings were cancelled nor the change history was lost. 

    Even after the warning "An action you have taken requires that one or more fields be dropped from the Microsoft Dynamics AX database...." during the synchronization - the change tracking for that table was fine.

  • PA-22040759-0 Profile Picture
    PA-22040759-0 6,194 on at

    Thanks Oleg,

    What I have been told is that a syncronization sometimes copies data of a table, drops the table and then recreates the table. In that case I'm told that you'll loose the Change Tracking setup. And as I understand, Management Reporter has code to set this up by itself again.

    Thanks,

    Palle

  • Verified answer
    Community Member Profile Picture
    Community Member on at

    Hi,

    In my experience, synchronization only drops tables in case of the Object ID conflicts or renaming/changing the base type of an existing table field (see "The action you have taken will drop and re-create the table ... and all associated index. This can be caused by renaming a field or changing the type and/or size of the field." in SQLSyncInfo table).

    Regarding the Management Reporter - it does not automatically restore change tracking settings if they were lost. Administrator has to do that "manually" by clicking "Reconfigure change tracking" in the management console.

  • PA-22040759-0 Profile Picture
    PA-22040759-0 6,194 on at

    Thank you, Oleg.

    That answers my questions.

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 > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans