topic Re: Failure to “post” changes from child versions to parent, in Data Management Questions

Failure to “post” changes from child versions to parent,

JamalNUMAN — Fri, 04 Sep 2015 14:33:46 GMT

Failure to “post” changes from child versions to parent,

In the screenshots below, three child versions are taken from the parent version (default).

Same feature is edited in the three child versions.

Changes in the child versions are detected and “Reconcile” is applied

“Post” has introduced the message below

Then how the changes in the child versions can be posted to the parent?

Does the ArcGIS detect the conflicts between the child versions?

Does the ArcGIS resolve the conflicts between the child versions and then resolve them with the parent?

Thank you

Best

Jamal

Re: Failure to “post” changes from child versions to parent,

JakeSkinner — Fri, 04 Sep 2015 14:56:31 GMT

Hi Jamal,

Since the version the DEFAULT version is protected, you must connect to the geodatabase as a user with DBO privileges to perform the post. If there are conflicts found, you will be prompted to resolve the conflicts.

Re: Failure to “post” changes from child versions to parent,

AsrujitSengupta — Fri, 04 Sep 2015 14:56:47 GMT

The error that you are observing during Post is indicating that you may not be connected as a DBO user. The DEFAULT version has an Access level of 'Protected' and thus only the version owner, DBO in this case can do the POST.

Conflict will only be detected if the same feature has been modified in both the versions, the Parent and the Child.

When you perform the Reconcile for the first Child version, no conflict should be detected, because the feature was not modified in the DEFAULT version, but was only modified in the Child version.

However, subsequent Reconciles for the other two child versions should detect a Conflict, and will let you choose in whose favour to resolve that Conflict.

Re: Failure to “post” changes from child versions to parent,

JamalNUMAN — Fri, 04 Sep 2015 15:37:53 GMT

Many thanks guys for the answer.

Sure the default is accessed by the owner (sa) as shown in the screenshots below. Nevertheless, post fails to work.

What other issues should I consider?

Re: Failure to “post” changes from child versions to parent,

AsrujitSengupta — Fri, 04 Sep 2015 16:49:08 GMT

All the 4 connections are with 'sa'?

Re: Failure to “post” changes from child versions to parent,

JamalNUMAN — Fri, 04 Sep 2015 19:14:03 GMT

At all! Connections are made with different users (ali, amjad and sami) as shown in the screenshots below

Re: Failure to “post” changes from child versions to parent,

AsrujitSengupta — Fri, 04 Sep 2015 19:19:18 GMT

Exactly...so when you perform the reconcile, use the Connection which was connected with 'sa'...change to the other version and then do the reconcile.

Re: Failure to “post” changes from child versions to parent,

JamalNUMAN — Fri, 04 Sep 2015 20:30:56 GMT

well. If the “start editing” is started selecting the default version as the target, then neither “reconcile” nor “post” are activated! Then how changes in the child versions can be transferred to the default?

Re: Failure to “post” changes from child versions to parent,

AsrujitSengupta — Fri, 04 Sep 2015 20:35:08 GMT

Follow the below workflow:

1. From the connection as 'sa' user> add the feature class into ArcMap

2. Change Version to the child version

3. Now start editing

4. Now do the Reconcile

You should get the conflict

Re: Failure to “post” changes from child versions to parent,

JamalNUMAN — Sat, 05 Sep 2015 04:23:56 GMT

Thanks Asrujit.

I’m not sure why this is the only scenario that works; I mean to firstly add the default version (with sa credentials) and then to switch it to a child version and next to apply the reconcile\post (in editing environment).

Re: Failure to “post” changes from child versions to parent,

AsrujitSengupta — Sat, 05 Sep 2015 10:07:21 GMT

It will work even when you connect with any 'sysadmin' login and connect to the child version to perform the Reconcile\Post.

Re: Failure to “post” changes from child versions to parent,

JamalNUMAN — Sun, 13 Sep 2015 17:31:48 GMT

Why this is considered as “conflict”? There is no update for the same feature in both parent and child versions

http://webhelp.esri.com/arcgisserver/9.3/java/index.htm#geodatabases/an_overv-60074501.htm

Re: Failure to “post” changes from child versions to parent,

AsrujitSengupta — Sun, 13 Sep 2015 22:32:03 GMT

The error that you are observing during Post is indicating that you may not be connected as a DBO user. The DEFAULT version has an Access level of 'Protected' and thus only the version owner, DBO in this case can do the POST.
Conflict will only be detected if the same feature has been modified in both the versions, the Parent and the Child.
When you perform the Reconcile for the first Child version, no conflict should be detected, because the feature was not modified in the DEFAULT version, but was only modified in the Child version.
However, subsequent Reconciles for the other two child versions should detect a Conflict, and will let you choose in whose favour to resolve that Conflict.

Re: Failure to “post” changes from child versions to parent,

JamalNUMAN — Mon, 14 Sep 2015 04:56:56 GMT

The 9.3 help (in my screenshot above) indicates that editing in different editing sessions result in “conflicts”. For example, if a feature is updated (in an edit session) and then the edit session is stopped and restarted where the same feature is updated (in the second edit session), this causes conflict!!!!!

How this can be true?

Re: Failure to “post” changes from child versions to parent,

AsrujitSengupta — Mon, 14 Sep 2015 14:41:50 GMT

The link doesn't mention this:

and then the edit session is stopped and restarted where the same feature is updated (in the second edit session), this causes conflict!!!!!

The link is talking about scenarios when the feature is being edited in two simultaneous sessions.

If the same feature has been updated in the same version by two different Editors, then conflicts are bound to occur asking which edit to maintain and which one to discard.

Re: Failure to “post” changes from child versions to parent,

JamalNUMAN — Mon, 14 Sep 2015 15:32:32 GMT

Thank you for the elaboration. It is much more obvious now.

However, doesn’t the “conflict” need to have updates on the same feature on both parent and child? In the link provided, it states that there is a conflict at the level of same version as the same feature is updated from two editors.

Which ones of the following can be considered as conflict?

Same feature is edited in both parent and child
Same feature is edited in child versions
Same feature is edited in the same versions but from multiple editors (who are accessing the same version at the same time)

Re: Failure to “post” changes from child versions to parent,

AsrujitSengupta — Mon, 14 Sep 2015 15:54:50 GMT

Both 1 and 3 are TRUE.

Option 2 is actually a part of option 3 itself.

Re: Failure to “post” changes from child versions to parent,

JamalNUMAN — Mon, 14 Sep 2015 16:15:53 GMT

This new thing for me; that updating same feature in different child versions is considered as conflict (particularly id multiple editors are updating same feature in same version).

Before, I thought that conflict IS LIMITED TO updating the same feature in both parent and child version.

Re: Failure to “post” changes from child versions to parent,

AsrujitSengupta — Mon, 14 Sep 2015 16:19:13 GMT

We always learn something new everyday

Re: Failure to “post” changes from child versions to parent,

JamalNUMAN — Sun, 04 Sep 2022 15:44:20 GMT

The good thing in Pro that the name of the user is displayed with the name of the version.

Both the parent and child versions are accessed with the sa user which makes it possible to post the edits from the child to the protected parent. The child is accessed by the sa by adding the layer by sa (as usual) but then switching the version to child