Branch version changes not in default after posting

Question

Hello,

we are having the following issue with branch versioning:

After adds, updates and deletes are made, we reconcile and post to the default version. In some cases, the edits made to one or multiple that were edited do not appear in the default version. They also disappear from the version changes, so when we click on Version Changes in ArcGIS Pro, there are no changes listed. One way to make the changes appear again in the Version Changes is to edit the attribute of one of the features in the affected layer. Posting again after doing that, it mostly works and the changes appear in the default version.

I looked into our postgresql database and checked what happened when this issue appeared. I saw that in the table sde_branch_tables_modified, all rows with the branch_id of the affected version disappear after posting (which I think is the expected behaviour), but the edited features in the table keep the gdb_branch_id of the version instead of switching to 0 (default version). It's hard to properly analyze the problem though, as it does not happen constantly or in any recognizable pattern. I also can't find any relevant entries in the logfiles.

Any advice or similar experiences?

Best regards

malte · Answer

The EGDB upgrade seems to have fixed the issue.

George Thompson · Answer

I am assuming you meant Pro 3.5.1 since 3.6.x is not out yet.

I may be a good idea to upgrade your EGDB to match the version of your client. I would do this in a test environment first and retest the workflow (you may need to publish new services from the test environment).

There have been lots of updates since Pro 3.2.x

malte · Answer

We're currently on Pro 3.6.1, Enterprise 11.4 and Postgresql 14.6.

I just checked the Geodatabase version, most are still on 3.2.1. It might be worth to upgrade and see if it changes something.