nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS fails to update the parent version according to the last edited child version,

JamalNUMAN

ArcGIS fails to update according to the last edited version,

For example, in the screenshot below, a feature is firstly moved by Peter version, then by Sami and then by Ali. I was expecting that when applying the reconcile\post tool, then all versions (including the parent) will be updated according Ali’s version as it is the last edited version. This is not happening.

I observed that the ArcGIS respects the last child version created but not the last version edited when applying the reconcile\post tool. Am I correct?

Thank you

Best

Jamal

タグ付きの投稿をもっと見る

Accepted answers

All comments

Asrujit_SenGupta

In the tool, look at the order of the Versions:

AdamZiegler1

Hi Jamal - the tool as configured will ignore any conflicts (abort if conflicts detected is unchecked) and use the last version posted to the default version. So, in this case during the reconcile process there would have been conflicts between all edit versions, they were all ignored in favor of the edit versions. Then when the POST action occurred, all edit versions would push their edit, the last would be the final say. This tool should be used with caution. I would urge individual versions be reconciled/posted whenever possible, especially if editors are working in the same area.

-Adam Z

JamalNUMAN

Thank you for the help.

I like the term you used Adam “the last would be the final say”. But the last what?

Please, have a look on the two screenshots below. Guess which edits will be transferred to the parent in this case? It should be Ahmad as it is the most recent CREATED version which is not necessarily the last EDITED version.

I was assuming that the changes of the last EDITED version must be pushed to the parent but not the ones of the last CREATED version.

AdamZiegler1

Hi Jamal - although I can not find supporting documentation, I believe the order would be based on the version_id. This comes from the SDE_versions table in the SDE schema. What you show above makes sense, as long as the order in which the versions show up in the SDE_versions table are the same as how they are processed.

Something like this:

Version ID/Version

4/ali

5/peter

6/sami

7/ahmad

-Adam

AdamZiegler1

Hi Jamal - you raise some very good questions. In workflows that I have implemented in the past we always had each editor save, reconcile and post their versions individually. I would think that if I had implemented the reconcile and post on all versions I would use the abort if conflicts are found so that I could review edits to the feature and make the best decision on which was right. In your example, all editors are editing the feature not knowing that the other editors are modifying that feature as well. The software can't make a decision on which is correct, so it defaults to reconciling and posting the versions in the order that they were created. If you want the last edit in to be the one that sticks, you could have all editors use the same version.

-Adam Z

JamalNUMAN

thanks Adam.

What I wanted is to still work with versions but to be able to update the data according the last edited version but not depending on the last created. I understand that this might be challenging but that is the rules I wanted to work with.

Best

Jamal

AdamZiegler1

Having all your editors work in the same version would achieve that. Last edit is going to persist. When there are multiple edit versions the last created version will rule when using the batch reconcile tool. You could maintain your workflow, but choose to abort if conflicts are found...then go check each of the versions to see which you want to keep. Automated when no conflicts are found, manual but the results you want when conflicts are found.

-Adam Z

JamalNUMAN

Thank you very much Adam for the prompt help. The valuable scenario you have suggested can form a good solution for what I’m looking for

Best

Jamal

MajdoleenO_A__Awadallah

Dear AZiegler-esristaff,

Thank you so much for your input, Do you mean with “then go check each of the versions to see which you want to keep” applying this manually, then how I will guess who is the last edited version (Majd, Peter or Sami)?

Thank you in advance

Best,

Majdoleen

JamalNUMAN

I think the behavior needs to be enhanced such that the edits are updated based on the last updated ones but not in respect with the time the versions are created. That doesn’t make sense for me

会話に参加する

サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。

クイックリンク

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.