...
The REST API now includes a feature that allows users to perform batch updates on condition records by providing the full key of the records. This functionality enables updates to non-key fields and non-validity period fields, including attributes and integration status fields. Users can leverage this capability to ensure all required attributes are correctly set. The feature utilizes the existing generic REST API endpoint loaddata
.
Condition record set can be identified by either ID or Name. And as per general functionality of loaddata
endpoint, the (non-key, non-validity) attributes not listed in request are untouched.
In request replace CRCIX with correct type depending on number of keys the item(s) have.
Example 1
In this example condition record set ID is provided.
Item | Value | |||||
---|---|---|---|---|---|---|
Method |
| |||||
URL |
| |||||
Request |
| |||||
Response |
|
Example 2
In this example condition record set Name is provided.
Item | Value | |||||
---|---|---|---|---|---|---|
Method |
| |||||
URL |
| |||||
Request |
|
|
|
|
|
| ||||||
Response |
|
|
Info |
---|
See also:
|