Update Existing Custom Contact Field crm.contact.userfield.update
Scope:
crmWho can execute the method: administrator
The method crm.contact.userfield.update updates an existing custom contact field.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
id* |
Identifier of the custom field. The identifier can be obtained using the methods |
|
fields* |
Object format:
where:
The list of available fields is described below. An incorrect field in Only those fields that need to be changed should be passed in |
Parameter fields
|
Parameter |
Description |
|
MANDATORY |
Is the field mandatory? Possible values:
|
|
SHOW_FILTER |
Should the field be shown in the filter? Possible values:
|
|
XML_ID |
External code |
|
SETTINGS |
Additional field parameters. Each field type ( The field only overwrites the passed values |
|
LIST |
List of possible values for a custom field of type |
|
SORT |
Sort index. Must be greater than zero |
|
SHOW_IN_LIST |
Should the custom field be shown in the list? This parameter has no effect within Possible values:
|
|
EDIT_IN_LIST |
Allow user editing? Possible values:
|
|
IS_SEARCHABLE |
Are the field values included in the search? This parameter has no effect within Possible values:
|
|
Filter label in the list. When passing a string, it is set for each language. For languages where no value is explicitly specified, The field completely overwrites the previous value |
|
|
Header in the list. When passing a string, it is set for each language. For languages where no value is explicitly specified, The field completely overwrites the previous value |
|
|
Label in the edit form. When passing a string, it is set for each language. For languages where no value is explicitly specified, The field completely overwrites the previous value |
|
|
Error message. When passing a string, it is set for each language. For languages where no value is explicitly specified, The field completely overwrites the previous value |
|
|
Help message. When passing a string, it is set for each language. For languages where no value is explicitly specified, The field completely overwrites the previous value |
Parameter SETTINGS
Each type of custom field has its own set of additional settings. This method supports changing only those described below.
|
Name |
Description |
|
DEFAULT_VALUE |
Default value |
|
ROWS |
Number of rows in the input field. Must be greater than 0 and less than 50. If a value <= 0 is passed, it will be set to If a value >= 50 is passed, it will be set to |
|
Name |
Description |
|
DEFAULT_VALUE |
Default value |
|
Name |
Description |
|
DEFAULT_VALUE |
Default value |
|
PRECISION |
Number precision. Must be greater than or equal to 0. If an invalid value is passed, it will be set to |
|
Name |
Description |
|
DEFAULT_VALUE |
Default value, where When passing a value, it will be set according to the rule:
|
|
DISPLAY |
Appearance. Possible values:
|
|
Name |
Description |
|
DEFAULT_VALUE |
Default value. Object format:
where
If an invalid value is passed, it will be set to:
|
|
Name |
Description |
|
DISPLAY |
Appearance. Possible values:
|
|
LIST_HEIGHT |
List height. Must be greater than 0 |
|
Name |
Description |
|
IBLOCK_TYPE_ID |
Identifier of the information block type |
|
IBLOCK_ID |
Identifier of the information block |
|
DEFAULT_VALUE |
Default value |
|
DISPLAY |
Appearance. Possible values:
|
|
LIST_HEIGHT |
List height. Must be greater than 0 |
|
ACTIVE_FILTER |
Should elements with the active flag be shown? Possible values:
|
|
Name |
Description |
|
ENTITY_TYPE |
Identifier of the reference type. Use |
If none of the following options are passed, the binding to leads will be enabled by default (LEAD = Y)
|
Name |
Description |
|
LEAD |
Is the binding to Leads enabled? Possible values:
|
|
CONTACT |
Is the binding to Contacts enabled? Possible values:
|
|
COMPANY |
Is the binding to Companies enabled? Possible values:
|
|
DEAL |
Is the binding to Deals enabled? Possible values:
|
Type uf_enum_element
|
Name |
Description |
|
ID |
Identifier of the list item. When passing this parameter, the corresponding list item will be changed; otherwise, a new list item will be added. The identifier can be obtained using the method |
|
DEL |
Flag necessary for deleting a list item. Makes sense only when passing Possible values: Default is |
|
VALUE |
Value of the list item |
|
SORT |
Sort index. Must be greater than or equal to 0 |
|
DEF |
Is the list item the default value? Possible values:
For a multiple field, multiple |
|
XML_ID |
External code of the value. Must be unique within the list items of the custom field |
Code Examples
How to Use Examples in Documentation
Example of Updating a String Type Custom Field
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":536,"fields":{"MANDATORY":"N","SHOW_FILTER":"N","SETTINGS":{"DEFAULT_VALUE":"Hello, World! Default value (changed)","ROWS":10},"SORT":2000,"EDIT_IN_LIST":"N","LIST_FILTER_LABEL":"Hello, World! Filter (changed)","LIST_COLUMN_LABEL":{"en":"Hello, World! Column (changed)","de":"Hallo, Welt! Spalte (geändert)"},"EDIT_FORM_LABEL":{"en":"Hello, World! Edit (changed)","de":"Hallo, Welt! Bearbeiten (geändert)"},"ERROR_MESSAGE":{"en":"Hello, World! Error (changed)","de":"Hallo, Welt! Fehler (geändert)"},"HELP_MESSAGE":{"en":"Hello, World! Help (changed)","de":"Hallo, Welt! Hilfe (geändert)"}}}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/crm.contact.userfield.update
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":536,"fields":{"MANDATORY":"N","SHOW_FILTER":"N","SETTINGS":{"DEFAULT_VALUE":"Hello, World! Default value (changed)","ROWS":10},"SORT":2000,"EDIT_IN_LIST":"N","LIST_FILTER_LABEL":"Hello, World! Filter (changed)","LIST_COLUMN_LABEL":{"en":"Hello, World! Column (changed)","de":"Hallo, Welt! Spalte (geändert)"},"EDIT_FORM_LABEL":{"en":"Hello, World! Edit (changed)","de":"Hallo, Welt! Bearbeiten (geändert)"},"ERROR_MESSAGE":{"en":"Hello, World! Error (changed)","de":"Hallo, Welt! Fehler (geändert)"},"HELP_MESSAGE":{"en":"Hello, World! Help (changed)","de":"Hallo, Welt! Hilfe (geändert)"}}, "auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/crm.contact.userfield.update
BX24.callMethod(
'crm.contact.userfield.update',
{
id: 536,
fields: {
MANDATORY: "N",
SHOW_FILTER: "N",
SETTINGS: {
DEFAULT_VALUE: "Hello, World! Default value (changed)",
ROWS: 10,
},
SORT: 2000,
EDIT_IN_LIST: "N",
LIST_FILTER_LABEL: "Hello, World! Filter (changed)",
LIST_COLUMN_LABEL: {
"en": "Hello, World! Column (changed)",
"de": "Hallo, Welt! Spalte (geändert)"
},
EDIT_FORM_LABEL: {
"en": "Hello, World! Edit (changed)",
"de": "Hallo, Welt! Bearbeiten (geändert)"
},
ERROR_MESSAGE: {
"en": "Hello, World! Error (changed)",
"de": "Hallo, Welt! Fehler (geändert)"
},
HELP_MESSAGE: {
"en": "Hello, World! Help (changed)",
"de": "Hallo, Welt! Hilfe (geändert)"
},
},
},
(result) => {
result.error()
? console.error(result.error())
: console.info(result.data())
;
},
);
require_once('crest.php');
$result = CRest::call(
'crm.contact.userfield.update',
[
'id' => 536,
'fields' => [
'MANDATORY' => "N",
'SHOW_FILTER' => "N",
'SETTINGS' => [
'DEFAULT_VALUE' => "Hello, World! Default value (changed)",
'ROWS' => 10,
],
'SORT' => 2000,
'EDIT_IN_LIST' => "N",
'LIST_FILTER_LABEL' => "Hello, World! Filter (changed)",
'LIST_COLUMN_LABEL' => [
'en' => "Hello, World! Column (changed)",
'de' => "Hallo, Welt! Spalte (geändert)"
],
'EDIT_FORM_LABEL' => [
'en' => "Hello, World! Edit (changed)",
'de' => "Hallo, Welt! Bearbeiten (geändert)"
],
'ERROR_MESSAGE' => [
'en' => "Hello, World! Error (changed)",
'de' => "Hallo, Welt! Fehler (geändert)"
],
'HELP_MESSAGE' => [
'en' => "Hello, World! Help (changed)",
'de' => "Hallo, Welt! Hilfe (geändert)"
],
]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
try {
$contactUserfieldItemId = 123; // Example ID
$userfieldFieldsToUpdate = [
'FIELD_NAME' => 'New Field Name',
'USER_TYPE_ID' => 'string',
'SORT' => '100',
'MULTIPLE' => 'N',
'MANDATORY' => 'N',
'SHOW_FILTER' => 'Y',
'SHOW_IN_LIST' => 'Y',
'EDIT_IN_LIST' => 'Y',
'IS_SEARCHABLE' => 'Y',
'EDIT_FORM_LABEL' => 'New Label',
'LIST_COLUMN_LABEL' => 'Column Label',
'LIST_FILTER_LABEL' => 'Filter Label',
'ERROR_MESSAGE' => 'Error Message',
'HELP_MESSAGE' => 'Help Message',
'LIST' => '',
'SETTINGS' => '',
];
$result = $serviceBuilder
->getCRMScope()
->contactUserfield()
->update($contactUserfieldItemId, $userfieldFieldsToUpdate);
if ($result->isSuccess()) {
print($result->getCoreResponse()->getResponseData()->getResult()[0]);
} else {
print("Update failed.");
}
} catch (Throwable $e) {
print("Error: " . $e->getMessage());
}
Example of Updating a List Type Custom Field
Current list items:
[
{
"ID": "115",
"SORT": "100",
"VALUE": "List item #1",
"DEF": "Y",
"XML_ID": "XML_ID_1"
},
{
"ID": "116",
"SORT": "200",
"VALUE": "List item #2",
"DEF": "N",
"XML_ID": "XML_ID_2"
},
{
"ID": "117",
"SORT": "300",
"VALUE": "List item #3",
"DEF": "N",
"XML_ID": "XML_ID_3"
},
{
"ID": "118",
"SORT": "400",
"VALUE": "List item #4",
"DEF": "N",
"XML_ID": "XML_ID_4"
}
]
Change it as follows:
- remove list items with
ID = 115andID = 116 - update the list item with
ID = 117:VALUE: “List item #3” -> “List item #3 (changed)”SORT: 300 -> 50
- add a new list item “List item #5”
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"fields":{"MANDATORY":"N","SHOW_FILTER":"Y","LIST":[{"ID":115,"DEL":"Y"},{"ID":116,"DEL":"Y"},{"ID":117,"VALUE":"List item #3 (changed)","SORT":50},{"VALUE":"List item #5","XML_ID":"XML_ID_5","SORT":500}],"SETTINGS":{"DISPLAY":"DIALOG","LIST_HEIGHT":3},"SORT":1000}}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/crm.contact.userfield.update
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"fields":{"MANDATORY":"N","SHOW_FILTER":"Y","LIST":[{"ID":115,"DEL":"Y"},{"ID":116,"DEL":"Y"},{"ID":117,"VALUE":"List item #3 (changed)","SORT":50},{"VALUE":"List item #5","XML_ID":"XML_ID_5","SORT":500}],"SETTINGS":{"DISPLAY":"DIALOG","LIST_HEIGHT":3},"SORT":1000},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/crm.contact.userfield.update
BX24.callMethod(
'crm.contact.userfield.update',
{
fields: {
MANDATORY: "N",
SHOW_FILTER: "Y",
LIST: [
{
ID: 115,
DEL: "Y"
},
{
ID: 116,
DEL: "Y",
},
{
ID: 117,
VALUE: "List item #3 (changed)",
SORT: 50,
},
{
VALUE: "List item #5",
XML_ID: "XML_ID_5",
SORT: 500,
},
],
SETTINGS: {
DISPLAY: "DIALOG",
LIST_HEIGHT: 3,
},
SORT: 1000,
},
},
(result) => {
result.error()
? console.error(result.error())
: console.info(result.data())
;
},
);
require_once('crest.php');
$result = CRest::call(
'crm.contact.userfield.update',
[
'fields' => [
'MANDATORY' => "N",
'SHOW_FILTER' => "Y",
'LIST' => [
[
'ID' => 115,
'DEL' => "Y"
],
[
'ID' => 116,
'DEL' => "Y",
],
[
'ID' => 117,
'VALUE' => "List item #3 (changed)",
'SORT' => 50,
],
[
'VALUE' => "List item #5",
'XML_ID' => "XML_ID_5",
'SORT' => 500,
],
],
'SETTINGS' => [
'DISPLAY' => "DIALOG",
'LIST_HEIGHT' => 3,
],
'SORT' => 1000,
]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": true,
"time": {
"start": 1724419843.518672,
"finish": 1724419844.120328,
"duration": 0.6016559600830078,
"processing": 0.1907808780670166,
"date_start": "2024-08-23T15:30:43+02:00",
"date_finish": "2024-08-23T15:30:44+02:00",
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Root element of the response, contains |
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 400
{
"error": "",
"error_description": "Access denied."
}
|
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 Error Codes
|
Code |
Description |
Value |
|
|
|
The passed |
|
|
|
The passed |
|
|
|
Occurs when:
|
|
|
|
The custom field with the passed |
|
|
List item with value XML_ID= |
The passed |
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 allowed to be called using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The methods must be called using the HTTPS protocol |
|
|
|
The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support |
|
|
|
The REST API is available only on commercial plans |
|
|
|
The user whose access token or webhook was used to call the method lacks 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 account administrator has allowed access to this application only for specific users |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the option "Temporary closure of the public part of the site". 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 Custom Field for Contacts crm.contact.userfield.add
- Get Custom Contact Field by Id crm.contact.userfield.get
- Get a list of custom fields for contacts crm.contact.userfield.list
- Delete Custom Contact Field crm.contact.userfield.delete