...
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
.
The Condition record set Record Set can be identified by either ID
(Example 1) or Name
. And as per (Example 2). As per the general functionality of of the loaddata
endpoint endpoint, the (non-key, non-validity) attributes not listed in the request are stay untouched.
In the actual request replace , replace CRCIX
with with the correct type depending on the number of keys the itemCondition Record Item(s) have (CRCI1
..CRCI12
).
Example 1
Anchor | ||||
---|---|---|---|---|
|
In this example condition record set , Condition Record Set ID
is provided.
Item | Value | |||||
---|---|---|---|---|---|---|
Method |
| |||||
URL |
| |||||
Request |
| |||||
Response |
|
Example 2
Anchor | ||||
---|---|---|---|---|
|
In this example condition record set , Condition Record Set Name
is provided.
Item | Value | |||||
---|---|---|---|---|---|---|
Method |
| |||||
URL |
| |||||
Request |
| |||||
Response |
|
...