Branch Versioning and Attributed Relationship Classes

Question

I recently took an ESRI class on Branch Versioning that was focused on the process of preparing data for Branch Versioning. I am now configuring my test data and of course I hit a snag that was not covered in the ESRI class, attributed relationship classes. Do attributed relationship classes need to to be configured for Branch Versioning with editor tracking enabled?

AnnieJames21 · Accepted Answer

The following would be the best practice for registering many:many relationship classes:

1) Add GlobalIDs  to all participating data in no particular order, but likely: Origin Feature Class, Destination Feature Class, Attributed Table.

2) Add Editor Tracking to all participating data in no particular order, but likely: Origin Feature Class, Destination Feature Class, Attributed Table.

In 2.9, you can use the Manage page from the r-click context menu in the Catalog pane to complete steps 1 and 2 in a single operation on the selected item.

3) Register the Origin Feature Class as Versioned (this will register the Attributed Table as versioned as well)

4) Register the Destination Feature Class as Versioned.

Again in 2.9, you can use the Manage page from the r-click context menu in the Catalog pane to complete steps 3 and 4 in a single operation on the selected item.

Let us know how it goes.

Annie

MelissaJarman · Accepted Answer

Timothy -

Are you saying that you published the origin and destination table, but did not include the attributed relationship class in the map service and this caused problems when editing the service?

I did find this documented in the help, but I am not sure if there are analyzer warnings/errors for this type of situation.

Prepare data to publish a feature service

* Feature services allow queries on related data, but only if the relationship is defined through a geodatabase relationship class. If a published map document has a layer and table related through a geodatabase relationship class, the feature service allows queries on the layer to return objects from the related table. To support queries that return related objects, you must include the table and layer involved in the relationship class in the published map document. If either the origin or destination layer or table is not included in the map document, the feature service ignores the relationship.Note:

For attributed relationship classes, include the relationship class table in the map document.