I'm duplicating a related "implemented" idea to make sure this idea gets fully implemented.
Original: Filter Catalog EGDB FCs by owner
In Catalog:
It would be helpful if we could filter/show/hide enterprise geodatabase connection objects (FCs, tables, views, relationship classes) by owner.
For example, if there are objects from several owners (ROADS, WATER_RES, WATER), let me only see objects from WATER.
My connection is OS Authentication (objects from lots of owners), not a DB/owner-based connection (only one owner).
Oracle 10.7.1 EGDB
Thanks for opening this @Bud.
I wanted to share that it is possible to display only the objects in a geodatabase owned by a specific user by using the search functionality in the catalog pane. Searching by a username will temporarily filter your project pane by the search criteria, allowing you to view a single users data.
I recognize that this is different from the idea posed here but it may help you in the mean time.
In ArcGIS Pro, the current “List only objects owned by the connecting user” setting is useful when working with data owner connections, but it is not suitable for publishing workflows using non-owner database users.
In our enterprise geodatabase, data is owned by business schemas, while publishing is performed through dedicated read-only and edit database users. These users have privileges on the datasets but do not own them. When the option is enabled, the publishing connections appear empty; when disabled, all accessible schemas and relationship classes are displayed, which makes browsing very difficult in large multi-schema geodatabases.
It would be useful to make Catalog filtering configurable per database connection or workspace, with filters such as:
- show objects owned by selected owner/schema;
- hide or show object types such as relationship classes, tables, views, feature classes;
- save these filters with the .sde connection or the ArcGIS Pro project.
This would preserve clean owner-based browsing for data administration while supporting publication from read/edit application accounts.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.