When Changing the Set of Values of a Custom Field of a Smart Process, New Invoice, or Document onCrmTypeUserFieldSetEnumValues
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.
Scope:
crmWho can subscribe: any user
The event ONCRMTYPEUSERFIELDSETENUMVALUES will trigger when the set of values of a custom field of the list type enumeration is set or changed for a smart process, a new invoice, or a document for signing.
The event arrives both when the list of values is edited in the interface and when the userfieldconfig.add and userfieldconfig.update methods are called.
A single action on a list-type field sends one or two events:
- when a field is created together with a set of values, the handler receives onCrmTypeUserFieldAdd and
onCrmTypeUserFieldSetEnumValues - when the field settings are changed together with the set of values — onCrmTypeUserFieldUpdate and
onCrmTypeUserFieldSetEnumValues - when only the set of values changes — a single
onCrmTypeUserFieldSetEnumValuesevent
These cases cannot be distinguished by the contents of data: all events carry the same three keys. If the handler is subscribed to both onCrmTypeUserFieldUpdate and onCrmTypeUserFieldSetEnumValues, guard against processing the same ID twice. All cases are covered in the Which Events Arrive Together section.
Events will not be sent to the application until the installation is complete. Check the application installation
What the Handler Receives
Data is transmitted as a POST request
{
"event": "ONCRMTYPEUSERFIELDSETENUMVALUES",
"event_handler_id": "713",
"data": {
"FIELDS": {
"ID": "6977",
"ENTITY_ID": "CRM_13",
"FIELD_NAME": "UF_CRM_13_1742999523"
}
},
"ts": "1742999524",
"auth": {
"access_token": "s6p6eclrvim6da22ft9ch94ekreb52lv",
"expires_in": "3600",
"scope": "crm",
"domain": "some-domain.bitrix24.com",
"server_endpoint": "https://oauth.bitrix.info/rest/",
"status": "L",
"client_endpoint": "https://some-domain.bitrix24.com/rest/",
"member_id": "a223c6b3710f85df22e9377d6c4f7553",
"refresh_token": "4s386p3q0tr8dy89xvmt96234v3dljg8",
"application_token": "51856fefc120afa4b628cc82d3935cce"
}
}
|
parameter |
Description |
|
event |
Symbolic code of the event. In this case — |
|
event_handler_id |
Identifier of the event handler |
|
data |
An object containing information about the custom field whose set of values has changed. Contains a single key |
|
data.FIELDS |
An object containing the identifiers of the custom field whose set of values has changed. The structure is described below |
|
ts |
Date and time of the event sent from the event queue |
|
auth |
Object containing authorization parameters and information about the account where the event occurred. The structure is described below |
Parameter FIELDS
|
parameter |
Description |
|
ID |
Identifier of the custom field whose set of values has changed. Pass it together with |
|
ENTITY_ID |
Identifier of the object the custom field belongs to: The The values are described in the Which Objects Trigger the Events section |
|
FIELD_NAME |
Symbolic code of the custom field, for example |
The event does not pass the set of values itself. The list of values is returned by the userfieldconfig.get method in the enum key. This method requires the userfieldconfig scope in addition to the crm scope the application subscribes to the event with.
Parameter auth
Required parameters are marked with *
|
Name |
Description |
|
access_token |
Authorization token OAuth 2.0 |
|
expires_in |
Time in seconds until the token expires |
|
scope* |
Scope under which the event occurred |
|
domain* |
Address of Bitrix24 where the event occurred |
|
server_endpoint* |
Address of the Bitrix24 authorization server needed to refresh OAuth 2.0 tokens |
|
status* |
Status of the application that subscribed to this event:
|
|
client_endpoint* |
Common path for REST API method calls for Bitrix24 where the event occurred |
|
member_id* |
Identifier of Bitrix24 where the event occurred |
|
refresh_token |
Token for extending authorization OAuth 2.0 |
|
application_token* |
Token for secure event handling |
Authorization tokens are not always passed to the event handler. If the hit that initiated the event could not be linked to a specific Bitrix24 user, the tokens are not passed. Always check the contents of the auth key in the code.
It is recommended to store tokens obtained earlier during the application installation. Use them when working with the application interface in the form of embeds, widgets, and so on.
Continue Learning
- Event Handler
- Register a New Event Handler event.bind
- Overview of Events When Working with Custom Field Settings
- When Adding a Custom Field of a Smart Process, New Invoice, or Document onCrmTypeUserFieldAdd
- When Updating a Custom Field of a Smart Process, New Invoice, or Document onCrmTypeUserFieldUpdate
- When Deleting a Custom Field of a Smart Process, New Invoice, or Document onCrmTypeUserFieldDelete