|MatchUp Object Incremental Interface Navigation|
|Order of Operations|
Before generating match keys for the records in the database, the code must supply the Incremental interface with information about what sort of data it will be handling.
This function clears any existing field mappings.
It is a good idea to call this function before beginning to map fields, especially if the application may be required to perform multiple deduping operations in a single session.
This function selects the types of fields that will be used to build the match key and the order in which they will be added using the AddField function.
The function accepts an enumerated value of the type MatchcodeMapping. It tells the Incremental interface which data types will be used for this deduping operation and in what order they will be passed to the deduper when passing data using the AddField function.
The data types used must contain the data expected by the matchcode being used, but it does not have to be an exact match. For example, if the matchcode requires a five-digit ZIP Code but the database contains a single “City/State/ZIP” field, simply add the CityStZip mapping and pass the full string to the AddField function later. MatchUp Object is smart enough to use only the information it needs.
In another example, a matchcode calls for both last name and first name but the database contains only full names. Simply apply the FullName mapping twice and pass the full name data twice to the AddField function.
Applying the two above examples to a matchcode that uses 5-digit ZIP codes, street addresses, last and first names, in that order, use the following mappings:
mapOK = mdMU->AddMapping(mdMU.CityStZip)// uses only ZIP Code mapOK = mdMU->AddMapping(mdMU.FullName) // uses last name only mapOK = mdMU->AddMapping(mdMU.FullName) // uses first name only mapOK = mdMU->AddMapping(mdMU.Address)
For a list of these enumerations, see Matchcode Mapping Enumerations.
The function returns a non-zero value if the mapping is allowed by the selected matchcode, false if the mapping caused an error.
|Syntax||int = mdMU->AddMapping(mdMU.MatchcodeMapping)|
|C||int = mdMUIncrementalAddMapping(mdMU, mdMU.mdMatchUpMatchmodeMapping)|
|.Net||integer = mdMU.AddMapping(mdMU.MatchcodeMapping)|