Implementation Guide › Implementation › Data Gathering (Data Source Expert) › Adapter Feature Advanced Topics › Event Singularity › Adapter Configuration File with Event Singularity

Adapter Configuration File with Event Singularity

TranslatorCollection/Translator/OnDuplication

This field determines what must be done if the Event already exists in the database.

Possible values are:

• Add-inserts (additional) Event(s) into the database.
• Update-causes the deletion (in some cases) of the existing Event and the insertion of a new one after validating that the event has changed.
• updateAlways-causes the deletion (in some cases) of the existing Event and the insertion of a new one without checking for changes.
• Ignore-does not insert a new event into the database.

The default value is Add.

Ignore versus Add

There may be minor performance decreases while running the Adapter in the Ignore mode. However, in the Add mode, the system triggers recalculation in every case of a duplicated event.

Update versus updateAlways

Using the Update option decreases the performance of the Adapter, while updateAlways decreases the performance of the calculation while triggering recalculation for every case.

TranslatorCollection > Translator > TranslatorFields > TranslatorField > IsKey

This attribute determines whether the field it belongs to should contribute its value towards the unique key for the raw data. It is included if value = "yes" and not included if value = "no". The default value (if no value is given) is "yes" for standard fields (ResourceId, EventTypeId and Timestamp) and "no" for all others. The key should be chosen carefully to ensure that the raw data maintains the required integrity and ensures the calculations are fully accurate.