Survey123 Connect 3.22.49 returning error "parent layer Id 0 not found for related table"

Question

Hi,

We have a Hosted Feature Layer with 2 layers and 3 tables. It has 6 relationships to support viewing related data in ArcGIS Online based maps and apps.

We have three survey forms targeting one, or two, of the layers/tables using the form_id setting and repeats driven by the globalid-parentglobalid relationship. This has been working without issue for over a year.

After updating to Survey123 Connect 3.22.49 I'm not able to update the survey form and get the error "parent layer Id 0 not found for related table". It's referring to a layer and relationship not used by the form, nor driven by globalid/parentglobalid. It seems that something has changed with Survey123 Connect, and it's now identifying relationships it previously ignored?

@DougBrowning have you encountered any issues with 3.22.49 or have any insights into what is happening?

I appreciate we may have set something up incorrectly but it's been functional for over a year and there's not a lot of formal documentation on what is supported around additional relationship classes in the layer design. We'd like to utilize them with the upcoming release of Field Maps and support for tasks and related form elements, so that users can add quick notes and save survey forms for the complicated stuff. @ZacharySutherby anything you can share from your end?

Cheers,

Chris

Teresa_Blader · Answer

@ZacharySutherby I'm just running into this now, at 3.24. Is there anything to be done about it?

I have a structure where:
Layer 1 has a 1:M with Layer 0 and 1:M with Layer 2.
Layer 0 has a 1:M with Layer 2.

For some forms in my workflow, I have a form that doesn't include Layer 0 to Layer 2 relationship, just Layer 1 to Layer 2, so Layer 0 is left out. Can't publish: Parent layer ID 0 not found for table....

Is that it? Just out of luck? The workaround doesn't really make sense to me... "Use two separate related tables, they can be in the same hosted feature layer or two separate hosted feature layers." My separate related tables are in the same hosted feature layer.

Thanks!!

ChristopherCounsell · Answer

I've sent you a direct message with our layers and relationships overview.

We have a setup where Layer 3 is related to Layer 2 (globalid/parentglobalid) and related to Layer 1 (globalid/customguidfield). It has worked fine for a year, only failed with the 3.22.49 release.

It's really valuable for these relationships to exist as it means users can view records more easily in maps and often Layer 3 may be populated directly without a parent in Layer 2.

This is going to be critical for the upcoming Field Maps update when it supports related record elements and Tasks. We'd like to keep simpler forms in Field Maps but continue to leverage Survey123 for others.

ZacharySutherby · Answer

Hey @ChristopherCounsell,

No additional requirements for relationships with other layers/tables not intended for use in Survey123. The thing to keep in mind is Connect has BUG-000120260 - Survey123 Connect for ArcGIS fails to publish a survey from an existing feature service when referencing a secondary related table, returning the error message: “Parent layer id _ not found for related table.” logged that is a consideration when building a schema intended for use as a submission_url in Survey123.

Where this would come into play is say you had a schema of:

* Layer 1
* Layer 2
* Layer 3

Layer 1 has a 1:M relationship with Layer 3, and Layer 2 has a 1:M relationship with Layer 3.

If you want to author a survey where the form_id is set to Layer 2 and Layer 3 is a repeat in the form design, this situation will run into the defect above as when Connect triages the feature layer it will incorrectly assume it should be using the Layer 1 to Layer 3 relationship causing the error message to display.