When using the Migrate to Utility Network geoprocessing tool, the Target Class picklist does not list Assembly as an available class in the mapping section.
Yet the output migration database does include the Assembly feature class as shown below.
Is this a bug or intentional?
Solved! Go to Solution.
The migration toolset is designed to create a simpler model that doesn't include any rules for containment or associations. Therefore, we decided not include the assembly class as a target. The water valve class is a water device, and if you have a complex valve assembly that contains multiple components, you will be representing them as like-for-like objects in the utility network.
The migration toolset is designed to create a simpler model that doesn't include any rules for containment or associations. Therefore, we decided not include the assembly class as a target. The water valve class is a water device, and if you have a complex valve assembly that contains multiple components, you will be representing them as like-for-like objects in the utility network.