MatchUp Object:Incremental:Match Key

From Melissa Data Wiki
Jump to navigation Jump to search

← MatchUp Object Reference

MatchUp Object Incremental Interface Navigation
Order of Operations
Match Key
Key File

The following functions take the real data being compared and construct a match key according to the mappings defined with the above functions and the matchcode specified when the Incremental deduper was initialized.


This function clears all values from previous calls to the AddField function.

To ensure that no extraneous information carried over from one record to the next, call this function after calling the BuildKey function or before the first call to the AddField function.

Syntax mdMU->ClearFields()
C mdMUIncrementalClearFields(mdMU)
.Net mdMU.ClearFields


This function passes a component of list data to the interface prior to calling the BuildKey function.

Fields must be passed to this function in the same order that the corresponding data types were mapped using the AddMapping function.

The following example expands on the AddMapping example. The matchcode uses five-digit ZIP codes, the street addresses, last and first names, in that order. The database contains a single “City/ST/ZIP” and a single full name field.

mdMU->AddField("Rancho Santa Margarita, CA 92688")
mdMU->AddField("Raymond F. Melissa")
mdMU->AddField("Raymond F. Melissa")
mdMU->AddField("22382 Avenida Empresa")

The deduper would use only the ZIP Code from the first AddField mapping, the last name from the second mapping, the first name from the third, etc.

Syntax mdMU->AddField(char)
C mdMUIncrementalAddField(mdMU, char)
.Net mdMU.AddField(string)


This function takes the information passed via calls to the AddField function and, using the mapping defined by the AddMapping function and the pattern defined by the matchcode being used, builds a match key.

A match key is a character string built according to a pattern defined by the current matchcode, consisting only of enough information to determine if the current record is unique or has a duplicate within the key file.

For example, let’s assume the matchcode called for a five-digit ZIP Code, first ten characters of a last name, a street number and the first ten characters of a street name. The current record is for Raymond F. Melissa at 22382 Avenida Empresa in the 92688 ZIP Code. The match key would be:


Because “Empresa” is only seven characters, the key would be padded with three spaces at the end.

Syntax mdMU->BuildKey()
C mdMUIncrementalBuildKey(mdMU)
.Net mdMU.BuildKey


This function accepts a match key before calling the MatchRecord function.

The BuildKey function creates a key from input data. If, however, the match keys are already stored in the source database, use this function to pass the keys to the deduper before calling MatchRecord.

Syntax mdMU->SetKey(char)
C mdMUIncrementalSetKey(mdMU, char)
.Net mdMU.SetKey = string


This function accepts a character value that uniquely identifies each record in a set of data. The character value passed to this function must be unique for every record. This enables you to associate the match key in the key file to the corresponding record in the database.

Syntax mdMU->SetUserInfo(char)
C mdMUIncrementalSetUserInfo(mdMU, char)
.Net mdMU.SetUserInfo = string