nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Multiple related tables Survey123 Connect

PeterMcdonnell_1968

Good morning all,

I have not attempted this before and have followed a number of videos and documents to try to implement this but keep failing! Any help would be gratefully received.

Just quick background. I was tasked with creating a survey for bats. Originally I was going to create this in field maps but given that select multiple isn't supported I I have read about the work around but that isn't an ideal solution). There is historical data and data is collected at known roosts once or twice a year, so rather like an asset inspection, the questions for this part of the survey are based on a paper survey form. This year two new sets of data need to be collected related to threats to the roosts and measures that should be implemented to prevent any decline in bat numbers at a roost.

I created a point feature layer in Pro with all the historical data and then tables for the survey, threats and measures. Potentially there are multiple threats and measures at a single roost. I created relationship classes for the tables to the feature layer based on GlobalID and GUID fields. The feature layer was published to AGOL online and configured.

I created a form from the feature layer in Survey123Connect. There is a need for repeats for the both the Threats and Measures questions. I can't publish the Survey, I have made a mistake somewhere possibly many a but can't track it/them down.

When I try to publish to AGOL form Survey123 Connect I get this error:

Connect error.PNG

I am also attaching the Survey123Connect form.

You will see there is hidden GUID field associated with each part of the form that is based on a related table. I tried with just a single GUID field after the final question but that didn't publish either. It got to the same point as above. I couldn't find any information online or examples of people having multiple related tables. Perhaps the answer is to have three Survey 123 forms each print to the same feature layer and the associated related table. That is only a guess though.

Thanks in advance for any pointers and apologies for rookie errors.

LESSER HORSESHOE BAT_copy.xlsx

JeffreyThompson2_1-1728674843841.png

Find more posts tagged with

Accepted answers

All comments

JA7

You should only have a single line on your Settings tab pointed to the parent layer. The children tables are "added" by insuring the table name matches the corresponding repeat name in the survey tab.

The only time you would have a child table in the Settings tab is if your survey was only populating that child table and ignoring the parent table. In that situation the child table would be the only line on the Settings tab.

Working with existing Feature Services

PeterMcdonnell_1968

Hi Jennifer,

Thanks a million for taking the time to look at my question. This has been wrecking my head. I got pulled onto something else today so I will try out your advice first thing tomorrow.

Again many thanks,

Peter

MichaelZeno1

But what if you only want to populate the child tables but you have 2 of them? Would you have to use both child names in the settings tab?

JA7

No. You can only directly populate a single child table.

PhillipHinz_1

In the above case, he needs to relate two child tables (ConservationMeasures and PressureandThreats) to one parent table (Lesser_Horseshoe_Bat_Surveys). Jennifer said to only put the parent in the Settings tab. Then put in one child table name (ConservationMeasures) into the name column for the "begin repeat" row (as part of the Begin Repeat & End Repeat sequence). That would then populate the first child table.
Then the second table would be populated with a second Begin Repeat & End Repeat sequence.
So doesn't that mean two child tables are being populated in sequence?

PhillipHinz_1

@Fern_YT I never was able to get the Survey123 Connect form to publish using regular relates. I had to use relates with Global ID and GUID. The parent was a line feature class with multiple child tables. I couldn't get it to work if I used a table as the parent. My original idea was to use a Project Table with multiple child feature classes (somethings in the project were lines and other things polygons). I never figure out why this didn't work.
So you might need to use the GlobalID and GUID rather than your plot_ID.

Fern_YT

Thanks - I switched everything to globalid and guid and still am having issues so I started a new post. Really appreciate your help!

PhillipHinz_1

Great Chris! See my post to the new post. you are doing the same problem-solving steps that I did - so this is completely normal.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.