LCA Error for Batch of Entities or Relations
Enhancements have been added to handle error associated with a batch of entities or relations.
While creating a batch of relations or entities for any relationType
or
entityType
, multiple relations or entities requests are sent in one
POST
call. If one of the relations or entities has an issue with the
associated LCA Hook, the response returns an error for the entire batch of relations or
entities. The error message doesn't accurately convey the issue for the particular relation or
entity and the entire batch is not persisted.
An enhancement has resolved this issue and the response now shows the proper error message for incorrect relation or entity only. The details for the other records in the batch are also displayed.
Request | Description |
---|---|
|
This request example consists of three entities. As per the
configured LCA in this example, the FirstName of an
entity cannot have any special character. However, in this example,
entity A3 has the special character hash (#) in the
FirstName (#A3).
Note that out of the three entities in the batch, only entity A3 has incorrect value as per the configured LCA. |
Behavior | Response | Description |
---|---|---|
Old Behavior | Status Code:
200 Response:
|
The response returns an error for the complete batch of entities. The
status code 200 with the detailed error message, does not
identify the actual issue for entity A3. Instead, throws the error for
the complete batch of entities without persisting them. |
New Behavior | Status Code:
200 Response:
|
The response returns the details of the two persisted entities and an error message only for the incorrect entity. |