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

Announcements

Introducing our New Video Series: Community Spotlight
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / AX2012 R2 LogisticsEle...
Microsoft Dynamics AX (Archived)

AX2012 R2 LogisticsElectronicAddress ValidFrom and ValidTo deprecated

(0) ShareShare
ReportReport
Posted on by Sven Joos 811
Hi, can anyone tell me why the validFrom and ValidTo fields were made DEL_ fields on the LogisticsElectronicAddress table since R2? This has a direct impact on our customers who used this functionality to have history on the electronic address data of a party. In addition, on the LogisticsPostalAddress table these fields still exist, so this is not consistent with the LogisticsElectronicAddress Table. Kr, Sven

*This post is locked for comments

I have the same question (0)
  • cmossell Profile Picture
    cmossell Microsoft Employee on at

    These changes were made as part of the address book performance enhancements in R2. If you elaborate on the specific requirements, I'd be happy to help find a solution to the issue.

    Chris

  • Sven Joos Profile Picture
    Sven Joos 811 on at

    Hi Chris,

    in the past, because the LogisticsElectronicAddress was a date-effective table, users could see the previous value of e.g. a party's email-address (and during which period that e-mail address was valid). With the disappearance of the validFrom and validTo, this is no longer possible. It can be very interesting for a company to see the previous e-mail, phonenumber of their customers.

    What I do not understand is why this was changed because the LogisticsPostalAddress table is still a date-effective table. A bit hard to explain this change to someone, since on one address table it is disappeared and on the other it still exists.

    So, as I understand, we might have to implement ourselves some "history" on the data of LogisticsElectronicAddress since I have the feeling Microsoft will probably not consider reversing this change on the LogisticsElectronicAddress table?. We can do that in multiple ways, that is not the problem, it is just a petty that this functionality disappeared from standard AX.

    Possible solutions:

    - activate database logging on this table, but viewing the history of this data using this tool doesn't seem very user-friendly and on top of that, database logging brings down performance.

    - implement ourselves again the date-effective framework on this table

    - create a "history" table and upon each insert/update/delete on LogisticsElectronicAddress write data to the "history" table

    - get a fix from Microsoft? :-)

    Kr,

    Sven

  • cmossell Profile Picture
    cmossell Microsoft Employee on at

    Sven,

    I think the best option is to create a history table, and log changes there. It would be the most surgical change and least likely to interfere with anything else.

    Chris

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

News and Announcements

Introducing our New Video Series: Community Spotlight

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Sanhthosh.Kumar.K Profile Picture

Sanhthosh.Kumar.K 2

#2
Raed Salah Bzour Profile Picture

Raed Salah Bzour 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans