preserveURIs option
If this parameter is present, the Entities takes into account URIs you specify in the request. You can use this parameter for both entity and attribute URIs.
Example 1. Entities URIs in the Request
If this option is present for an entity URI, the API finds this entity and overrides it
with attributes in the request. It can be used for inserting new attributes with
new/existing crosswalks to entities. If this type of entity doesn't exist, the API returns
the EXPLICIT_URI_OF_NON_EXISTING_OBJECT_DEFINED(242)
error.
Existing Entity
Insert New Attribute With preserverURIs
by the Entity URI
In this case, the match entity is found by the URI, and the new attribute is inserted into it.
Results
Example 2. Attributes URIs in the Request
URIs of attribute values can be changed during overwrite operation (of an attribute has
more than one value and at least one of values were changed). As you can see in the
partialOverride
option example, the URI of the value of the
FirstName
attribute was changed after overwrite.
If the preserveURIs
option is present for simple or nested attributes,
URIs of attribute values for which they were specified in the request JSON will not be
changed. This option does not work with reference attributes.
Existing Entity
Overwrite With preserveURIs
Option for Attributes
In this case, the match entity is found by the crosswalk, and the URI of the attribute value has not changed.
Results