Set up field dependencies
- 2 Min.
After fields are configured, you can set up field dependencies between those fields to enforce data entry rules and guide users toward accurate submissions. Field dependencies reduce errors and ensure your organization's policies are followed consistently, without requiring approvers to chase down missing information and show fields only when relevant.
Scenario
Ester has recently added project numbers and project billable to her configured fields for expenses. However, some projects require billing and others not. Let’s see how she sets up field dependencies so that reporting on expenses can be differentiated at time of submission.
To optimize the set up for field dependencies, take the following steps:
- Search for and open Configured Fields.
- On the action bar click on Field Dependencies and select New.
- On the Field Type dependency Card, set your condition and expectation, please see the table below explaining the rules and expected behaviours when selecting fields.
| Field | Description |
|---|---|
| When Field Type | The "trigger" field. When this field is filled in, the dependency activates, it must be a Configured Field. |
| Condition | Defines when the rule fires. Choose Has a specific value or Has any value. |
| Value | Only required if Condition is set to Has a specific value. Specifies which value triggers the rule. |
| Then Field Type | The field the system is expected to act on when the condition is met. Must also be a Configured Field. |
| Expectation | Defines what is expected of the reference field. Options here are Must have a value, Must have a specific value, or Must have no value. |
| Expected Value | Only required if Expectation is set to Must have a specific value. Specifies what value the reference field must contain. |
| System Created | Checked automatically if this dependency was generated by the system (not manually created). |
| Disabled | Checked automatically if a conflict is detected during a Consistency Check and a reason is provided. |
- Fill in the Field Type Card to your condition and expectation rules for the expenses and select Close to finish the set up.
- On the action menu click on and run a Consistency Check and validate your dependency rules do not have any conflicts.