The API uses
type for Database and app for Space. See Terminology.Setting the
fibery/id Field for Entities is mandatory to apply the Conflict Action when a duplicate is found.The Conflict Field can be of type:
fibery/text, fibery/int, or fibery/date
| Conflict Action | Description |
skip-create | do not create Entity if a Duplicate was found |
update-latest | updates the Duplicate found with all fields from the Entity to be created, excluding platform fields (fibery/id, fibery/public-id, fibery/rank, fibery/creation-date). If more than one Duplicate is found, the Duplicate with the latest fibery/creation-date is selected for updating. |
skip-create: Uses the first found Duplicate in the batch.update-latest: Uses the last found Duplicate in the batch.
- NULL values are not considered equal. An entity with a NULL Conflict Field value is not considered a Duplicate of another entity with a NULL value.
- Text Field comparisons are case-sensitive.
- Created: If an Entity was created, the array contains the new Entity’s information with
createaction. - Skipped: If an Entity was not created because
skip-createwas applied to a found Duplicate, the array contains a resolved Conflict withskip-createaction. - Updated: If an Entity was used to update a found Duplicate due to
update-latest, the array contains a resolved Conflict withupdate-latestaction. - Batch Duplicate handling: If an Entity was ignored due to a Duplicate found within the same batch of Entities, the array contains a resolved Conflict with
prefer-duplicate-found-in-the-batchaction. This action uses the Duplicate entity (D) and resolves it by applying the specified Conflict Action later: - If no Conflict is found for D, the array contains the created Entity D info with
createaction. - If a Conflict is found for D and resolved with
skip-create, the array contains a resolved Conflict withskip-createaction. - If a Conflict is found for D and resolved with
update-latest, the array contains a resolved Conflict withupdate-latestaction.
Case 1
- Batch of Entities contain duplicates
- There are no existing duplicates in the DB
- Conflict Action is
skip-create
Case 2
- Batch of Entities contains duplicates
- There are existing duplicates in the DB
- Conflict Action is
skip-create
Case 3
- Batch of Entities contains duplicates
- There are no existing duplicates in the DB
- Conflict Action is
update-latest
Case 4
- Batch of Entities contains duplicates
- There are existing duplicates in the DB
- Conflict Action is
update-latest