Set up field dependencies in Salesforce to use within the Formstack for Salesforce app. Supporting dependent picklists drastically reduces manual setup through our conditional rules, which can be really overwhelming, and gives you more time back into your day! Learn more on Salesforce Dependent Fields below.
Common Use Cases
- Auto-parts ordering form: Car Year -> Make -> Model -> Parts
- Insurance Claim: Category -> Insurable Service -> State -> Approved Providers
- Education Class Feedback or Change Request: School within University -> Department -> Semester -> Course -> Cohort -> Professor/T.A.
- Location: Region -> Country -> State -> City
- HR: Protected Status declaration: Country -> State -> Protected status designation
Helpful Links
- https://trailhead.salesforce.com/en/content/learn/projects/customize-a-salesforce-object/picklists-field-dependencies
- https://www.salesforcetutorial.com/field-dependency-in-salesforce/
- https://help.salesforce.com/s/articleView?id=sf.fields_dependent_field_considerations.htm&type=5
- https://www.youtube.com/watch?v=7X-q8E2Q_Jo
Capabilities
- Supported Controlling field types: Checkbox, Picklist (single-select and variations - Radio Button List, Searchable Picklist)
- Supported Dependent field types: Picklist (single-select and variations - Radio Button List, Searchable Picklist), Multi-Select Picklist (and variations - Multi-Select Tag List, Multi-Select Checkbox Tag List, Checkbox List)
- Ability to add a field to a form without adding its controlling or dependent fields. Fields behave as if no dependencies are defined.
- Any number of dependent and controlling picklists, as well as any level, can be added to the form and should be supported automatically. E.g. a controlling picklist can be added with its dependent picklist and that dependent picklist can be a controlling picklist of another dependent picklist.
- Dependent picklists don’t have any values available if the controlling picklist value is not selected.
- Picklist values can be customized by hiding some values but no additional values can be added.
- If a controlling field value is changed and the dependent one is no longer valid, then the dependent picklist is cleared.
- Support for using dependent fields in rules in the same way as if they had no dependencies configured.
- All picklist values are available in rules for Dependent Picklists regardless of dependencies configured, other rules, or what is set up in field settings.
- On form execution, dependency configuration takes precedence, then any rules in our Forms app are applied to further filter down available values.
- Dependent field values can be merged into alerts.
- Dependent field values can be used in payment settings.
- Dependent field values can be used with Documents integration.
- Available in all paid pricing plans including NativeCloud.
- Forms with pre-existing fields that have a dependency relationship defined but built prior to this feature will continue to work with no change in behavior. Fields must be refreshed to load the field dependencies defined in salesforce. If the field is removed, then the browser page should be refreshed before adding the field back onto the form.
- Able to set a default value on a controlling field which will automatically set the correct values on dependent fields.
Limitations
- The Salesforce user accessing the app and the Primary User need API Access permissions to perform REST Calls so that Dependent Field configuration can be loaded.
- A Remote Site Settings from the customer org domain is needed. This is automatically added by the app on Form Menu load but it may fail and must be added manually.
Have any further questions? We’re here to help! Please reach out to support@formstack.com for additional assistance.
Are you looking for consultation or help building out your use case(s)? Team up with third party Certified Formstack experts to bring your custom projects to life.