Allow the unique assignment of Relationship IDs when publishing

[roemhildtg]

Similar to how we publish layers with a uniquely assigned ID, we also need to assign relationship IDs. This is because applications sometimes reference these ids and there is no rhyme or reason as to how relationship IDs get set internally so every time I publish after adding a layer that partakes in a relationship the IDs change. 

Please allow us to assign a relationship ID or ensure that ArcGIS doesn't renumber an existing relationship in a map when publishing to arcgis server.

[MatthewRantala1]

Just commenting that this is a enhancement in the queue (no idea when it will be implemented): https://support.esri.com/en-us/enhancement/add-the-option-allow-assignment-of-unique-numeric-ids-f-e...

[RobRader1]

@MatthewRantala1  :  It would be very helpful if a workaround could be created for on premise enterprise type installations and linked to this Idea. If such a workaround exists today, then please link that instead. 

Such a workaround could take the form of:

a) Updating the service definition file that will be used by the service. Perhaps the process would be publish the service. Then update the service definition file. Followed by republishing the service using the new service definition file.

b) Update the Map/Project used to publish the service and set this directly.

The work around could take the form of a python script, manual changes or any tool type you prefer.  It could also take the form of an API example. Such an example, could then wrapped up as a sample tool and maintained by the community. 

In a nutshell, a workaround would be extremely helpful.

[TanuHoque]

Implemented in ArcGIS Pro 3.3. You also need ArcGIS Enterprise/Server 11.3 or above too.

Once you enabled this 'assignment of unique numeric IDs..' option on a map's Properties page

... you will see text box(es) in the Relates tab under each relate, that allows you to provide user defined IDs to each relates.

Help: https://pro.arcgis.com/en/pro-app/latest/help/sharing/overview/assign-layer-ids.htm#ESRI_SECTION1_42... 

Thank you all for your suggestions and contributions.

[tiztrain]

hey @TanuHoque ,

I have noticed that with this new setting, you have to be careful if you have multiple groupings in a service. In the image below, 'Site - SEFF' and 'Species - SEFF' and related. The others are also related separately.

In this case,  I have to make sure that the LayerIDs that are assigned go from 0-5 and then I have to make sure that the relationshipID uses the same number as the layerID. If I don't, trying to create some offline managed areas fails.

Is this by design?

[lkirbywrk]

c

[LanceKirby2]

@tiztrain I've been dealing with a similar issue. Can you describe in more detail what you experienced? I've included a description below of my issue.

Offline areas drop related tables and I believe it is a similar issue. I don't have matching ids, since my service (and web map) were originally published with ArcGIS Pro 3.2 and later overwritten with ArcGIS Pro 3.6.

I have been experiencing consistent behavior with a polygon + 7 related point feature classes. I also have a table with 11 related child tables. In my offline areas, 5/7 point layers visible and selectable within relationship navigation. All related tables are visible, but only 7/11 are selectable. The craziest thing, is when I attempt to add to one of the selectable tables, it sends me to a totally different related table and not necessarily a selectable one. 

After seeing your comment I renumbered the layer/table ids sequentially (not the relationship ids) and everything seems to be working. The layer ids and related ids don't necessarily match so I wonder if I am going to run into something else later.

[tiztrain]

@LanceKirby2 I have not been having any more issues regarding relationships. I have been able to get my schema's with 10+ relationships to work fine consistently now.