Mapping externally specified unique IDs of a ContactManager contact

ContactManager supports creation of a contact with an external unique ID specified by the core application.

• If an external unique ID is specified in the XmlBackedInstance data sent in the createContact method call, ContactManager populates the LinkID of the new contact with that value. The field that ContactManager checks for in the createContact call is External_UniqueID.
• If the createContact method call does not specify an external unique ID, ContactManager generates its own unique ID and stores that value in the contact’s LinkID.

For example, the following lines of mapping code from various parts of the construct method in the ContactManager class ContactMapper support this mechanism:

fieldMapping(ABContact#External_UniqueID),
fieldMapping(ABContactAddress#External_UniqueID),
fieldMapping(Address#External_UniqueID),
fieldMapping(ABContactTag#External_UniqueID),
fieldMapping(EFTData#External_UniqueID),
fieldMapping(ABContactCategoryScore#External_UniqueID),

See also

• PolicyCenter mapping of externally specified unique IDs
• Creating and linking a contact
• ContactManager link IDs and comparison to other IDs
• ABContactAPI methods