Example of merging entities from three data sources - Card Synchronization 3.4.2

Card Synchronization Plugin Guide 3.4.2

Applies to
Card Synchronization 3.4.2
Last updated
2023-01-27
Content type
Guides > Plugin and extension guides
Language
English
Product
Card Synchronization
Version
3.4

You can merge entities from three different data sources using global keys.

In the following example, cardholders from three different data sources are merged. The data sources are presented in order of their priority.

Global key configuration for Data source A

  • Resolve data source relationships using global keys is not selected.
  • Custom field and Email address are selected as a global key fields for cardholders.

Cardholder data in Data source A

Unique ID Email Name Custom field A
ACH1 CH1@genetec.com Cardholder A1 111
ACH2 CH2@genetec.com Cardholder A2 222
ACH3 CH3@genetec.com Cardholder A3 333

Global key configuration for Data source B

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

Cardholder data in Data source B

Unique ID Email Name Custom field B
BCH1 CH3@genetec.com Cardholder B1 222

Global key configuration for Data source C

  • Resolve data source relationships using global keys is not selected.
  • Custom field and Email address are selected as a global key fields for cardholders.

Cardholder data in Data source C

Unique ID Email Name Custom field C
CCH1 CH3@genetec.com Cardholder C1 111

Result

Two cardholders are created in Security Center.
  • ACH1, ACH3, BCH1, and CCH1 are merged into one cardholder. The name of the cardholder is Cardholder A1 because the value is taken from the data source with the highest priority.
    • ACH1 and CCH1 are merged because the fields Custom field C and Custom field A share the same value 111, which is configured as a global key for ACH1 and CCH1.
    • CCH1, BCH1, and ACH3 are merged because they all share the same email CH3@genetec.com, which is configured as a global key for all three.
  • ACH2 is created as a separate cardholder because its global keys do not match with any other global keys.
Email Name Custom field A Custom field B Custom field C
CH1@genetec.com Cardholder A1 111 222 111
CH2@genetec.com Cardholder A2 222