Update Custom Field of a Given Requisite Template crm.requisite.preset.field.update
Choose a tool for developing with an AI agent:
- use Alaio Vibecode to build an app for Bitrix24 from a task description without knowing any programming language. The agent writes the code and deploys the app to a server, with no manual hosting setup
- use the MCP server to develop a REST API integration in your own project. The agent refers to the official REST documentation
Scope:
crmWho can execute the method: a user with "edit" access permission for both contacts and companies
Updates a custom field in the specified template.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
id* |
Identifier of the custom field to be updated. Identifiers of custom fields in the requisite template can be obtained using the crm.requisite.preset.field.list method. |
|
preset* |
An object containing the identifier of the template to which the custom field is added (e.g., Template identifiers can be obtained using the method crm.requisite.preset.list |
|
fields* |
An object with fields and their values that need to be updated. The crm.requisite.preset.field.fields method allows you to get the description of the fields that can be modified. The API requires a value to be specified in the FIELD_NAME field. If it does not need to be changed, the current value can be specified. |
Parameter fields
Required parameters are marked with *
|
Name |
Description |
|
FIELD_NAME* |
Field name. The API requires specifying a value in this field. If it does not need to be changed, you can specify the current |
|
FIELD_TITLE |
An alternative name for the field in the requisite. The alternative name is displayed in various forms for filling out requisites. Depending on the specific form, the alternative name may or may not be used |
|
SORT |
Sorting. The order in the list of template fields |
|
IN_SHORT_LIST |
Show in the short list. Deprecated field, currently not used. Retained for backward compatibility. Can take values |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"ID":1,"preset":{"ID":27},"fields":{"FIELD_NAME":"RQ_NAME","FIELD_TITLE":"Name","IN_SHORT_LIST":"Y"}}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/crm.requisite.preset.field.update
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"ID":1,"preset":{"ID":27},"fields":{"FIELD_NAME":"RQ_NAME","FIELD_TITLE":"Name","IN_SHORT_LIST":"Y"},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/crm.requisite.preset.field.update
// This snippet is an ES module: top-level await requires type="module" or a bundler.
// $b24 is an already-initialized SDK instance (see the SDK "Get started" guide).
import { Text } from '@bitrix24/b24jssdk'
import type { B24Frame } from '@bitrix24/b24jssdk'
declare const $b24: B24Frame
try {
const response = await $b24.actions.v2.call.make<boolean>({
method: 'crm.requisite.preset.field.update',
params: {
ID: 1,
preset: {
ID: 27,
},
fields: {
FIELD_NAME: 'RQ_NAME',
FIELD_TITLE: 'Name',
IN_SHORT_LIST: 'Y',
},
},
requestId: Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
} else {
const result = response.getData()!.result
console.info('Field updated:', result)
}
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
<!-- Load the SDK (UMD build); it is exposed as the global B24Js -->
<script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
<script>
async function updatePresetField() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.actions.v2.call.make({
method: 'crm.requisite.preset.field.update',
params: {
ID: 1,
preset: {
ID: 27,
},
fields: {
FIELD_NAME: 'RQ_NAME',
FIELD_TITLE: 'Name',
IN_SHORT_LIST: 'Y',
},
},
requestId: B24Js.Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
return
}
const result = response.getData().result
console.info('Field updated:', result)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', updatePresetField)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.crm.requisite.preset.field.update(
bitrix_id=1,
preset={
"ID": 27,
},
fields={
"FIELD_NAME": "RQ_NAME",
"FIELD_TITLE": "Name",
"IN_SHORT_LIST": "Y",
},
).response
result = bitrix_response.result
print(result)
except BitrixAPIError as error:
print(
"Bitrix API error",
f"error: {error.error}",
f"error_description: {error.error_description}",
sep="\n",
)
except BitrixSDKException as error:
print(f"Bitrix SDK error: {error.message}")
except Exception as error:
print(f"Unexpected error: {error}")
try {
$response = $b24Service
->core
->call(
'crm.requisite.preset.field.update',
[
'ID' => 1,
'preset' => [
'ID' => 27,
],
'fields' => [
'FIELD_NAME' => 'RQ_NAME',
'FIELD_TITLE' => 'Name',
'IN_SHORT_LIST' => 'Y',
],
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
// The data processing logic you need
processData($result);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error updating preset field: ' . $e->getMessage();
}
BX24.callMethod(
"crm.requisite.preset.field.update",
{
ID: 1, // Custom field ID to be changed
preset:
{
"ID": 27 // Requisition template ID
},
fields: // Field values to be changed
{
"FIELD_NAME": "RQ_NAME", // The API requires a value to be specified in this field. If
// no change is needed, leave the previous value.
"FIELD_TITLE": "Name",
"IN_SHORT_LIST": "Y",
}
},
function(result)
{
if(result.error())
console.error(result.error());
else
{
console.info(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'crm.requisite.preset.field.update',
[
'ID' => 1,
'preset' => ['ID' => 27],
'fields' => [
'FIELD_NAME' => 'RQ_NAME',
'FIELD_TITLE' => 'Name',
'IN_SHORT_LIST' => 'Y',
]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "crm.requisite.preset.field.update", b24.Params{
"id": 1,
"preset": b24.Params{
"ID": 27,
},
"fields": b24.Params{
"FIELD_NAME": "RQ_NAME",
"FIELD_TITLE": "Name",
"IN_SHORT_LIST": "Y",
},
})
if err != nil {
return fmt.Errorf("crm.requisite.preset.field.update: %w", err)
}
var ok bool
if err := json.Unmarshal(res.Result, &ok); err != nil {
return fmt.Errorf("parse response: %w", err)
}
fmt.Println("done:", ok)
Response Handling
HTTP status: 200
{
"result": true,
"time": {
"start": 1716898310.398361,
"finish": 1716898310.936332,
"duration": 0.537971019744873,
"processing": 0.09376883506774902,
"date_start": "2024-05-28T14:11:50+02:00",
"date_finish": "2024-05-28T14:11:50+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 PresetField with ID '27' is not found"
}
|
Name |
Description |
|
error |
String error code. It consists of digits, Latin letters, and underscores. It may arrive empty — in that case only |
|
error_description |
Error message for the developer. Do not show it to the end user without processing |
Possible Error Codes
|
Code |
Description |
|
|
The field with the specified identifier was not found. |
|
|
Template with the specified identifier not found |
|
|
The field identifier is not specified or has an invalid value. |
|
|
Insufficient access permissions to delete the field from the requisite template. |
Statuses and System Error Codes
HTTP Status: 4xx, 5xx
The errors described below are returned by the REST API itself, not by the logic of a specific method. They can arrive in response to any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The server returned an unexpected response. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The method is blocked because the request resource intensity limit has been exceeded. The block is lifted automatically once the accumulated execution time of the method no longer exceeds the limit |
|
|
|
The request contains no authorization data: neither an access token nor a webhook code was passed |
|
|
|
Methods are called over the HTTPS protocol only |
|
|
|
The REST API is blocked due to overload. This is a manual individual block. To have it lifted, contact Bitrix24 technical support |
|
|
|
REST API access is not active for this account. In Bitrix24 Cloud, check the current plan or trial status: Vibe+ plans include REST API access, while Essentials plans do not. A webhook receives a different error message — |
|
|
|
No active webhook with the specified user identifier and secret code was found |
|
|
|
No method with this name was found. The name is misspelled, the method does not exist in the REST API, or it is unavailable without the required scope |
|
|
|
The request requires broader permissions than the token has: for a webhook these are the permissions granted to it, for an application it is the scope. For an application, the error message ends with |
|
|
|
The access token has expired |
|
|
|
The application is installed, but the Bitrix24 administrator has granted access to it only to specific users |
|
|
|
The public part of the site is closed. To open it 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
- Add a Custom Field to the CRM Requisite Template crm.requisite.preset.field.add
- Get Fields Available for Addition to the Requisite Template crm.requisite.preset.field.availabletoadd
- Get Custom Field of Requisite Template by ID crm.requisite.preset.field.get
- Get a List of All Customizable Fields for a Specified CRM Requisites Template crm.requisite.preset.field.list
- Delete Custom Field from CRM Requisite Template crm.requisite.preset.field.delete
- Get Description of Custom Fields for the Requisite Template crm.requisite.preset.field.fields