Sections in the CRM Detail Form: Overview of Methods
If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect to the MCP server so that the assistant can utilize the official REST documentation.
The sections in the CRM detail form display information about the entity. For example, in a deal detail form, there may be sections about the client, order, and delivery terms.
The methods crm.item.details.configuration.* manage the sections of the detail form. You can save user-specific settings or set a uniform view for the entire company.
Quick navigation: all methods
How to Work with Form Settings
- Define the CRM entity type using
entityTypeId. You can find the identifiers in the sections System CRM Types and Smart Processes. - For deals and smart processes, specify the funnel in the
extrasparameter (dealCategoryIdorcategoryId). You can retrieve the list of funnels using the method crm.category.list. - Obtain the current configuration using the method crm.item.details.configuration.get.
- Save changes using the method crm.item.details.configuration.set or reset the settings to default values via crm.item.details.configuration.reset.
- To make the common configuration mandatory for all users, use crm.item.details.configuration.forceCommonScopeForAll.
Scope of Settings
The scope parameter defines whose settings will be changed.
|
Scope Code |
Purpose |
|
|
Personal configuration for a specific user. Used by default |
|
|
Common configuration for all Bitrix24 users |
To work with personal settings, standard user permissions are sufficient. Changing common or other users' settings requires administrator rights.
Relationship with Other Objects
CRM Entity Type. The settings of the detail form apply to a specific entity type through the entityTypeId parameter. For system objects, use identifiers from the section System CRM Types, and for smart processes, refer to the section Smart Processes.
Funnels. For deals and smart processes, the view of the detail form may differ across different funnels. Specify the funnel identifier in the extras parameter. If the parameter is not provided, the system uses the default funnel.
User. Personal settings of the detail form are tied to the user through the userId parameter when scope = 'P'. If userId is not provided, the methods use the user executing the request. You can obtain the user identifier using the method user.get.
Common Causes of Errors
- An unsupported CRM entity type has been specified.
- Incorrect
extrasparameters have been provided for the selected type. - Insufficient permissions to modify the common configuration.
Overview of Methods
Scope:
crmWho can execute the methods: depending on the method and parameters
Configuration Management
|
Method |
Description |
|
Returns the current settings of the detail form sections |
|
|
Saves changes to the detail form section settings |
|
|
Resets settings to default values |
|
|
Makes the common configuration mandatory for all users |