We have created a UN v6 using Pro 3.3.5 and then extending the latest Esri foundational data model. We are now attempting to publish that to an Enterprise 11.1 environment. However, we get a "Domain code is invalid error" regarding the BIGINTEGER domain value defined within the AP_Attribute_Types domain, which is applied to the "attribute_type" field of the B_NetworkAttribute table. However, we've confirmed the value is not actually being used by any records. Attempting to remove the value renders all feature classes unreadable. We've confirmed our asset package is UN v6 and all objectIDs are 32-bit.
I'm interested to hear your thoughts.
Thanks,
Mike
Ok, that's good to know. Perhaps the BIGINTEGER error is a red herring for something else happening. Yes, we initially tried to deploy to Enterprise 11.1 with Pro 3.3. We were able to stage a UN and then attempted to Apply Asset Package. At that time we received the message: Error 160250: Objects in this class cannot be updated outside an edit session. Failed to execute (Append).
Various troubleshooting steps led us first a "Dataset version is later than is supported by your server" message, that main.SewerJunction shows a minimum client version 13.2, and eventually the BIGINTEGER error message.
Unless there's a different path we missed, our tentative plan is to start with a fresh UN created from 3.1 and apply/recreate our modified schema from 3.3.