Utility Network and Distributed Collaboration

[jsarthur]

Has anyone successfully implemented a Distributed Collaboration (DC) using Utility Network (UN) feature layers? We set up a DC for our internal collaboration between the referenced feature layers in the ArcGIS Enterprise (AGE) Portal to our own AGOL portal and syncing as a copy. There are about 40 feature layers total in the DC, but half of these layers are erroring out on the sync. The other half sync with no issues. We are on AGE 10.9.1 and UN version 5.

The error message is: "Request made to publish items as new services but the item 'xxxxx' already exists. Unable to publish item. Remove existing item and sync collaboration workspace."

I have been working with Esri support and they say the collaboration configuration is correct. We created a new test collaboration and the same errors persist. I am speculating on whether it is even possible to use DC with UN layers because of their complexity (the UN feature classes contain numerous Attribute Rules, for example).  

I hope to find out if anyone else has a similar setup that is operating successfully. Thanks!

[RobinsonJonathanDOIT]

Thank you for the detailed response!

[aperi]

@RobertKrisher  Thanks for the clarification on ArcGIS Enterprise (AGE) to AGOL.

Checking on Utility Network Distributed Collaboration support — is it now supported between two ArcGIS Enterprise portals (e.g., both on 11.5)?  Thank You!

[RobertKrisher]

@aperi 

Distributed collaboration is supported between different ArcGIS Enterprise environments at 11.5: Getting the most out of distributed collaboration in ArcGIS Enterprise

[aperi]

Thank You @RobertKrisher for the link about AGE-AGE DC. Yes- the UN feature layers do sync across in AGE-to-AGE distributed collaboration, but the Utility Network layer (and the dirty areas sublayer) itself does not show up on the receiving portal. Just checking if this is the expected behavior when enabling UN for collaboration?

[RobertKrisher]

@aperi that is the currently expected behavior.

[aperi]

Thank You @RobertKrisher 

[jsarthur]

@RobertKrisher Thanks, Robert. I was specifically asking about AGE to AGO, which I now understand that AGO is not intended to work with UN layers. We have especially seen issues related to the OID change to 64-bit with UN 7 and working through issues with services that have sync enable, so trying to copy UN feature layers from AGE to AGO has not been a viable option. Note: I have only been trying to copy the layers without the UN object for read-only purposes, and even that has been a huge challenge. Thanks again!

[RobertKrisher]

@jsarthur I updated my response to make it clearer I was responding to the question @aperi asked. The tabbing/indenting on the community site sometimes makes it hard to track the separate threads.