eSearch Widget 2.9 Related Tables

[RichBell]

I'm having an issue with more than 1 related table. I have 4 related tables configured in the eSearch widget, using WAB 2.9 the first table gets configured with an "id" of 0 and it works. The other tables get assigned an "id" of 1,2,3. They not not work. I get an error code in the console "id not found" or nothing, no error. But each table does work if I attach them separately one at a time and not all 4.

[RobertScheitlin__GISP · Accepted solution]

Rich,

   What does your relationship section of your rest endpoint for one of the layers look like? 

for example:

Relationships:

• calhoun.COUNTY.A_Bridge (0) -- Related To: ABIMS Bridges (0)
• calhoun.COUNTY.ADT (1) -- Related To: Average Daily Traffic (1)
• calhoun.COUNTY.Rail_Cross (2) -- Related To: Railroad Crossings (2)
• calhoun.COUNTY.Signs (3) -- Related To: Road Signs (3)
• calhoun.COUNTY.Guardrail (4) -- Related To: Guardrails (4)

[RichBell]

I looked at the restend "id's". I found the problem.

The eSearch must be configured with the related tables "id's" in proper order, not by the table names as in the restend. The names and id's where out of sync.

Thank You.