When it comes to setting up Contacts, Accounts, and Deal fields on Freshworks CRM, there are always instances where you may want to set up customized fields that are relevant only to a dropdown option chosen in another field. This is known as Field Dependency and can help you set the behavior of another field based on the option chosen.
How does it work?
Field Dependency is set between two fields – a controlling field and a dependent field.
- Controlling Field: Controlling fields are those which control the available values in one or more corresponding dependent fields.
Fields that can be controlling fields: Both Default and Custom fields of type: - Dropdown - Checkbox - Radio Button
- Dependent Field: Dependent fields are those which display values based on the selected controlling field value.
Fields that can be dependent fields: Default and Custom fields of any type
Based on the value selected in the controlling field, dependent fields can be made dynamic.
Let us assume that you chose the outcome of a deal between won or lost; choosing the option 'won' presents you with a set of options that allows you to pick reasons for why the deal was successful.
Refer below to learn how this can be done:
- Click Admin settings , scroll down to the Sales Force Automation (SFA) section and click on Deal Fields.
- On the Deal fields page, click to create a custom field with the title “Lost to competition”.
- You can also create dependencies between existing fields.
- A controlling field can have multiple dependent fields.
- However, a dependent field can have only one controlling field.If an account is downgraded, all the dependencies will be deactivated and users will not be able to access the dependency screen.
- If the account is upgraded, the dependency will be listed in deactivated state
This field will be the Dependent field and will carry the names of all of your competitions. This field will be mapped to the controlling field ‘Lost Reason’
Lost to competition
- Upon saving the custom fields, click the Define Field Dependencies button. This opens a dedicated page where you can configure field dependencies. On this page, click the . button
- Clicking the Add dependency button opens a form titled “ADD NEW DEPENDENCY”. You can use this form to set dependencies between different fields.
- Proceed by selecting a Controlling field. In this case, we’ve chosen “Lost to competition”
Selecting the controlling field and the options from the field:
- Now select the respective Dependent fields for the controlling field.
Selecting dependent fields for “Lost to competition”:
Turn on the the Mark as required * toggle to make the field dependency required. Whenever a field is marked required, the user cannot submit the form without filling the field.
- Click to save your field dependency settings. Check your Deal fields in Admin settings to verify if your field dependency is active.
You can also enable/ disable the dependencies by simply clicking on the toggle under the Field dependency page.
- Users will have a limit of 30 field dependencies to create per entity in the Estate plan, 60 field dependencies in Forest plan.
- User can create a maximum of 10 level of field dependencies
1. What is the impact area across app?
2. What happens when a dependent field is marked as mandatory?
If the dependent field is marked mandatory, the mandatory check will be made only when the dependent field is shown on the form based on the controlling field value.
For example, let us assume that a controlling field has two choices “Won” and “Lost” where the choice “Lost” is connected to the dependent fields “Reason for loss”, marking the field “Lost” mandatory would make the field “Reason for loss” mandatory. However, if the user chooses “Won”, then the field mandate will not be applied.
3. What happens when an account is downgraded to blossom or sprout?
Field dependency is not available for the Sprout and Blossom plans. So whenever an account is downgraded to Blossom or Sprout, the field dependencies are automatically deactivated. However, the created dependencies will not be deleted and will be a part of the account. Once the user accounts are upgraded back to higher plans, the field dependencies can be reactivated by the user.