Add DELETE Attribute Request
Creates a change item inside data change request for deleting of an existing attribute.
It should be used in the same way as the request for deleting attributes. The only difference is the 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.
Request:
DELETE <TenantURL>/{attributeValueURI} | Parameter | Name | Required | Details |
|---|---|---|---|
| Headers | Authorization
| Yes | Information about authentication access token in format "Bearer <accessToken>" (see details in Auth API). |
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 DELETE 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":"0000sLJ",
"type":"DELETE_ATTRIBUTE",
"createdTime":1445443808276,
"createdBy":"User",
"attributePath":"ProductMetrics/3/NumberPatients/5",
"oldValue":{
"value":"1111"
},
"crosswalk":{
"type":"configuration/sources/Veeva",
"value":"e1"
}
}