How can I set up dependencies within an input form for my survey? (Step 3)

Learn how to create dependencies between different input fields within an input form.

1.	Click on the input field that you want to make dependent on another input field(s).
2.	Go to the "Dependencies" tab in the edit mode.
3.	Select the input field on which the current question should be depend. All possible database labels of the input fields are shown via a dropdown list. You can also search for them by entering the desired database label.
4.	Select the condition.
5.	If needed (e.g. for "is equal to"), you can now select the option of the other input field to which the dependency should refer.
6.	Click on the button "Add dependency".
7.	Don't forget to save the whole input form again in the upper right corner. Otherwise the dependency will not be saved!
8.	If you set more than one dependency for this question, you can choose between the different types.
	Two options are available here: AND or OR. If you select AND, you tell the system that this question should only appear if ALL of these criteria are met. If you select OR, you tell the system that this question should appear if at least ONE of the criteria below is met. Per default the option is set to "AND". When adding more than one dependencies, make sure to adjust the option as needed. Currently, a combination of both AND/OR dependencies is not offered. Only one of these options can be used.
9.	You can set more than one dependency on one specific field or combine dependencies based on separate fields. For example: Field C should become visible if Field A = yes AND Field B = not empty

⭐ Fun facts:

1. You cannot save circular conditions.
2. You can make a "rich text" field dependent on other fields – but not vice versa – because the "rich text" is not an input field.
3. You can make a "table" input field dependent on other fields, but not vice versa.
4. To learn more specifics on the definition and use of each input field type refer to the following article: Which types of input fields exists and how do I use them correctly?
5. You can apply dependencies to make a field visible on a certain condition or invisible if some/all conditions are not met. The more suitable approach depends on your project requirements.
6. Required fields hidden by a dependency are not considered "missing" and are not included in the completion % of (missing) required fields.
7. The dependency options vary based on the type of input field you are referring to.
8. If two "Date" fields are available, you can base the dependency on the comparison of these two "Dates".
   1. For example: Show Field A if "Date 1" = "Date 2"
   2. "Date" fields can only be compared with "Date" fields, not other input field type, including "Date and time".
   3. "Numbers" fields can be compared with "Numbers" fields or "Slider" fields or "Smart Field(s)" with numeric output and vice versa.
9. Consider using the "not equal to..." condition if one specific option shall not trigger your dependency:
   1. For example: Create dependency on Field A = "a, b, c, d", but not = "e"
      1. use condition Field A is not equal to "e"  instead of  = a OR = b OR = c OR = d
      2. add condition AND Field A = not empty to trigger your dependency on actual entries only (except "e")
10. Always test your dependency set up using the Preview function (button located on the top right corner of the form)