Articles in this section
Authenticate Emails with SPF, DKIM, and SenderID Auto-forwarding your emails to Vtiger Automate Outgoing Emails in Email Settings Automation - Approvals Automation - Assignment Rules Automation - Multi-path Workflows Automation - Scheduled Workflows Automation - Scheduler Automation - Standard Workflows Automation - Webforms Automation - Workflow Action - Create Event Automation - Workflow Action - Create Records Automation - Workflow Action - Create Task Automation - Workflow Action - Invoke Custom Function Automation - Workflow Action - SMS Task Automation - Workflow Action - Send Mail Automation - Workflow Action - Update Fields Automation - Workflow Action - Webhook Automation - Workflows - Vtiger Expressions Configuration - Business Hours Configuration - Company Details Configuration - Consents Configuration - Customer Portal Configuration - Maps Configuration - Usage Details Configure Encrypted data fields in Vtiger CRM Configure Picklist Dependencies Considerations for Deactivating Vtiger Users Control Fields and Record Displays using Configuration Editor Create Reminders for Records and Inbox Create a field of a Grid type Customize your self-service portal theme using CSS styles Dealing with Currencies and Taxes Enable Desktop Notifications on Chrome Web Browsers Extensions - Extension Store IMAP Configuration - 2-way sync between Vtiger and IMAP providers Inventory - Payments and Subscriptions Inventory - Tax Management Inventory - Terms and Conditions Login to Vtiger on SSO SAML using ADFS Mailroom Functionality in Different Scenarios Manage Multiple Currencies Marketing & Sales - Forecast and Quota Settings Marketing & Sales - Pipelines and Stages Marketing and Sales - Deal to Project Mapping Marketing and Sales - Lead Conversion Data Mapping Marketing and Sales - Profile Scoring Module Management - Labels Editor Module Management - Module Numbering My Preferences My Preferences - Calendar Settings My Preferences - My Tags My Preferences - Notification Preferences SAML Support in Vtiger CRM Set up Mailroom Settings - Configure Module Settings Settings - Create Dynamic Fields and Layouts Module Management - Creating a Relationship Between Modules Settings - Customize Records and Fields for your Business Settings - How to set email autoresponder to Webform submission? Settings - Left Menu Settings - Manage Global Picklists in Vtiger Settings - Set up your Support Team Settings - Start Up Page Settings - Working with Picklist Values Module Management - Module Builder Support - SLA Policies Troubleshooting Login Issues Unsubscribe your Email User Management - Authentication User Management - Encrypted Field Access Logs User Management - Groups User Management - Login History User Management - Profiles User Management - Roles User Management - Settings Log User Management - Sharing Rules User Management - Users User Management - Vtiger Support Access Vtiger Buzz - Chrome Extension for Notifications Vtiger Implementation wizard Vtiger Language Support Websense - Trackers Websense - Widgets Configuration - Storage Guard Adding a local DNS Entry Adding Additional Hidden Fields to a Webform Duplicate Prevention in Modules Module Management - Modules Module Management - Module Layouts & Fields

Configuring Dependent Fields and Blocks for Modules

This article will help you configure dependent fields and blocks in modules.
Rashmi Kashyap
30 Mar, 2021 - Updated 5 months ago


With Dependent Fields and Blocks, you can define dynamic business rules at the field level. They are activated only when the configured condition is satisfied. Additionally, you can set rules to mark a field as mandatory or read-only.

For example, you can define a condition where the Location field must be revealed only when you fill out the Phone Number field in a record.

Watch a video to understand the working clearly.


Note: Dependent Fields and Blocks is supported only in the following screens:

  • Detail View
  • Edit View
  • Mass Edit
  • Workflows (Create record or Update fields action)

Working of Dependent Fields and Blocks

In this section, you will learn about the functionality of Dependent Fields and Blocks in Vtiger CRM. But before you dive into the working of this setting, it is essential that you complete these prerequisites:

  • Set up Blocks and Fields in Module Layouts & Fields > Detail View Layout
  • Define the Picklist or Checkbox fields that will be later used as a Trigger field

