Select to view content in your preferred language

Survey123 tables

547
4
Jump to solution
02-25-2026 08:26 AM
SueBoelk2
Occasional Contributor

I’m unsure of the correct approach, so please advise.

(It is understood that I will likely have to make table changes in Pro to make this work (so that is a given.))

Here is the situation:

We have a main form that holds the point feature and questions (It will be used in the field). The inspector goes to a seed seller, gathers information and photos then returns to the office and uses the form with 4 tables to complete his inspection by filling out:

Fill out Part 1 and Part 2 – for Farm or Non-Farm Seed.

Fill out Part 1 and Part 3: for AG & Grass Seed.

Fill out Part 1 and Part 4: for Vegetable seed.

When the inspector gets back to the office the point feature will be opened to view the field inspection data and then go to fill out the relevant parts (ie. Pt 1 & Pt 2, etc. depending on the type/use of seed).

Is this feasible: Have a radio button in Part 1 where if the group Farm or Non-Farm Seed is clicked the inspector will see only Part 1 and Part 2 or if Veg Seed is clicked the inspector sees only Part 1 and 4 or Part 1 and 3 only for Ag & Grass Seed.

[I’ve tried doing calculations, relelvant expressions, and body::esri:visible to hide/show tables but w/o success. however I welcome any suggestions as I am still in the early stages of learning ].

P.S. The form with four tables are related to the main table pt feature and will, when published, be used in Experience Builder (used in the office) to do what has been described above (fill out Part 1 and Pt 2, etc.).

Thanks for your patience and help.

 

 

0 Kudos
1 Solution

Accepted Solutions
Neal_t_k
MVP Regular Contributor

To build off of what @DavidSolari is saying and from your examples, You may want to make one form to build your feature service.

Main Form -> in a repeat have Group1, and then nested in group (repeat) 1 have a repeat for Group 2, 3, 4.

If you let Survey123 build the feature, you would still end up with the 1 feature and 4 tables, but your relationships would be automatically built.

Also once that is built you could build additional forms to accomplish your workflow.  Build 1 form to submit data in the field. And the second form to fill in additional info in the office. The second form could be formatted to pull from the inbox, which would preserve you relationships of your main form to the tables.

Use relevancy in the second form to show appropriate tables for Groups 2,3,4

View solution in original post

0 Kudos
4 Replies
ZenMasterZeke
Frequent Contributor

Not sure what exactly you're looking for here. I know you attached 2 files, but is this all supposed to be in one form, where the initial data is gathered in the field and then the same survey form is completed in the office? Or do you have the field form completed, then want to fill out other surveys (or some other app) based on the values in the first survey?

1. Survey 1 started in the field -> completed in office

2. Survey 1 completed in field -> other surveys/other apps completed in office based on Survey 1

3. ??

0 Kudos
SueBoelk2
Occasional Contributor

Zen Master Zeke- Thanks for your reply.

In answer to your question: I have the field form completed and then want to fill out the other surveys based on the values from the first survey.

2. Survey 1 completed in field -> other surveys/other apps completed in office based on Survey 1.

 

 

0 Kudos
DavidSolari
MVP Regular Contributor

If the 4 parts each have their own table in the service, what you can do is have "repeat" sections limited to one record each, this gives the appearance of a question group but saves the data in those separate tables. This help page gives a quick overview of how to associate a survey with an existing feature service, as long as your main point layer and all 4 table layers are in the same service this'll work.

0 Kudos
Neal_t_k
MVP Regular Contributor

To build off of what @DavidSolari is saying and from your examples, You may want to make one form to build your feature service.

Main Form -> in a repeat have Group1, and then nested in group (repeat) 1 have a repeat for Group 2, 3, 4.

If you let Survey123 build the feature, you would still end up with the 1 feature and 4 tables, but your relationships would be automatically built.

Also once that is built you could build additional forms to accomplish your workflow.  Build 1 form to submit data in the field. And the second form to fill in additional info in the office. The second form could be formatted to pull from the inbox, which would preserve you relationships of your main form to the tables.

Use relevancy in the second form to show appropriate tables for Groups 2,3,4

0 Kudos