Add UPDATE Attribute Request
Creates a change item inside data change request for the updating of an existing attribute.
changeRequestId
parameter-it indicates that these changes must not be done in the real object; instead, they must be added to the given data change request for future review. PUT <TenantURL>/{attributeValueURI}
Parameter | Name | Required | Details |
---|---|---|---|
Headers | Authorization
| Yes | Information about authentication access token in format "Bearer <accessToken> " (see details in Auth APID ). |
Source-System
| No | Source system this request is representing. Example: "configuration/sources/Reltio" when data is not loaded from other source systems and is created in Reltio Platform directly. | |
Content-Type
| Yes | Should be "Content-Type: application/json" . | |
Query | changeRequestId
| No |
ID of the data change request to which a new change item should be added. |
crosswalkValue
| Yes-if Source-System is not 'Reltio' |
ID of the entity object providing this attribute in the source system. Example: an entity comes from Facebook and its identifier in Facebook is 'id3562'. For this entity, | |
crosswalkSourceTable
| No | ||
Body | Yes | JSON object representing attribute values to be used for creating/updating the data change request. |
changeRequestId
parameter is not required if the user has READ
privilege for the object and attribute, has INITIATE_CHANGE_REQUEST
privilege for the attribute, but does not have UPDATE
privilege for the attribute. A new data change request will be created automatically in this case. Response
JSON Object representing the new change item.
{
"id": "0000wbZ",
"type": "UPDATE_ATTRIBUTE",
"createdTime": 1445443808301,
"createdBy": "User",
"attributePath": "Identifiers/6",
"oldValue": {
"value": {
"Type": [{
"value": "Test"
}],
"ID": [{
"value": "1111"
}]
}
},
"newValue": {
"value": {
"Type": [{
"value": "NewType"
}],
"ID": [{
"value": "666"
}]
}
},
"crosswalk": {
"type": "configuration/sources/Veeva",
"value": "e1"
}
}