We have a map service with two layers that point to the same feature class. There is a table in the map service that is related to this feature class. When you look at the services directory at the table, it lists just one of the layers as being related to the table, even though both layers are in the same feature class. The one it displays is the one that is higher up in the layer list and that has a lower layer ID. The problem is that we want to do relationship queries against the layer it doesn't list.
This all seems to be determined behind the scenes by ArcGIS Server, so how does it work and how can we work around this issue? I don't want to change the layer order. It really should list both layers as being related.
