Select to view content in your preferred language

SystemEndDate and SystemStartDate from Upgraded ArcMap fabric

157
2
Jump to solution
03-25-2025 12:28 PM
PhilipWeeks
Regular Contributor

I've been working on upgrading a parcel fabric from ArcMap to ArcPro and I've noticed two missing fields in the new ArcPro Fabric, SystemEndDate and SystemStartDate.  The Legal Start and End Dates transferred and while some queries which relied on SystemEndDate Is Not Null can be done by checking RetiredByRecord, thee date itself is useful information as it represents when the action was taken in the system to retire or create a parcel and it seems strange the upgrade process would just drop this info.

All the retired records have the same placeholder ID, DDDD-DD-DDDDDD...etc...  I'm wondering if because plans weren't actively being used and this info would be in a related table, that's why it's lost, but I'm just guessing.

Is there any equivalent in the new ArcPro fabric to the SystemEndDate and SystemStartDate fields?  Are they maybe renamed or stored in another table somewhere?  Or if I do want this info so I have to manually copy them to a new field because the upgrade process is erasing data in system maintained fields?

1 Solution

Accepted Solutions
JasonCamerano
Esri Contributor

The system start and end date were removed as they were not accurately reflecting when a parcel was retired in the legal sense and are no longer used in the ArcGIS  Pro fabric.

And you are correct in regards of why retired parcels were associated to {DDDD....DDDD} globalID.  That is because in ArcMap there was no reliable way to determine which plan retired parcels.  There for a place holder was used to retire all the historic parcels.  

If you want to maintain the system start / end dates you can do what you suggested by copying the values over to another field.  Then it will be treated as an extended attribute and be copied over. 

View solution in original post

2 Replies
FrankConkling
Regular Contributor

For some clients, we have moved the SystemStartDate and SystemEndDate to the records feature class to reflect the documents' dates that caused the change.

While it might not be 100% accurate, especially if plans were not used in the ArcMap Parcel Fabric, you can use an arcade expression to traverse through the record to parcel relationship class and populate the fields in the record feature class.

Good Luck,

Frank Conkling - Panda Consulting

JasonCamerano
Esri Contributor

The system start and end date were removed as they were not accurately reflecting when a parcel was retired in the legal sense and are no longer used in the ArcGIS  Pro fabric.

And you are correct in regards of why retired parcels were associated to {DDDD....DDDD} globalID.  That is because in ArcMap there was no reliable way to determine which plan retired parcels.  There for a place holder was used to retire all the historic parcels.  

If you want to maintain the system start / end dates you can do what you suggested by copying the values over to another field.  Then it will be treated as an extended attribute and be copied over.