MatchUp Object:Read-Write:Mapping: Difference between revisions
Created page with "{{MatchUpObjectReadWriteNav |FunctionsCollapse= }} {{CustomTOC}} Before generating match keys for the database records, the application must supply the Read-Write interface ..." |
No edit summary |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 17: | Line 17: | ||
==AddMapping== | ==AddMapping== | ||
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 [[MatchUp Object:Match Key#AddField|AddField]] function. | 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 [[MatchUp Object:Read-Write:Match Key#AddField|AddField]] function. | ||
The function accepts an enumerated value of the type | The function accepts an enumerated value of the type [[MatchUp Object:Enumerations#MatchcodeMapping|MatchcodeMapping]]. It tells the Read-Write 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 [[MatchUp Object:Read-Write:Match Key#AddField|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 data in the list uses a single “City/State/ZIP" field, simply add the CityStZip mapping and pass the full string to the [[MatchUp Object:Match Key#AddField|AddField]] function later. MatchUp Object is smart enough to use only the information it needs. | 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 data in the list uses a single “City/State/ZIP" field, simply add the CityStZip mapping and pass the full string to the [[MatchUp Object:Read-Write:Match Key#AddField|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 database contains only full names. The application would simply apply the FullName mapping twice and pass the full name data twice to the [[MatchUp Object:Match Key#AddField|AddField]] function. | In another example, a matchcode calls for both last name and first name but database contains only full names. The application would simply apply the FullName mapping twice and pass the full name data twice to the [[MatchUp Object:Read-Write:Match Key#AddField|AddField]] function. | ||
To demonstrate the above: | To demonstrate the above: | ||
| Line 34: | Line 34: | ||
</pre> | </pre> | ||
For a list of | For a list of these enumerations, see [[MatchUp Object:Enumerations#MatchcodeMapping|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. | The function returns a non-zero value if the mapping is allowed by the selected matchcode, false if the mapping caused an error. | ||
Latest revision as of 20:26, 5 August 2015
| MatchUp Object Read-Write Interface Navigation | ||||||
|---|---|---|---|---|---|---|
| Overview | ||||||
| Order of Operations | ||||||
|
Before generating match keys for the database records, the application must supply the Read-Write interface with information about what sort of data it will be handling.
ClearMappings
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.
| Syntax | mdMU->ClearMappings() |
|---|---|
| C | mdMUReadWriteClearMappings(mdMU) |
| .Net | mdMU.ClearMappings |
AddMapping
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 Read-Write 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 data in the list uses 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 database contains only full names. The application would simply apply the FullName mapping twice and pass the full name data twice to the AddField function.
To demonstrate the above:
mdMU->AddMapping(mdMU.CityStZip) // uses only ZIP Code mdMU->AddMapping(mdMU.FullName) // uses last name only mdMU->AddMapping(mdMU.FullName) // uses first name only 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 = mdMUReadWriteAddMapping(mdMU,mdMU.mdMatchUpMatchmodeMapping) |
| .Net | integer = mdMU.AddMapping(mdMU.MatchcodeMapping) |