Select to view content in your preferred language

Refreshing Dirty Areas Layer After Enabling Utility Network in ArcGIS Pro

170
3
Jump to solution
Tuesday
SanchezNuñez
Frequent Contributor

Good afternoon,

After running the Disable Utility Network and then Enable Utility Network tools, all data in the Dirty Areas tables is cleared because the table name changes (for example, UN_5_DirtyAreas becomes UN_7_DirtyAreas the next time I run Enable Utility Network).

Is there a way to refresh the Dirty Areas layer in an existing ArcGIS Pro map so that it reflects the latest data from the updated Dirty Areas table?

Thanks

 

 

0 Kudos
1 Solution

Accepted Solutions
MikeMillerGIS
Esri Frequent Contributor

The UN_# represents the Dataset ID of the Utility Network.  This is defined when the database is created, as this represents the ObjectID of that item in the GDB Items table.  This cannot change during enable/disable.  Only if you delete/recreate the database.  

Are you sure you are connected to the correct service?  Did you reload your data?

 

Are you referring to the Layer ID of the Feature Service?  If so, you should always assign a unique ID to them in your map prior to publishing.

View solution in original post

3 Replies
MikeMillerGIS
Esri Frequent Contributor

The UN_# represents the Dataset ID of the Utility Network.  This is defined when the database is created, as this represents the ObjectID of that item in the GDB Items table.  This cannot change during enable/disable.  Only if you delete/recreate the database.  

Are you sure you are connected to the correct service?  Did you reload your data?

 

Are you referring to the Layer ID of the Feature Service?  If so, you should always assign a unique ID to them in your map prior to publishing.

gis_KIWI4
MVP Regular Contributor

@SanchezNuñez - That is expected behavior. When you disable ands enable network topology it does a network wide validate and clears out the dirty areas. These dirty areas aren't necessarily topology errors.
If there are errors (red areas) then those will be retained even after enabling the network topology as they need fixing. 

If any topological changes occur dirty areas will be created (blue hatched area) when you do a validate then there are two possibilities -  1) it is successfully validated in which case the dirty area is cleared 
2) There is an error and blue area turns red.

As for the name change in the layer, I cannot reproduce that on my end.

 

VishApte_NGIS
Emerging Contributor

I have not encountered any table name change e.g. UN_5_* to UN_7_* as a result of disabling and enabling topology. It can only happen if you drop the topology and recreate it. Then the table names will have much larger ID as GDB Items sequence would have gone up considerably.