reconcile and post

[carlataylor-emrit]

Hi. We have  a branch versioning with our Enterprise account. At the top of the tree we have Default. Most users work in their area versions and reconcile and post to the Corporate version. This is where I work. Over time, the reconcile to Default has become non existent, however our IT team has tried to connect to our Oracle database and are pointing towards Default. I tried to reconcile to this version but there are years worth of edits.

Has anyone ever had to reconcile nd post after years of not doing so? What can I do as it is failing on my local machine.

[George_Thompson]

What is the error that you are receiving?

How long after you start the reconcile process does the error occur?

You might have to increase the timeout of the service during the R / P process to some very large #. This may allow the process to complete before the service may time out.

What is the service default settings?

I am also not clear on what the IT department connecting to the Oracle table has to do in this scenario. If they connect to the table directly, they would technically see all the records in it. It would require a custom query to filter to the "current" ones. This is due to all branch versioned data is in a single table.

[BillFox]

😯😮😲

This is due to all branch versioned data is in a single table

[George_Thompson]

What I mean by that is that all the records (adds / deletes / etc.) are in a single table and not "spread" across other tables as they are in Traditional Versioning. https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/branch-version-scenarios.ht... for more info......

[BillFox]

so far, it reads we are locked into branch for things like utility network and parcel fabric

is esri going to allow traditional versioning for those too?

[George_Thompson]

I cannot speak with full authority, but Utility Network / Parcel Fabric / New Workflow Manager all require Branch Versioned data. I am not sure that they will make it available to use with traditional versioning.

The way I look at branch versioning is that is the updated way to work with web services. I also think that new capabilities will use branch versioning in the future also.

There are other things in play here, which is too much for a post.....

[BillFox]

🤔

and the list goes on, only a single level of versions, No "posting version" between protected default and private editor version, etc.

what a shake-up

Considerations

Consider the following when editing the data in a named version:

• Branch versioning allows only one level of named versions to be created from the default version. In other words, you cannot create a named version from a named version.
• Only one editor per named branch version is allowed, or multiple users can read from the named version. Once an editor begins editing data in a named version, an exclusive lock is obtained and no other user can connect to the version.
• You can undo and redo edits when editing the data in a named version.
• Reconcile and post operations are done using the default version as the target version; you cannot reconcile with or post to another named version.
• Because the branch versioning model is a temporal model in which all records and edits are tracked in the same base table, there is no requirement to compress.

[BillFox]

so another complete re-read of the versioning  documentation...

"Because an enterprise geodatabase can contain datasets with a mixture of versioning types, it is important to understand the implementation and usage workflows supported for each type."

https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/overview-of-versioning-in-a...

[George_Thompson]

This is important to understand when designing the data and storage. I have seen people have both in a single EGDB and it works well. One of the biggest things that I see is related to lack of administration and maintenance of the EGDB that cause the most issues.