What this solution does
The 5 Corners module 'Dependent Fields and Lists in CRM' addresses the issue of overloaded deal cards. Standard forms often contain dozens of fields, causing managers to fill in irrelevant data, miss critical information, and compromise data integrity.
The solution hides unnecessary fields and displays only relevant ones. You define dependency rules in the administrative section without involving developers or modifying code. The form dynamically restructures itself: hidden sections disappear, required fields appear exactly when needed, and option lists in child fields automatically narrow down to valid values.
The functionality includes three key mechanisms:
Display fields upon filling the parent field. For example, selecting a 'Deal Source' automatically reveals a block of fields specific to that source.
Display fields based on specific list values. Each option of a parent field triggers its own unique set of child fields.
Value-based mandatory field logic. A child field becomes mandatory only when a specific parent option is selected. The interface displays a mandatory indicator, and server-side validation blocks saving the card if the rule is violated. A classic example: selecting 'Refusal' in the 'Call Result' field makes the 'Refusal Reason' field mandatory, while hiding it completely for all other options.
The module enables dynamic management of fields in CRM cards. The list of available values for a child field is automatically narrowed based on the parent field's selection, either through manual mapping or by querying a related information block.
Rules can apply not only to individual fields but to entire form sections, allowing them to be shown or hidden as a group.
Full support is provided for all core entities: leads, deals (including pipelines), contacts, companies, and smart processes. A unique set of fields can be defined for each pipeline stage, making the Kanban board adaptable rather than uniform. Dependency rules function correctly during stage transitions.
An integrated help section on the settings page provides a breakdown of all dependency types and tooltips for each column, eliminating the need to consult external documentation. Configuration is stored in the portal database; the rules table can be preserved when uninstalling the module to restore settings upon reinstallation.
System requirements:
Bitrix24 (on-premise version) with the CRM module installed.
PHP version: 8.2 or higher.
Database: MySQL and PostgreSQL (the module is compatible with both editions).
General iT can connect “5 CORNERS. Dependent Fields and Lists in CRM”, install and configure the module, and make sure the integration works correctly.