We will explain the functionality in a bottom-up approach with the following diagram:

  1. Firstly, the controller (Trigger) field is activated. 
  2. Next, the specified conditions are checked and matched with the Trigger field.
  3. Lastly, based on the access rules, the Dependent Fields and Blocks are shown. 

Consider this example.
A customer sells insurance with Product A and Product B. He has 120 custom fields for Product A and 120 custom fields for Product B. The customer’s requirement is straightforward.  They don’t want Product B’s fields to be visible while working on Product A and vice-versa.

Here is the solution.
With the help of Dependent Fields and Blocks, we can achieve the above requirement. When the customer selects Product A from a Picklist or Checkbox field, the fields related only to Product A are shown, and when he selects Product B, the fields related only to Product B are shown.

Configuring a Dependency

Once you understand the functionality, configuring the dependency is quite an easy task. We have divided the entire process into four steps for better understanding. Read on...

Step 1: Accessing the Dependent Fields and Blocks screen

This is the primary step in using which you can go to the Dependent Fields and Blocks screen.

  1. Log in to your CRM account.
  2. Click the User Menu on the top right corner of the screen.
  3. Click Settings.
  4. Go to Module Management.
  5. Click Module Layouts & Fields.
  6. Select the module for which you want to configure dependent fields.
  7. Click the Dependent Fields/Block tab.

Step 2: Adding a new dependency

You can add both block dependency and field dependency here.

If you choose a block dependency, you can add multiple child field dependencies under it. You cannot do the same for a field dependency.

  1. Click the +New Dependency button. 
  2. Click the drop-down under the Dependent Fields/Block column.
  3. Select a block or field.
  4. If you wish to add a child field dependency under a block, click +New Field Dependency

Step 3: Setting the access rules

Once you decide on the dependent blocks and fields, you must specify the user’s action on the field.

  1. Click the drop-down under the Access column.
  2. Choose the access rule. For block dependencies, the default and only option is Show, where we show the block. For field dependencies, you can choose among the following options:
    • Show (Read + Write) - Show the field with a read and write access.
    • Show (Read + Write & Mandatory) - Show the field and make it mandatory with read and write access.
    • Mandatory - Make the field mandatory.
    • Show (Read only) - Show the field with only read access.


  • If you wish to add another action for the same dependency, click +New Action and repeat steps 12 and 13.
  • Fields that are defined as mandatory at the module level (in Detail View Layout) are not affected by the access rules set in Dependent Fields and Blocks. This applies only to Show (Read + Write & Mandatory) and Mandatory access rules.

Step 4: Specifying the conditions

Once you add the access rules, you must mention the trigger field and its value. The trigger is a condition that must be satisfied for the dependent fields/blocks to be shown.

  1. Click the field drop-down under the Condition column.
  2. Select a field. Only picklists and checkboxes fields will appear here.
  3. Click the operator drop-down. 
  4. Select either equals or Not Equals.
  5. Enter the picklist value in the text field.
  6. Click Save to save the dependency.


  • If you wish to add another condition for the same dependency, click +Add Condition and repeat steps 14-18.
  • You can delete a condition by clicking the Delete icon next to the condition.

You can edit or delete an existing dependency by hovering over the dependency.

Handy Hint: If you see a alt text icon in the List View, it represents that the field is not shown due to a dependency rule.


Here are a few limitations that you must be aware of:

  • A dependent field cannot be a controller (Trigger) field.
  • If you move the Trigger field to a different block in the Detail View Layout after setting up a dependency rule, you must reset the rule associated with the Trigger field. 
  • When a Trigger field is disabled, the condition will be in a Strikeout mode.
  • Dependent fields will slow the list views. If List View columns include dependent fields, then it could take more time to load the list.
Related articles
Module Management - Labels Editor Module Management - Module Numbering Duplicate Prevention in Modules
Home Privacy Policy Terms of Service Security Center Policy & Legal Center Contact Us
© Copyright 2021 Vtiger. All rights reserved.
Powered by Vtiger
Facebook Twitter Linkedin Youtube