Best practices for importing entities - Card Synchronization 3.2

Card Synchronization Plugin Guide 3.2

Applies to
Card Synchronization 3.2
Last updated
Content type
Guides > Plugin and extension guides
Card Synchronization
Plugin and extension guides

Create a custom field for unique IDs in your data sources and in Security Center before importing entities. Following this best practice will facilitate troubleshooting if you delete the plugin, and then re-create it. You will be able to merge all duplicate imported entities at the same time.

After deleting the plugin, all imported entities remain in Security Center. If you create the plugin again, and then add the same data sources to the new plugin, all the imported entities will be duplicated.

The duplicate imported entities will be merged after you add a Security Center data source that uses the unique ID global key for each entity type.

Data source configuration

Before adding data sources to the Card Synchronization plugin, include an additional custom field for each entity type in your data sources.

In a database, the custom fields view should include one row for every entity you will import from that database.
  • Use a descriptive name as the CustomFieldName.
    Example: <ExternalSystemName>UniqueID.
  • The values of EntityUniqueId and of CustomFieldValue are the unique ID of the cardholder, cardholder group, or credential.
In cardholder, cardholder group, and credential files, include an additional column to enter the unique ID of each entity.
NOTE: If you want to manually add cardholders to imported groups, create a parent group and add the cardholders and groups as children of the parent group. Otherwise, the manually added cardholders are removed from the group during synchronization.

Security Center configuration

Create a custom field that uses the text data type for each of the following entity types:
  • Cardholders
  • Cardholder groups
  • Credentials
Use the same name you used in the data source.
Example: <ExternalSystemName>UniqueID.