Skip to main content

Notifications

Finance | Project Operations, Human Resources, ...
Unanswered

ProjTable to LogisticsPostalAddress relation bug? in ProjTable form related to sysrowversionnummber field

(0) ShareShare
ReportReport
Posted on by 15

Okay this is a strange one. I'm not 100% certain I'm right but I really cannot find any other cause of this issue.

This bug is occurring on our sandbox environment. Essentially all addresses related to projects that were created before we upgraded to 10.0.31 no longer display. I got access to the sandbox database and I can confirm that the LogisticsPostalAddress record still exists, the data for the deliverylocation field within the projtable still exists for all of the records, and the relations still match up. I went as far as configuring my dev environment to access the sandbox database and follow the code and for whatever reason it doesn't find the related address records. The only thing I've been able to find is this.

pastedimage1678714550594v1.png

The above snippet is just data from the database joining the projtable to the logisticspostaladdress table, the sysrowversionnumber listed there is for the logisticspostaladdress records. Any projtable record that is related to a an address record with the sysrowversionnumber of 0x does not display or relate in the form, however any combinations that do have data listed in that column do work. 

Other relative information. Our sandbox has been setup for awhile now and we have yet to go into production. I don't know if that could be a factor here. My dev environment which was provisioned about 2 months before the 10.0.31 patch does not have this problem, the data that exists there has valid sysrowversionnumbers even though that data was sourced from the sandbox environment.

Does anyone have any idea what could be happening here? 

Thank you,

  • Samuel Roberts Profile Picture
    Samuel Roberts 15 on at
    RE: ProjTable to LogisticsPostalAddress relation bug? in ProjTable form related to sysrowversionnummber field

    Okay I just confirmed the issue. I did an SQL update to one of the "broken" logistics address records by changing its location to itself, causing an update to the record. It now has a SYSROWVERSIONNUMBER value and when I look up the project record it now relates and is visible when all previous tests it was not working.

    If anyone has any information about why this might be happening or any reassurance that something like this would not happen in production I'd appreciate it because this big of a data issue is really scary for someone transitioning to D365.

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

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Vahid Ghafarpour – Community Spotlight

We are excited to recognize Vahid Ghafarpour as our February 2025 Community…

Congratulations to the January Top 10 leaders!

Check out the January community rock stars...

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,074 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 230,900 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans