Update Custom Field of CRM Requisite
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 execute the method: any user
This method updates an existing custom field of the requisite.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
id* |
Identifier of the custom field. Can be obtained using the method crm.requisite.userfield.list |
|
fields* |
Set of fields — an object of the form |
Parameter fields
|
Name |
Description |
|
XML_ID |
External key. Used for data exchange operations. Identifier of the object in the external information base. The purpose of the field may change by the final developer |
|
SORT |
Sorting |
|
MULTIPLE |
Multiplicity indicator. Possible values:
|
|
MANDATORY |
Mandatory indicator. Possible values:
|
|
SHOW_FILTER |
Show in the list filter. Possible values:
|
|
SHOW_IN_LIST |
Show in the list. Possible values:
|
|
EDIT_IN_LIST |
Allow user editing. Possible values:
|
|
IS_SEARCHABLE |
Are field values included in the search. Possible values:
|
|
EDIT_FORM_LABEL |
Label in the edit form |
|
LIST_COLUMN_LABEL |
Header in the list |
|
LIST_FILTER_LABEL |
Filter label in the list |
|
ERROR_MESSAGE |
Error message |
|
HELP_MESSAGE |
Help |
|
LIST |
List elements. For more details, see the section Get Field Descriptions for Custom Field Type "Enumeration" (List) crm.userfield.enumeration.fields |
|
SETTINGS |
Additional settings (dependent on type). For more details, see the section Get Field Settings Description for Custom Field Type crm.userfield.settings.fields |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":235,"fields":{"EDIT_FORM_LABEL":"Category","LIST_COLUMN_LABEL":"Category","LIST_FILTER_LABEL":"Category"}}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/crm.requisite.userfield.update
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":235,"fields":{"EDIT_FORM_LABEL":"Category","LIST_COLUMN_LABEL":"Category","LIST_FILTER_LABEL":"Category"},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/crm.requisite.userfield.update
try
{
const response = await $b24.callMethod(
"crm.requisite.userfield.update",
{
id: 235,
fields:
{
"EDIT_FORM_LABEL": title,
"LIST_COLUMN_LABEL": title,
"LIST_FILTER_LABEL": title
}
}
);
const result = response.getData().result;
console.info(result);
}
catch( error )
{
console.error(error);
}
$title = "Category";
try {
$response = $b24Service
->core
->call(
'crm.requisite.userfield.update',
[
'id' => 235,
'fields' => [
'EDIT_FORM_LABEL' => $title,
'LIST_COLUMN_LABEL' => $title,
'LIST_FILTER_LABEL' => $title
]
]
);
$result = $response
->getResponseData()
->getResult();
if ($result->error()) {
error_log($result->error());
} else {
echo 'Success: ' . print_r($result->data(), true);
}
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error updating user field: ' . $e->getMessage();
}
const title = "Category";
BX24.callMethod(
"crm.requisite.userfield.update",
{
id: 235,
fields:
{
"EDIT_FORM_LABEL": title,
"LIST_COLUMN_LABEL": title,
"LIST_FILTER_LABEL": title
}
},
function(result)
{
if(result.error())
console.error(result.error());
else
{
console.info(result.data());
}
}
);
require_once('crest.php');
$title = "Category";
$result = CRest::call(
'crm.requisite.userfield.update',
[
'id' => 235,
'fields' =>
[
'EDIT_FORM_LABEL' => $title,
'LIST_COLUMN_LABEL' => $title,
'LIST_FILTER_LABEL' => $title
]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": true,
"time": {
"start": 1717769551.504986,
"finish": 1717769551.817433,
"duration": 0.31244707107543945,
"processing": 0.04784202575683594,
"date_start": "2024-06-07T16:12:31+02:00",
"date_finish": "2024-06-07T16:12:31+02:00",
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Result of updating the custom field:
|
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 40x, 50x
{
"error": "",
"error_description": "The entity with ID '235' is not found."
}
|
Name |
Description |
|
error |
String error code. It may consist of digits, Latin letters, and underscores |
|
error_description |
Textual description of the error. The description is not intended to be shown to the end user in its raw form |
Possible Errors
|
Code |
Error Text |
Description |
|
Empty string |
|
Custom field with the specified identifier not found |
|
Empty string |
|
Custom field with the specified identifier not found |
|
Empty string |
|
Identifier of the custom field is not specified or has an invalid value |
|
Empty string |
|
Insufficient access rights to modify the custom field |
|
|
|
Failed to update the custom field |
|
|
|
Failed to save values of the list-type custom field (e.g., when a duplicate external key of one of the values occurred) |
Statuses and System Error Codes
HTTP Status: 20x, 40x, 50x
The errors described below may occur when calling any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The current method is not permitted for calls using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The HTTPS protocol is required for method calls |
|
|
|
The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it |
|
|
|
The REST API is only available on commercial plans |
|
|
|
The user associated with the access token or webhook used to call the method lacks the necessary permissions |
|
|
|
The manifest is not available |
|
|
|
The request requires higher privileges than those provided by the webhook token |
|
|
|
The provided access token has expired |
|
|
|
The user does not have access to the application. This means that the application is installed, but the portal administrator has restricted access to this application to specific users only |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the "Temporary closure of the public part of the site" option. Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |
Continue Learning
- Create a New Custom Field for crm.requisite.userfield.add
- Get User Field by ID crm.requisite.userfield.get
- Get a list of custom fields of the requisite by filter crm.requisite.userfield.list
- Delete User Field of Requisite crm.requisite.userfield.delete