Option to add a form again

[YIK3S]

The picture below shows the list of questions once the user answers them I want an option to answer them, for multiple results. For example, if the user had 3 different tests they need to answer these questions three different times, I’m not how to add an add option to fill this part of the form again Please let me know

[SkrOYC]

mshello:

if the user had 3 different tests they need to answer these questions three different times

They can’t for some reason?
If you want to have just 1 record with three times the info taken from this form, I feel like you are wanting something wrong.
It’s better to have n amount of child records.

Could you explain better your idea or table schema?

[YIK3S]

This is at the end of the form, the user should be able to upload information related to all the tests in one app sheet submission, so for test 1 they only fill the unit weigh, cylinder size, age, and strength once. But if they had 2 tests I need an option to store test 1 info and add test 2 information.

[SkrOYC]

I get it, but that may not be the best option since you would need N number of columns for that, in general it’s a bad practice.
Make another table that just stores the values you showed above and add a column to reference to the main form that the user will upload.
Take a look at this:

help.appsheet.com

References Between Tables

Learn about references, when to create them, and how to use them so your data makes sense.

Expressing Ownership Between Tables

References can indicate not only that two tables are related, but that rows of one table should be owned by (or considered a part of) rows from another table. This is done by activating the IsAPartOf option in the Ref column structure. Typically, this should only be done in cases where rows containing the Ref column only make sense when associated with a row from the referenced table. For example, you may have a separate Order Details table for line items that reference an Order , but conceptually each entry should be considered “part of” an Order and shouldn’t exist independently (put another way, the Order record “owns” the Order Details that reference it).

There are several implications of enabling this ownership relationship:

1. Form views should allow users to add or update related rows that are a part of that row without leaving the form.
2. A form comprised of multiple rows should be treated as a single update.
3. If a row is deleted, any related rows that are a part of it should also be deleted (and again treated as a single update).

The first of these to take effect will be #1: System-generated reverse reference columns related to Ref columns marked IsAPartOf will appear in form views and allow users to view, add, and edit line items within the form view. The availability of these options is limited by the table or slice permissions (and until the final form is saved, pending adds can still be modified even if the table doesn’t allow updates).

You can tell AppSheet that the records from the new table are part of the main one, and the user will be able to add those N number of times directly from the main form