idea Catalog View — Indicate if object is a database view, annotation, etc. in Type column in ArcGIS Pro Ideas

Catalog View — Indicate if object is a database view, annotation, etc. in Type column

Bud — Tue, 21 Mar 2023 16:07:21 GMT

Idea Edited 2023-03-17

In the Catalog View:

Database views are currently categorized as tables in the Type column. And annotation FCs are categorized as feature classes.

Those categorizations seem misleading. Could they be changed to better reflect those object types?

There might be other kinds of objects that aren't categorized specifically enough in mobile geodatabases too. I haven't tested them all. See mobile geodatabase datasets for a list.

Related: Filter Catalog by object type

Re: Catalog View — Column to indicate object type (FC, table, DB view) - Status changed to: Already Offered

NaicongLi — Thu, 16 Mar 2023 22:21:47 GMT

Hello @Bud , what you are suggesting is already offered in ArcGIS Pro. If you would widen the Type column in the Catalog view, you will see that the Type string for feature classes, tables, and so on, are indeed distinct:

Re: Catalog View — Column to indicate object type (FC, table, DB view)

NaicongLi — Thu, 16 Mar 2023 23:14:11 GMT

@Bud - We do appreciate your feedback, and look forward to more of your ideas!

Re: Catalog View — Indicate if object is a database view in Type column

Bud — Sat, 18 Mar 2023 02:07:29 GMT

@NaicongLi

I've edited the idea so that it's specifically about database views and annotation. Could this idea be re-opened? Thanks.

Re: Catalog View — Indicate if object is a database view, annotation, etc. in Type column

Bud — Wed, 22 Mar 2023 13:50:01 GMT

@NaicongLi

I checked with support and they say it's working as designed. So I think that means this is a legitimate idea, not a bug.

Esri Canada Case #03294188
The scenario that you have described with views in a mobile geodatabase stored as a Mobile geodatabase table is an expected behaviour. The data you add to a mobile geodatabase can be stored in the following dataset types:
Tables (nonspatial)
Feature classes
Relationship classes
Feature datasets
For the views you have created, it is non-spatial so they will be stored as a mobile geodatabase table.

This web link shows all the dataset types for a mobile geodatabase: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-mobile-gdb/mobile-geodatabases.htm#ESRI_SECTION1_C30D73392D964D51A8B606128A8A6E8F

ENH-000156877
In ArcGIS Pro geodatabases (Enterprise, File or Mobile) views are categorized as table in the Catalog View type column

Re: Catalog View — Indicate if object is a database view, annotation, etc. in Type column - Status changed to: Open

NaicongLi — Tue, 21 Mar 2023 16:01:26 GMT

Re: Catalog View — Indicate if object is a database view, annotation, etc. in Type column

SSWoodward — Thu, 06 Apr 2023 17:23:01 GMT

Thanks for the idea @Bud

This looks a lot like an idea that is already in product plan:

Link - Pro Catalog Sort by Feature Geometry

Let us know if that idea meets the needs of your request to specify the feature type of each feature class in the catalog (anno, point, line, view etc) and we can merge.

The behavior you're seeing with unregistered mobile geodatabase spatial views showing as non-spatial tables is a known bug.

BUG-000157223 - The View Icon shows as Standalone table instead as Feature Class in Mobile Geodatabase

Re: Catalog View — Indicate if object is a database view, annotation, etc. in Type column - Status changed to: Needs Clarification

SSWoodward — Thu, 06 Apr 2023 17:43:30 GMT

Re: Catalog View — Indicate if object is a database view, annotation, etc. in Type column

Bud — Thu, 06 Apr 2023 18:08:32 GMT

@SSWoodward Feel free to merge. (No need to bring over all the comments from this post.)

Re: Catalog View — Indicate if object is a database view, annotation, etc. in Type column - Status changed to: Closed

SSWoodward — Thu, 06 Apr 2023 18:32:10 GMT

@Bud I don't believe I can merge without the comments, but agree they are better where they are. I'll close this. Go ahead and give a kudo to the other idea and I'll make sure the other kudo makes its way over there from here.