Skip to Content
Author's profile photo Former Member

Postalsoft DeskTop Mailer and Business Edition: Usage of the MERGE_KEY field during Email Append Processing

You may have noticed when you add the database fields necessary to perform Email Append,  a new hidden field  is required – MERGE_KEY.  Since the email append process will take 7-10 days, we did not think it would be acceptable to lock the database the entire time of the email append processing. When the email data is ready to be merged, however, the Postalsoft product needs a method to merge the correct record in the database with the processed email address data returned as a result of Extended Services processing.  The way Postalsoft matches the records is with the MERGE_KEY.  The value of this field is sent to Authenticom, and is associated to an individual record. When the email append records are returned from Authenticom, the Postalsoft product matches the value in the MERGE_KEY field from both the processed record and the record in the Postalsoft database to ensure the correct record is updated with the email append data.

The introduction of the MERGE_KEY field allows you to add and remove records without affecting the ability to find correct record in the database to update when the email append process complates. 

You may ask “What happens if you delete a record that was sent to Authenticom for processing?”.  That is not a problem since each record returned from Authenticom that contains a value in the  MERGE_KEY filed that is not matched in the database, this returned record is bypassed and the next returned record in the email append data is processed.

All this is made possible by the MERGE_KEY field. It is hidden so you are not tempted to change it’s value, since this would affect how the merging of the Email Append records is done.

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.