FORMBUILDER DEPENDENCY PATH
WHAT'S COVERED IN THIS ARTICLE?
- What are subforms?
- What are option lists?
- What is subform/option list dependency?
- Understand the element path
The subform element can be used to create sub-section of a larger form. It is more efficient to create smaller "subforms" and place them inside a parent form. Subform elements can be configured to allow for only a single or multiple paging.
An option list is just what it sounds like; a list of options the user can choose from when collecting data. An Option List can be used with the following element types:
Subform/Option List Dependency
This feature allows you to see to see which elements and forms your Subforms are attached to across your profile. The subform dependency path displays the relationship from the top layer (parent form) step-by-step until it ends on the element that will be impacted by deleting the form. The path can be multiple layers deep depending on form structure and the use of subforms.
Each line starts with a form table name and ends with an element data column name.
In this example, the dependency path shows that form "photo".
- inspection has a subform element named structure_condition which uses the form sec1_structure_condition. And within sec1_structure_condition it has a subform element called picture1 that uses the form photo.
- Note that it will show if multiple subform elements even if they are in the same form, for example picture1 and picture2.
If we make changes to or delete photo, all of the listed forms and elements will be affected.