Skip to main content

Change tracking [AX 2013 R3]

I came across this last week

Great blog post talking about change tracking in AX 2012 R3. I decided to give it a go and see how to leverage it for an integration project I am working on.

When you run the first job, you enable database tracking. In here you can define a retention period and if it should clean up automatically.


The next piece is to enable change tracking on the table.


Related tables get triggers to update the parent to tell it there was a change.


A change tracking version is maintained in AX. Every time you reset a new version is inserted.


If you run a basic select statement to see what is in change control. Below is the result.

JOIN dbo.VendTable c ON c.AccountNum = ct.AccountNum;


When you run the last job – returns a result set. This is actually a sql query that is run.


JOIN dbo.VendTable c ON c.AccountNum = ct.AccountNum;

declare @end_version bigint;
select @end_version = CHANGE_TRACKING_CURRENT_VERSION();

declare @begin_version bigint;
select @begin_version = 882;

if @begin_version is not null
declare @begin_version_VendTable bigint;
if (@begin_version is null or @begin_version < CHANGE_TRACKING_MIN_VALID_VERSION(OBJECT_ID('VENDTABLE')))
    select @begin_version = null;
    select @begin_version_VendTable = @begin_version;
if @begin_version is not null
insert into tempdb.dbo.t100025_6711C773064A4E3B93D08755E1C0E948(KEYFIELD_RECID, ChangeOperation, ChangeVersion, ChangedTableId)
select [VendTable_1 PhysicalTable].RECID, SYS_CHANGE_OPERATION as ChangeOperation, SYS_CHANGE_VERSION as ChangeVersion, 505 as ChangedTableId
from CHANGETABLE(CHANGES VENDTABLE, @begin_version_VendTable) as VendTable_1
    join VENDTABLE as [VendTable_1 PhysicalTable] on  [VendTable_1 PhysicalTable].ACCOUNTNUM = VendTable_1.ACCOUNTNUM  and [VendTable_1 PhysicalTable].DataAreaId = VendTable_1.DataAreaId
    where VendTable_1.SYS_CHANGE_OPERATION <> 'D'

/select * from tempdb.dbo.t100025_6711C773064A4E3B93D08755E1C0E948

Popular posts from this blog

AX - How to use Map and MapEnumerator

Similar to Set class, Map class allows you to associate one value (the key) with another value. Both the key and value can be any valid X++ type, including objects. The types of the key and the value are specified in the declaration of the map. The way in which maps are implemented means that access to the values is very fast. Below is a sample code that sets and retrieves values from a map. static void checkItemNameAliasDuplicate(Args _args) { inventTable inventTable; Map map; MapEnumerator mapEnumerator; NameAlias nameAlias; int counter = 0; ; map = new Map(Types::String, Types::Integer); //store into map while select inventTable { nameAlias = inventTable.NameAlias; if (!map.exists(nameAlias)) { map.insert(nameAlias, 1); } else { map.insert(nameAlias, map.lookup(nameAlias) + 1); } } //retrieve fro

AX - How to use Set and SetEnumerator

The Set class is used for the storage and retrieval of data from a collection in which the values of the elements contained are unique and serve as the key values according to which the data is automatically ordered. You can create a set of primitive data types or complex data types such as a Class, Record or Container. Below is sample of a set of records. static void _Set(Args _args) {     CustTable       custTable;     Set             set = new Set(Types::Record);     SetEnumerator   setEnumerator;     ;     while select custTable     {         if (custTable && !         {             set.add(custTable);         }     }     if (!set.empty())     {         setEnumerator = set.getEnumerator();         setEnumerator.reset();         while (setEnumerator.moveNext())         {             custTable = setEnumerator.current();             info(strfmt("Customer: %1",custTable.AccountNum));         }     } } Common mistake when creating a set of recIds

Import document handling (attachment) files #MSDyn365FO

Out of the box you have limited data entities for migrating attachments. If you search what is already in the AOT, you will see a few various examples. I suggest you look at the LedgerJournalAttachmentsEntity as it is the simplest and cleans to copy from. I wont go into detail but I will give a quick run down of what it looks like. Use the DocuRefEntity as your main datasource. It does most of the work for you. Set your table you want to import for as the child datasource Add the Key You will need to add the postLoad method. There is minor code to update the virtual field FileContents. Below is an export I did for the general journal attachments. The import zip structure should be the same way. It will create the usual artifacts such as the excel, manifest and package header xml files. You will see a Resources folder under that. If you drill down to the resources you will see the attachments. This is an export and it used the document GUID for uniqueness. The other thing is the extensi