Select to view content in your preferred language

Unassign association role

468
2
Jump to solution
03-04-2024 11:57 AM
mshanaghan
Frequent Contributor

I am working on assigning association roles to my electric utility network features.

I understand that you can only unassign container/structure roles before enabling the network topology for the first time. Documentation: https://pro.arcgis.com/en/pro-app/latest/tool-reference/utility-networks/set-association-role.htm 

Does this mean that I should assign all association roles (and be 100% certain of them) before I enable network topology for the first time? If I change my mind about an association role, I am out of luck?

Thank you.

0 Kudos
1 Solution

Accepted Solutions
RobertKrisher
Esri Regular Contributor

Good question. Changing an asset type's association role from being a container to a structure (or vice-versa) will invalidate any containment/attachment rules for that asset type, along with all the associations associated with any features that belonged to that asset type. Because of this, I recommend you do several prototypes/pilots of your data to work through this, and any other, configuration or data modeling issues before you stand up your production utility network.

If you do make a mistake or change your mind several months later (on this or any other items we don't let you change after deploying), you do have a last resort to making changes. You can always export your data to an asset package (losing all your history and versions), make the configuration changes, then standing up a brand-new database and utility network.

View solution in original post

2 Replies
RobertKrisher
Esri Regular Contributor

Good question. Changing an asset type's association role from being a container to a structure (or vice-versa) will invalidate any containment/attachment rules for that asset type, along with all the associations associated with any features that belonged to that asset type. Because of this, I recommend you do several prototypes/pilots of your data to work through this, and any other, configuration or data modeling issues before you stand up your production utility network.

If you do make a mistake or change your mind several months later (on this or any other items we don't let you change after deploying), you do have a last resort to making changes. You can always export your data to an asset package (losing all your history and versions), make the configuration changes, then standing up a brand-new database and utility network.

mshanaghan
Frequent Contributor

This is very helpful. Thank you!

0 Kudos