akmanchianand

relationship/table ids are mixed up when multiple layers point to same featureclass

Discussion created by akmanchianand on Sep 22, 2011
Latest reply on Oct 10, 2011 by rnarayanan-esristaff
When we publish a feature service with four layers referencing the same feature class with one related table, the relationship/table ids in REST are mixed up.

Here is what it looks like in REST,
Layer one (0)
Layer two (1)
Layer three (2)
Layer four (3)
Table one (4)

Only the first layer displays the correct relationship and table id as below
forwardlabel (4) -- Related To: Table one (4)  ---- this is correct

The other three layer relationships are displayed incorrectly as below
backwardlabel (4) -- Related To: Layer one (0)      ---should be related to table one but shows layer one instead!
backwardlabel (4) -- Related To: Layer one (0)      ---should be related to table one
backwardlabel (4) -- Related To: Layer one (0)      ---should be related to table one

The table displays the correct relationship and table id i.e.
backwardlabel (4) -- Related To: Layer (0)

Is this a bug or am i missing something obvious?

regards
Anand

Outcomes