Latest Contributions by JohnAlsup

We remove the majority of attribute rules from the models before we release them.  We keep the attribute rules in a repository found here arcade-expressions/attribute-rules/attribute_assistant at master · Esri/arcade-expressions · GitHub.  We have done this because of the impact of any model modification to attribute rules. ... View more

In the Utility Network, if you enable "Include Structures" on the subnetwork definition, then when update subnetwork is run, the subnetwork name field will be populated with all the subnetwork names that this structure is associated with.  The only other thing you would need to do is create a junction feature on the line and then create a Structural Attachment association between each junction and the pole.  This would be a way to obtain the same information as your previous relationship class using standard utility capabilities. ... View more

You have three options, each with pros and cons. The StructureJunctionObject will increase the size of the associations table which will impact the time of enable topology and disable topology.  There are other potential impacts to things like validate, export subnetwork to name a few. The geodatabase related table method avoids those issues, but introduces new issues.  The relationship can lead to false or confusing conflicts and the user interface for geodatabase relationships leaves a bit to be desired. The third option is to make the jointuse table a related table only in the map, not using a geodatabase releationship class.  This avoids the conflict issue and actually provides a better UI experience for the user.  The draw back is you must manually create the record in the joint use table and copy and paste the GLOBALID from the pole to the joinuse record.   This could be done with an addin.   ... View more