Hello! I work for a large organization, and frequently run into this scenario: one asset (say, a pipe under the road) is important to multiple workgroups (for this example, Envi and Hydro). Each interested party uses versioned editing w/multiple editors to maintain their portion of the data. This situation begs for related tables. However, you cannot set editing privileges such that Envi can edit its table, but can't accidentally edit Hydro's table.
Do you have any suggestions for efficient table design which enforces inter-table relationships without compromising editing privileges?
To follow up: I ended up creating feature classes which both groups could edit. Then I created a set of relationship classes between each FC and a group-specific table, and privileged the group-specific tables to just that group. So, both groups can add/edit features, but can only edit their own group's table.
To follow up: I ended up creating feature classes which both groups could edit. Then I created a set of relationship classes between each FC and a group-specific table, and privileged the group-specific tables to just that group. So, both groups can add/edit features, but can only edit their own group's table.
