unable to create UN 5 Utility Network using Asset Package to Geodatabase

[KJ_GIS]

Here's my situation - 

Over the past couple months I've been testing the migration process as outlined in this tutorial

I started with the water essentials model that ships with water utility network foundation.  I've extended this somewhat from the expanded model, as well as making  customizations needed for my organization.   So far have been overall successful migrating from my geometric network into a local file geodatabase Utility Network.   

I'm now to the point where I'm ready to test bringing my local fgdb utility network asset package into my sde and portal environments.   My enterprise portal and AGS are both still at 10.9.1 since our org is still highly dependent on ArcGIS desktop.    It's my understanding 10.9.1 is only compatible with UN5.    There's an option on the latest version of ArcGIS Pro 3.5.1 untools, Asset Package to Geodatabase, to create Utility Network Version 5.   However when running this it errors out with this message "The Utility Network must be version 6 or higher".     I've tried to run the tool saving to version 6 (knowing this wont work with my portal, but just to test), and that errors out differently, complaining that "FLOW DIRECTION does not exist within table"

Asset Package to Geodatabase choosing  Current, Compatible, or 7, works fine.   

I've also tried the approach of Stage Utility Network (choosing UN5) to my sde, then Applying Asset Package, it also errors out.   

Is there any path for me to bring a newly created asset package or UN into UN5 in my 10.9.1 enterprise?   I have the feeling it's not working because I started with a newer data model then what UN5 will support.  

[gis_KIWI4]

@KJ_GIS - I think the issue is what you are suggesting it to be. The newer data model has fields that UN v5 does not. Perhaps you could try removing them somehow and see if that allows you to proceed. 

Removing them won't be easy. 
I think you will have to remove them form the asset package and possibly from any rules/properties table manually. 

The other option is to start with an older model that works well with UN v5? 

[KJ_GIS]

Thanks @gis_KIWI4  I was afraid that might be the case.  I'm holding out hope that it's a bug that's fixable before I go down that route.   I'm optimistic since the option to save at version UN5 was designed in the tool.    

[RobertKrisher]

@MikeMillerGIS 

[MikeMillerGIS · Accepted solution]

Two bugs here, we will release an updated to the untools soon to resolve them

- V5, we are just hard blocking this and need to lift that block, no workaround at the moment

- V6, if an asset package was created with a newer UN, it has items from that UN.  When we are creating a v6 UN with the asset package tools, it first assumes the target is the current UN and believes there is a FLOWDIRECTION field in the target classes.  We attempt to apply the field alias from the asset package to this field and it fails, as the field does not exist in the target.  Workaround is to delete the FLOWDIRECTION field from the domain and structure line and edgeobject classes in the Asset package.

[KJ_GIS]

Hi Mike, thanks!