Example of deleting entities from a data source after a merge - Card Synchronization 3.0

Card Synchronization Plugin Guide 3.0

series
Card Synchronization 3.0
revised_modified
2018-08-29

When you delete records corresponding to entities in Security Center from the external data source, the results of the deletion vary depending on what you configure as the synchronization behavior of the plugin.

The following example shows what happens when cardholders from an external data source are merged with existing cardholders in Security Center, and are then deleted from the external data source. Data source A is the external data source, and Security Center data source represents all the existing entities in Security Center.

Data source A has a higher priority than Security Center data source.

Global key configuration for Data source A

  • Resolve data source relationships using global keys is not selected.
  • Cardholder email is selected as a global key field for cardholders.

Cardholder data in Data source A

Unique ID Email Name Custom field A
ACH1 CH1@genetec.com Cardholder A1 CFA1
ACH2 CH2@genetec.com Cardholder A2 CFA2
ACH3 CH3@genetec.com Cardholder A3 CFA3

Global key configuration for Security Center data source

  • Resolve data source relationships using global keys is not selected.
  • Cardholder email is selected as a global key field for cardholders.

Existing cardholders in Security Center

Email Name Custom field B
CH1@genetec.com Cardholder 1 CFB1
CH2@genetec.com Cardholder 2 CFB2
CH4@genetec.com Cardholder 4 CFB4

Merge result

Upon synchronization, two existing cardholders are updated with external data, and one cardholder is created in Security Center.
  • Cardholder 1 and Cardholder A1 are merged into one cardholder because they share the value CH1@genetec.com, which is defined as a global key for both.
    • The name of the cardholder is Cardholder A1 because the value is taken from the data source with the highest priority.
  • Cardholder 2 and Cardholder A2 are merged into one cardholder because they share the value CH2@genetec.com, which is defined as a global key for both.
    • The name of the cardholder is Cardholder A2 because the value is taken from the data source with the highest priority.
  • Cardholder A3 is created in Security Center by the plugin.
  • Cardholder 4, which already existed in Security Center remains the same.
Email Name Custom field A Custom field B
CH1@genetec.com Cardholder A1 CFA1 CFB1
CH2@genetec.com Cardholder A2 CFA2 CFB2
CH3@genetec.com Cardholder A3 CFA3  
CH4@genetec.com Cardholder 4   CFB4

Deletion result

Depending on what is selected for the option When entities are deleted from their source, deleting all the cardholders from the external source after they have been merged with existing cardholders yields different results upon synchronization.
Delete the entities from Security Center is selected.
  • Only Cardholder 4 remains in Security Center because nothing was merged with it from the external data source.
Email Name Custom field A Custom field B
CH4@genetec.com Cardholder 4   CFB4
Keep the entities in Security Center is selected.
  • All entities remain in Security Center.
Email Name Custom field A Custom field B
CH1@genetec.com Cardholder A1 CFA1 CFB1
CH2@genetec.com Cardholder A2 CFA2 CFB2
CH3@genetec.com Cardholder A3 CFA3  
CH4@genetec.com Cardholder 4   CFB4
Only delete the entities created by the plugin is selected.
  • Only Cardholder A3 is deleted from Security Center because all the other cardholders already existed in Security Center before the merge.
Email Name Custom field A Custom field B
CH1@genetec.com Cardholder A1 CFA1 CFB1
CH2@genetec.com Cardholder A2 CFA2 CFB2
CH4@genetec.com Cardholder 4   CFB4