MatchUp Object:Hybrid:Mapping - Revision history

Admin at 20:39, 5 August 2015

2015-08-05T20:39:55Z

← Older revision		Revision as of 20:39, 5 August 2015
Line 22:		Line 22:
	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:Hybrid: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:Hybrid:Match Key#AddField\|AddField]] function.

	The function accepts an enumerated value of the type MatchcodeMapping. It tells the Hybrid 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:Hybrid:Match Key#AddField\|AddField]] function.		The function accepts an enumerated value of the type [[MatchUp Object:Enumerations#MatchcodeMapping\|MatchcodeMapping]]. It tells the Hybrid 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:Hybrid: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 database contains a single “City/State/ZIP" field, simply add the CityStZip mapping and pass the full string to the [[MatchUp Object:Hybrid: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 database contains a single “City/State/ZIP" field, simply add the CityStZip mapping and pass the full string to the [[MatchUp Object:Hybrid:Match Key#AddField\|AddField]] function later. MatchUp Object is smart enough to use only the information it needs.

Admin at 18:12, 5 August 2015

2015-08-05T18:12:01Z

← Older revision		Revision as of 18:12, 5 August 2015
Line 37:		Line 37:
	</pre>		</pre>

	For a list of these enumerations, see [[MatchUp Object:#~~Enumerations:~~MatchcodeMapping\|Matchcode Mapping Enumerations]].		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.

Admin at 21:13, 31 July 2015

2015-07-31T21:13:32Z

← Older revision		Revision as of 21:13, 31 July 2015
Line 37:		Line 37:
	</pre>		</pre>

	For a list of ~~the~~ enumerations, see [[MatchUp Object:~~Matchcode Mapping~~#Enumerations\|Matchcode Mapping Enumerations]].		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.

Admin: Created page with "{{MatchUpObjectHybridNav |FunctionsCollapse= }} {{CustomTOC}} Before generating match keys for the records in the database, the code must supply the Hybrid with information..."

2015-07-31T00:26:35Z

Created page with "{{MatchUpObjectHybridNav |FunctionsCollapse= }} {{CustomTOC}} Before generating match keys for the records in the database, the code must supply the Hybrid with information..."

New page

{{MatchUpObjectHybridNav
|FunctionsCollapse=
}}

{{CustomTOC}}

Before generating match keys for the records in the database, the code must supply the Hybrid 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 is required to perform multiple deduping operations in a single session.

{{ Object Syntax
|Syntax=mdMU->ClearMappings()
|C=mdMUHybridClearMappings(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 [[MatchUp Object:Hybrid:Match Key#AddField|AddField]] function.

The function accepts an enumerated value of the type MatchcodeMapping. It tells the Hybrid 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:Hybrid: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 database contains a single “City/State/ZIP" field, simply add the CityStZip mapping and pass the full string to the [[MatchUp Object:Hybrid: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:Hybrid:Match Key#AddField|AddField]] function.

Let’s apply the two above examples to a matchcode that uses 5-digit ZIP codes, street addresses, last and first names, in that order:

<pre>
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)
</pre>

For a list of the enumerations, see [[MatchUp Object:Matchcode Mapping#Enumerations|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.

{{ Object Syntax
|Syntax=int = mdMU->AddMapping(mdMU.MatchcodeMapping)
|C=int = mdMUHybridAddMapping(mdMU, mdMU.mdMatchUpMatchmodeMapping)
|.Net=integer = mdMU.AddMapping(mdMU.MatchcodeMapping)
}}

[[Category:MatchUp Object]]