Skip to main content

Idmap

The IDMap function is designed to keep track of the identifiers of synchronized records in different systems. An IDMap entry associates a universal record ID with a subscriber, endpoint and application record ID.  

 IDMaps are stored in the 1Gateway database and transmitted in message headers.

Idmap: Lookup local id mapping​

The idmap lookup mapping looks up an idmap entry in 1Gateway’s internal database for the specified endpoint and id location in the incoming message. It also uses the subscriber Id if defined. This is used to determine if this is a new message or a message update. If an idmap entry is found, it returns the 1Gateway record ID.

LookupID config

Idmap: Save local id mapping​

The idmap save local id mapping saves an idmap entry in 1Gateway’s internal database for the specified endpoint and id location in the incoming message. It also uses the subscriber Id if defined. If not found, it generates a random 1Gateway recordID and stores it in the database with endpoint and subscriberID (and the message.ID), and adds it to the message headers.  Before saving the idmap entry, it looks up if one already exists and overrides it. This is used to keep track of the relationship between messages in different external systems (also between 1Gateway instances)

SaveID config