Skip to main content
Open

ArcGISBranchVersionManager to support querying version differences

Related products:FME FormIntegrationsTransformers
  • November 14, 2025
  • 3 replies
  • 85 views

bruceharold
Supporter
Forum|alt.badge.img+19

The Esri ArcGIS Connector hub package includes the ArcGISBranchVersionManager transformer which currently supports List, Post and Reconcile actions.

This idea is to support querying version differences using the version management Differences API endpoint, including resultType and async parameter options.

The use case is to find edits that are to be propagated to an external (to ArcGIS) system in an efficient delta transaction.  Usually it will be the default version state at two moments that will be queried, as it is the default version that will be propagated to the external system.

In the legacy traditional version reading scenario, an SDE reader could extract differences with a Baseline Historical Date and Time constraint, this idea is an equivalency issue for branch versioned data.

 

3 replies

PierreAtSafe
Safer
Forum|alt.badge.img+8
NewOpen

jimc
Participant
Forum|alt.badge.img
  • Participant
  • November 17, 2025

Its worth noting that the Esri ArcGIS Feature Service Reader in the ArcGIS Connector package already has a Differences parameter, though it is limited to the differences between a named version and SDE.Default. Ideally it would be the reader that gets this new capability, rather than BranchVersionManager.


bruceharold
Supporter
Forum|alt.badge.img+19
  • Author
  • Supporter
  • November 17, 2025

Its worth noting that the Esri ArcGIS Feature Service Reader in the ArcGIS Connector package already has a Differences parameter, though it is limited to the differences between a named version and SDE.Default. Ideally it would be the reader that gets this new capability, rather than BranchVersionManager.

Thanks Jim, let’s see what comments turn up here on this. I was picturing a workflow where two moments in time (e.g. previous sync, now) for the default version were of interest.  I take your point a version with no edits could be compared to default over time as well, if the reader supported it.