Relationship classes, Feature Datasets, and topological datasets are viewable across all schemas of a db and is quite annoying.I've done research and have found posts complaining about this since as early as 2009:http://forums.esri.com/Thread.asp?c=158&f=2284&t=279568and techinical articles posted recently explaining it:http://support.esri.com/en/knowledgebase/techarticles/detail/22721But y'all should really do something about this. If tables are contained to their schemas, related elements like RC's, FD's, and topology should all be as well.
Relationship classes (and feature datasets) can be viewed by users who do not have permissions to the related data. This presents a security issue since users should not know any relathionships exist unless they are granted permissions to them.
See description of issue here:http://forums.arcgis.com/threads/20223-See-Datasets-and-Relationships-without-granting-permissions
the issue still exists in 10.7.1 to me. does anybody know where to find the option (List only objects owned by the connecting user with enterprise databases) in ArcGIS Pro?
Still a super annoying issue as of 10.8.1. Does anyone know if there's traction on this?
Would still love this to be fixed as we have several clients with multiple data models of surveys within SDE containing 100s of relates which we must scroll through each time we connect to SDE directly to access data.
Have not yet found a way to even hide/filter relationship classes in Pro, but this would be a good interim solution if there were a way.
In ArcGis Pro open the Options Menu -> Catalog Browsing -> Browse projet items -> List only objects owned by the connecting user
This setting hides relationship classes from other users in Arcgis Pro
@YannickBourone
Interesting. Although in cases like mine, my connections legitimately include tables from other users. So the "List only objects owned by the connecting user" setting would exclude those tables, which wouldn't be what I'd want.
Very useful to know is available! I wasn't aware of this capability, thanks for bringing to our attention. As with @Bud we've got content shared with particular DB users to bring content together (e.g. PORTAL_VIEWER), that are then shared as services. With this option the viewer user ends up with no content, so filtering display of content types would be fantastic for our workflows. Thanks for sharing!
Melden Sie sich an, um zu posten, Inhalte zu folgen und mehr. Neu hier? Kostenlos registrieren.