Select to view content in your preferred language

Database View — Refresh columns/schema of existing layer after schema change

1384
3
03-28-2023 10:11 AM
Status: Closed
Labels (1)
Bud
by
Esteemed Contributor

ArcGIS Pro 2.6.8; Oracle 18c 10.7.1 EGDB; SDO_GEOMETRY database view:

I have a database view (not registered with the GDB) that I've added to a map. I've spent some time configuring various layer properties including symbols, labels, joins, definition queries, etc.

I need to make a change to the view: Add a new field to the view by using a SQL Client. Now, I want the new field to show up in the attribute table in ArcGIS Pro.


As far as I can tell, there isn't a way to refresh the layer's schema so that the new field shows up in the attribute table.

I tried:

  1. Refresh button in the attribute table.
  2. Closing and re-opening the attribute table.
  3. Changing the data source in the properties (same source as before).
  4. Closing ArcGIS Pro and re-opening the map document.

But I still don't see the new field in the attribute table.

I would prefer not to remove the view feature layer from the Contents pane and re-add it, because then I would lose all my properties that I've set up. I'm aware that there is a geoprocessing tool to import the symbology from an old layer to a new layer. Which is good. But symbology is just one of many properties that I set up; I'm not aware of a way to transfer ALL properties from one layer to another.

Could functionality be added for refreshing the schema of an existing layer that is based on a view?

Thanks.


Related: Contents — Apply all properties from one layer to a different layer

3 Comments
Bud
by

It occurred to me that the view is technically a query layer in the Contents pane. So I ought to be able to re-define the SQL in the query layer, hopefully fixing the issue:

Bud_0-1680026404758.png

However, the property window hangs when I do that. So I can't hit OK in the properties window to apply the change.

Bud_1-1680026512753.png

So I can't tell if it fixed the issue or not.

 

Bud
by

This idea can be closed. Changing the SQL in the query layer solved the issue.

SSWoodward
Status changed to: Closed