Reconcile of Branch Version not displaying Changes

[Rohanrajan]

Hi,

I am using branch versioning to make edits to a UN dataset.

Scenario 1:

• I make a child version
• Make edits in it (Insert, Update, Delete) in more than 1000 records
• Reconcile
• No Changes to display after Reconcile

Scenario 2:

• I make a new child version to duplicate the Default version being intact (before posting the above said edits from Scenario 1)
• I Post the Scenario 1 edits
• Now I reconcile the Duplicate Default version with the Default that has Scenario 1 edits
• No Changes to display after Reconcile

Q1: Is this editing workflow correct?

Q2: Why can I not see the differences between the branches I merge / Reconcile-Post?

Q3: How do I review the changes between the branch and default versions before Posting it?

Any advice on this is much appreciated.

Thanks

[RobertKrisher]

Can you please confirm the following:

• After running append, the version differences tool shows the changes in your version.
• Please post a screenshot or python snippet including all the parameters you're using for reconcile (if you're using a GP tool)
• Show the version differences dialog after running reconcile.

As long as you didn't post, all the changes that were in your version before the reconcile should be there after the reconcile. But, as @gis_KIWI4 noted, it won't show any of the perceived changes to data caused by the reconcile with default. This is because those differences are changes that were applied to your version, but are rather differences that were applied to default that your version now sees.

If you are concerned that there is a bug, you should consider opening a case with support.

[UntitledMap]

Several of our GIS analysts are experiencing the same issues. Pro v3.4.3, Enterprise 11.5, PostGIS database hosted in Azure. 

User creates a branch version, then runs the Append tool to add data to that version.

After running the Append tool, the added data is not visible in the layer inside Pro, even after reconciling and posting. It is visible in the web layer though, before reconciling and posting. Seems like it Appended directly to the default branch. 

We've tried adjusting account permissions, but that doesn't seem to be the issue either. 

@RobertKrisher - Do you know if this is a bug with the tool or specific version of Pro? 

[RobertKrisher]

If the layer is pointed to a version and you're seeing it appear in default, I would log a case with support on that.