Select to view content in your preferred language

Relationships not showing up in REST API

10428
21
03-31-2011 09:47 AM
AricMueller
Deactivated User
We have ArcGIS Server 10.0 sp1 running on Windows (behavior exhibited in 2003 and 2008x64).  The published MXD services have relates established in the MXD to Oracle tables.  The tables are access via Oracle authentication.  The related tables are not registered in the geodatabase or arcsde.  In most cases, the tables are public synonyms of objects in another schema.  The relates work fine in ArcMap but do not show up in the REST api once published.  No errors or warnings are logged.  Relates established to other featureclasses do show up.  The behavior seems inconsistent as we have XP workstations with the exact same build of desktop and server which can make a relate to unregistered tables in another Oracle instance.  Can anyone provide any insight on whether this is expected behavior?  In other words, shouldn't any relationship (explicitly established as a relate in ArcMap) be visible to the REST api as long as there are no permissions issues (which there are not here)?
0 Kudos
21 Replies
ReneRubalcava
Esri Frequent Contributor
You guys provided some great info, thanks. I tried searching, but nothing came up.
I ran into this problem yesterday where I had relationships built in mxd, working in service, regular MapServer.
Added a join to the feature in mxd and relates stopped working in REST. Removed join, they work again.

It's really annoying, because now I have to fall back the old method of writing custom service endpoints to perform these queries, then merge them to the spatial data client-side.
0 Kudos
MeleKoneya
Frequent Contributor
We have a few projects where we need to join a table to a feature class and then publish the map service with Feature Access so I am disappointed that this is not possible with 10.0 and it sounds like the capability hasn't been added in 10.2.1 either.    We use a SQL table to symbolize off of and that SQL table is updated outside or our Geodatabase.     What we end up doing is creating a map service that has the Feature Class with a join in it to SQL and we use that for display and then we have another service that has the Feature Access capability enabled.    It ends up being tough to maintain and program around so I hope ESRI adds this functionality.

Mele
0 Kudos