Definition and Location of Field Dependencies:
Field dependencies are viewed in AppStudio and are by definition the other field(s) that are reliant on a given field, usually dependent fields are interlinked to one another by expressions. Although, in other respects Reports can be configured with fields that they are dependent on to work correctly, however such Reports are not included in the 'Field Dependencies' area.
Any field that has dependencies will be indicated by the atom symbol at the right hand side of the expressions box clicking on this will let you overview all dependent fields and open them directly in another tab if desired. Fields without any dependencies will not be marked by this symbol.
Clicking on any of the mentioned field ID's will take you directly to that Field in another tab.
The dependency indicator can also be found next to expressions in a Grid type field.
Clicking on any of the mentioned field ID's will take you directly to that Grid in another tab.
Field Dependency Uses:
- Perhaps the primary use of dependencies is determining the effect of deleting fields and whether this is appropriate when making changes to an App. It is a safety measure to ensure your App continues to function as it should and helps to prevent unwanted Expression Errors which stop your App from functioning.
- Also if you are a new builder to an App or are simply reminding yourself of the structure and flows of data within an App, dependencies provide a much faster way of overviewing this alternatively to manually tracking and tracing through.
Please sign in to leave a comment.