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

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / DirPartyTable recId qu...
Microsoft Dynamics AX (Archived)

DirPartyTable recId question

(0) ShareShare
ReportReport
Posted on by bankk 6,603

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!!!

*This post is locked for comments

I have the same question (0)
  • Verified answer
    dolee Profile Picture
    dolee 11,279 on at
    RE: DirPartyTable recId question

    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

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…

Pallavi Phade – Community Spotlight

We are honored to recognize Pallavi Phade as our Community Spotlight honoree for…

Congratulations to the October Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Tocauer Profile Picture

Martin Tocauer 4

#2
AlissonGodoy Profile Picture

AlissonGodoy 2

#2
NNaumenko Profile Picture

NNaumenko 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans