topic Re: Branch version dirty area returns on reconcile. in ArcGIS Pro Questions

Branch version dirty area returns on reconcile.

Steve_Salas — Thu, 15 Jul 2021 14:18:37 GMT

Hello, I am new to branch versioning and I have created a topology in my data. In my test data/feature service, I have a fully validated topology in the Default version (no dirty areas).

In a child version, I made spatial edits that resulted in a dirty area. I validated the dirty area and saved. If I reconcile this version with Default, the dirty area returns.

I validate the dirty area again and save, no other edits made. And then I reconcile with Default again and the dirty area is back. There have been no other versions posted to Default during this time.

I don't recall this occurring in traditional versioning so is this expected in branch versioned editing? Or did I missing something when creating this? I think we are on enterprise 10.8.1 and I created the data using Pro 2.7.2... but have since upgraded to Pro 2.8.0 and this continues to occur if I retest those steps above.

Re: Branch version dirty area returns on reconcile.

jcarlson — Thu, 15 Jul 2021 14:27:00 GMT

We see the same behavior. We're still not sure why it's happening, but we work around this by simply doing all of the validating on the Default version.

Re: Branch version dirty area returns on reconcile.

Steve_Salas — Thu, 15 Jul 2021 14:50:50 GMT

Thanks @jcarlson - interesting indeed!

Re: Branch version dirty area returns on reconcile.

jcarlson — Thu, 15 Jul 2021 14:54:28 GMT

Someone else I discussed this with wondered if the act of posting edits was itself a kind of edit, from the perspective of the topology. A bit over my head, but I can sort of see the logic there.

Re: Branch version dirty area returns on reconcile.

StefanDieters1 — Wed, 29 Sep 2021 01:47:01 GMT

This looks like known behavior: See: https://pro.arcgis.com/en/pro-app/latest/help/data/topologies/dirty-areas-created-as-a-result-of-the-reconcile-process.htm

the step by step examples in the related page are very helpful: https://pro.arcgis.com/en/pro-app/latest/help/data/topologies/error-features-and-versioned-feature-classes.htm

I was able to partially code out the situation by checking for dirty areas after making any changes and validating on default, and checking again ... messy and never super reliable. That was with ArcMap