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

[ChristopherCounsell]

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

[DougBrowning]

I just checked and I am still 3.19 but this is scary as I have 15 forms with relates to each in my service.  Almost seems like it is looking for a layer id of 0 and not looking for the name.  No idea why this would have been changed after all these years though.  @JamesTedrick 

[ZacharySutherby]

Hello @ChristopherCounsell, 

With 3.22 we fixed BUG-000155440, which introduced an unintended side effect where parent layers for view services are always being checked which is incorrect especially when using a submission_url. 

This has been logged as a few different BUGs with a few different workflows, the defects we have noted are: 

• BUG-000176334
• BUG-000176112
• BUG-000176015

We have a resolution for this issue in our 3.23 builds of Connect. Would you be able to test your workflow in the beta version of Survey123 Connect 3.23 from EAC, the issue should be resolved in this version. 

[ChristopherCounsell]

Hi @ZacharySutherby thanks for the quick response. I was able to publish the form in an 3.21.62 and 3.23.47 (early adopter version).

I believe I'm across the requirements to create a relationship class that allows us to include other layers/tables within the form as repeats. Are there requirements we should be aware of when creating additional relationship classes between the layers/tables, i.e. not intended for use within the survey form?

[ZacharySutherby]

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. 

[ChristopherCounsell]

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.