Handling n:m Relationships Between Utility Network Feature Classes and Standalone Tables

[RoswithaLauterbach]

I want to create an N:M relationship between several UN feature classes and a standalone table. I started in a local FGDB  (ArcGIS Pro 3.5.3) to create the relationship classes (based on globalid) and made some connections. Afterwards, I exported the AssetPackage and deployed it to ArcGIS Enterprise 11.5. Now I encounter some issues:

1. In the exported Assetpackage, I noticed that the relationships are still present, but all actual relationships disappeared (I have the feeling that this is due to the fact that the table is not part of the UN FDS. However, it seems that it is not possible to create a table inside a FDS).
2. In the deployed UtilityNetwork, even the relationship classes themselves are not created.  

Could you clarify whether n:m relationship classes between UN features and tables are currently supported? Does anyone has an idea what I could do to overcome this issue?    

[gis_KIWI4]

@RoswithaLauterbach - I created a relationship class and table with our deployed UN as a test and it worked for me. 

I can see the related data in ArcGIS Pro. 

I am certain we can create additional tables and relationship classes post deployment and it works as intended as long as they relationship class is included in the map that is used to publish the service.

Something that caught me out was not including the relationship feature class while publishing the service.

Hope this helps 🙂  

[RoswithaLauterbach]

@gis_KIWI4 did you try exporting this as Assetpackage and re-deploy it? As long as I stay in a deployed UN, it works fine for me as well.