Ardoq has three options for handling the update and creation of components and references:
Create new and update existing assets — the default Ardoq behavior
Update only existing assets when using custom ID or Ardoq OID
Create only new assets when using custom ID or Ardoq OID
Additionally, it has an option for automatically deleting data from Ardoq that is outside of the scope of the current import.
Create New and Update Existing Assets (Merge and Upsert)
With this option you will both create new components, update existing components, and keep all other components unchanged. This is the default data sync strategy for Ardoq.
Update only existing assets when using custom ID or Ardoq OID (Update Only)
With this option, you can target which specific assets you want to update based on their custom ID or Ardoq OID. Assets that are not specified by an ID will not be updated. New assets coming in that don't match an existing ID will not be created.
Create only new assets when using Custom ID (Create Only)
With this option, you can ensure that only new data gets created and existing data does not get overwritten or updated. Only custom IDs can be used for this purpose — Ardoq OIDs will be created internally after the import.
Delete Missing Assets
This options is most useful when the data you are importing represents a full dataset and not a subset. You can think of the new data coming in as the latest data and anything not part of that set as data to be removed. In other words, new data is added, overlapping data is replaced, and old data is deleted.
For instance, let's say you are maintaining a list of active employees in Ardoq by importing data from your Entra ID instance. You may want to enable the Delete Missing Assets option to automatically remove users who are no longer part of your organization from Ardoq. Without this option enabled, Ardoq will default to simply expanding your user list without ever removing employees who no longer exist in the Entra ID database.
Note: Only component types configured in the import will be affected. More specifically, only component types defined in the Component Name column mappings in the component tables, and in the Source column mappings in the reference tables.