Dynamics Community Forum Thread Details

DirPartyTable recId question

Hi everyone. I came across a scenario which I was hoping someone could clarify for me.

I have a customer who recently changed their primary address information. The relationship I understand is CustTable (Party) > DirPartyTable (PrimaryAddressLocation) > LogisticsPostalAddress. I see multiple entries in LogisticsPostalAddress for this customer's old and new address and noted the recId's. On the customer detail form, the new and revised address is showing properly. However, when I pull up the customer's DirPartyTable record I see that the value in the PrimaryAddressLocation field still points to the old LogisticsPostalAddress recId. Can someone enlighten me on how AX manages primary address data, and possibly explain why DirPartyTable could be referencing a stale address recId? Thanks much!!!

Hi,

I assume your environment is normal and the following explaination is based on this assumption.

First of all, the PrimaryAddressLocation points to a LogisticsLocation record. The LogiticsPostalAddress records, on the other hand, have a field called "Location" which would contain the recId for this particular LogisticsLocation record.

So it should be DirPartyTable (PrimaryAddressLocation) -> LogisticsLocation <- LogisticsPostalAddress (Location)

There are multiple LogisticsPostalAddress records pointing to the same "Location" because LogisticsPostalAddress is a ValidTimeStateTable. (See msdn.microsoft.com/.../gg861781.aspx for more on ValidTimeState tables). The end result is only one LogisticsPostalAddress record is in effect at one point of time, which is why the correct address is being shown.

So, if your customer only changes the details of the existing Primary address record, the "PrimaryAddressLocation" in DirPartyTable would not change.

However, if your customer created another address and set the new address as Primary, then the PrimaryAddressLocation should change accordingly.

Regards

Quick Links

Leaderboard