Applicable plans
Sprout Blossom Garden EstateForest


When it comes to setting up L/C/A/D fields on Freshsales, there are always instances when users may want to set up customized fields that are relevant only to the dropdown option that is chosen. This is known as Field Dependency and can help users set behavior of another field based on the option chosen.



How does it work?

Field Dependency is set between two fields – Controlling field and 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.

    Fields that can be dependent fields: Custom fields of any field type.


Based on the value selected in controlling field, dependent field can be made dynamic.


Note:  Both default and custom fields can be controlling fields. However, dependent fields can only be custom fields.


Let us assume that you chose the outcome of a deal between won or lost; choosing the option 'won' presents you with set of options that allows you to pick reasons for why the deal was successful.

Refer below to learn how this can be done:

TOTAL STEPS: 6

QUICK STEPS:  Admin Settings > CRM Customizations > L/C/A/D Fields > Field Dependency > Controlling fields > Dependent fields > Add Dependency > Save

TIME TAKEN: ~ 14 Min


DETAILED STEPS:

  1. On your Freshsales application, head to the Admin settings button  and click the same.

  2. On the Admin settings page, scroll down to the CRM Customizations row and click on Deal Fields.


  3. On the Deal fields page, click “” to create a two custom fields, one with the title “Won/Loss” and the other with the title “Reasons”.

    Note:  

    • 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 user will not be able to access the dependency screen.

    • If the account is upgraded, the dependency will be listed in deactivated state

    Won/Loss:


    These will be the Controlling fields.

    Reasons:

    These will be the Dependent fields.


  4. Upon saving the custom fields, click the button. This opens a dedicated page. On this page, click the button.

  5. 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 “Won” and “Loss” as the controlling fields.


    - Now select the respective Dependent fields for both the controlling fields.

    Selecting dependent fields for “Won”:



     

    Selecting dependent fields for “Lost”: 




  6. Hit Save to save your field dependency settings. Check your Deal fields in Admin settings to verify if your field dependency is active.


  7. You can also enable/ disable the dependencies by simply clicking on the toggle under the Field dependency page.


Note:

  • Users will have a limit of 10 field dependencies to create per entity 

  • User can create a maximum of 5 level of field dependencies


FAQs


1. What is the impact area across app?


Feature

Impact on controlling fields

Impact on dependent fields

Column Customization

No impact; the field will be treated independent

No impact; the field will be treated independent

Filter

No impact; the field will be treated independent

No impact; the field will be treated independent

Reports

No impact; the field will be treated independent

No impact; the field will be treated independent

Territory

No impact; the field will be treated independent

No impact; the field will be treated independent

Lead Scoring

No impact; the field will be treated independent

No impact; the field will be treated independent

Export

No impact; the field will be treated independent

No impact; the field will be treated independent

Bulk Update

The field will be shown a toggle to display dependent field. When enabled the toggle will display the dependent field.

Note: The toggle will be disabled by default and will not display any dependencies

Only when the toggle is enabled will the dependent fields be displayed.

Note: When a bulk update is made, validation will not be applied and the field will be updated even if the record does not match the field dependency.

Workflow

No impact; The field will be updated independently.

No impact; The field will be updated independently.

Note: When a bulk update is made, validation will not be applied and the field will be updated even if the record does not match the field dependency.

Import

The controlling field will be saved without validation.

If value of dependent field does not match with value of controlling field, the import will save the value without validation. But the value will not show up in the form as the dependency is not matched.

Webforms

As of now, field dependency is not supported on Webforms.

As of now, field dependency is not supported on Webforms.


2. What happens when 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 choose “Won”, then the field mandate will not be applied.    


3. What happens when an account is downgraded to blossom or sprout?

The feature 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.