I've been working with UPDM 2018 and untools 2.2 successfully for some time. Today, I upgraded to 2.3.0, and AssetPackageToUtilityNetwork is crashing. The first crash gave this error:
ERROR 001959: No valid asset type was found. [Excess Flow Valve/Automatic Reset]
Failed to execute (SetSubnetworkDefinition).
I tried running it again, and got this error:
Item Field OID Value Message Level
0 None None PipelineDevice-8 | PipelineDevice-17 | PipelineDevice-15 | PipelineDevice-19 | PipelineDevice-20 | PipelineDevice-16 | PipelineDevice-5 | PipelineDevice-18 | PipelineDevice-2 | PipelineDevice-12 | PipelineDevice-3 | PipelineDevice-13 | PipelineDevice-1 | PipelineDevice-9 | PipelineDevice-11 | PipelineDevice-4 | PipelineDevice-10 | PipelineDevice-6 AssetType domain is used in multiple places. error
What's up? Do I need to uninstall Pro 2.3 and go back to 2.2?
Solved! Go to Solution.
We have release v2.0.1. This is a minor update. We have eliminated the diagrams from the subnetwork definition. This will resolve the issue you are experiencing with 2.3.
I've successfully pinpointed the cause of the crash originally reported: it will occur if I take the UPDM asset package and add a many-to-many relationship class between PipelineAssembly and PipelineDevice, as below:
sRelClassName = "UNSGPipelineAssembly_PipelineDevice"
arcpy.CreateRelationshipClass_management(
"PipelineAssembly", "PipelineDevice", sRelClassName,
"SIMPLE", "Device", "Assembly", "NONE", "MANY_TO_MANY", "NONE",
"GLOBALID", "ASSEMBLY_GID", "GLOBALID", "DEVICE_GID")
arcpy.AddGlobalIDs_management(sRelClassName)
self.AddEditorTracking(sRelClassName)
I'm attaching a second asset package with that modification. In the meantime, I should be able to work around this issue by creating the relationship class after the asset package is applied, rather than going back to untools 2.2.0.