EnableNetworkTopology fails with "Domain does not exist"

NeilEtheridge

I am working on a UN implementation project and we recently made the move to Pro 2.5 and UNTools 2.5.  After deploying an asset package, we are now hitting an issue with EnableNetworkTopology where is fails with the message "Domain does not exist" ... 

It took quite a bit of working out what this meant but I finally tracked it back where one of the asset groups in "StructureJunction" does not have its asset type domain assigned.

The domain is present in geodatabase and can be manually assigned.  Although trying to save after assigning gives a 999999 error.  Saving a second time usually does the trick and makes it stick.  After this the EnableNetworkTopology is able to be rerun and completes successfully.

Saving error:

I have checked the source asset package (shown below) and the Domain is correctly assigned.

The issue appears to be with the deployment of the asset package using the tool arcpy.pt.AssetPackageToUtilityNetwork.  No errors are reported to the log however.  This was not an issue with UNTools 2.4

Has anyone come across something similar?

I have attached the UNTools log for anyone wanting a deeper look.

Many thanks,

Neil

DeployUtilityNetwork_untools_20200429_205816.log.zip

JakeSkinner_0-1715709876003.png

PaulLeBlanc1

That's the only domain that was not assigned? There could be something conflicting with the field definition and default values. If apply asset package always fails to assign this domain, then I'd like to take a closer look at the schema.

At Pro 2.6, we've fixed the error message on enable and you'll now get something like:
 ERROR 003077: All network feature classes must have attribute domains assigned on the Asset type field for each subtype (Asset group). [ElectricDistributionDevice - test]
 Failed to execute (EnableNetworkTopology).