Microsoft Dynamics 365 Blog

Although the use of “natural keys” in place of surrogate foreign keys in AIF is a documented design change in AX 2012, it seems there are still some questions around this functionality.

Per the documentation (…

The document services framework “..replaces a surrogate foreign key (SFK) with the natural key for a specific table


A simple example is the ContactForParty field in the DirContactPersonsService. This field in the ContactPerson table has an EDT of DirPartyRecId, but an error will occur if you attempt something like this…

AxdEntity_ContactPerson contactPerson = new AxdEntity_ContactPerson();

contactPerson.ContactForParty = dirpartyrecId;


This won’t work with a recId value, because the service will determine that ContactForParty is a surrogate foreign key and will look for the natural (replacement) key on DirPartyTable. The replacement key on DirPartyTable is PartyNumberIdx, so what we need to pass in via the service is the PartyNumber.

The concept seems pretty simple in this example, but it can become more complex when the replacement key is itself a surrogate foreign key. The WorkerSalesResponsible field in SalesTable is one such example.

  • WorkerSalesResponsible is a SFK referring to HcmWorker.
  • The HcmWorker table has a replacement key of Person (HcmWorker_AK1)
  • Person is itself a SFK referring to DirPerson.
  • DirPerson extends DirPartyTable, and the replacement key on DirPartyTable is again, PartyNumberIdx.
  • So we finally have the natural key we need. To import data into the WorkerSalesResponsible field via the SalesSalesOrderService we need to use a valid PartyNumber.


We're always looking for feedback and would like to hear from you. Please head to the Dynamics 365 Community to start a discussion, ask questions, and tell us what you think!