I have a feature class with nested related records like so: FeatureClass-->Table1-->Table2. If I click on a feature and select 'show related records' I'll get an attribute table tab with results from Table1. If I then select a record from that Table 1 tab and try to show related records the option is always disabled (greyed out). If I open attributes for Table1 via the layer list however this will work correctly for the same record (ie. I can select that record in the tab and then choose 'show related records' and get a tab for Table2 with any records related to the selected item in Table1).
This seems to definitely be a bug. Any ideas on how to get around this or get it fixed?
Ouch. No I rarely have the need to contact support directly. I emailed support. Hopefully this will be something they are willing to work on. Better support for related workflows would be really nice.
As Robert Scheitlin, GISP mentioned, currently only relationshipclasses for the first level are support in WAB. You can access them through REST, but the widgets in WAB wont show them.
We had a simular case and had to reduce the relationshipclasses to a single level (some attributes were added to the featureclass and the rest in the 1:M related table).
There are some other restrictions when consulting related features. From a selection of the table you wont be able to show the related features or filter features based on a selection from the related table. To mimic this functionality we tested converting the table to featureclass (using the label points of the related polygons). Far from optimal, but could be an option in some cases.
Until then, I'm having to do the same thing you are - flatten out our data via a crazed Rube Goldberg ETL process in order to enable staff who are authorities for information to keep their info up to date and let other staff make use of that info.