Contact Zone:MatchUp:Field Mapping - Revision history

Admin at 00:28, 5 January 2017

2017-01-05T00:28:06Z

@@ Line 1: / Line 1: @@
-[[Contact Zone:Reference|&larr; Contact Zone Reference]]
+{{ContactZoneMatchUpNav
+|MatchUpCollapse=
-{| class="mw-collapsible" cellspacing="2" style="background-color:#f9f9f9; border:1px solid #aaaaaa; font-size:9pt; color:#0645ad; padding:8px 8px;"
+}}
 {{CustomTOC}}

Admin at 00:55, 24 June 2014

2014-06-24T00:55:00Z

@@ Line 37: / Line 37: @@
 |[[Contact Zone:MatchUp:Output Filter|Output Filter]]
 |}
 |-
+|

Admin at 18:39, 23 June 2014

2014-06-23T18:39:41Z

← Older revision		Revision as of 18:39, 23 June 2014
Line 62:		Line 62:
	These are the mappings for the table used as a filter when matched against Source records. The Options tab allows you to specify whether only the Source records matching the Lookup records (intersected) will be output, or whether these matches will be suppressed from the output. When there is only a single input source connected to the MatchUp Component, this section will not be visible.		These are the mappings for the table used as a filter when matched against Source records. The Options tab allows you to specify whether only the Source records matching the Lookup records (intersected) will be output, or whether these matches will be suppressed from the output. When there is only a single input source connected to the MatchUp Component, this section will not be visible.

	~~===~~Matchcode Data~~===~~		;Matchcode Data
	For each component in a matchcode, this is the associated data type.		:For each component in a matchcode, this is the associated data type.

	~~===~~Input Column~~===~~		;Input Column
	For every matchcode component, you must map in the table column which will provide the data needed to compare records. You are only required to map one address line if the source contains a single address column.		:For every matchcode component, you must map in the table column which will provide the data needed to compare records. You are only required to map one address line if the source contains a single address column.

	~~===~~Input Data Type~~===~~		;Input Data Type
	For each input column provided, an additional mapping is required to tell the component the format of the incoming data. This allows you to process tables in various formats without having to pre-parse input data to satisfy matchcode component datatypes. For example, a matchcode requiring a last name can receive a FullName, LastName, InverseName, etc. as inputs. The component will correctly parse and extract the input data needed to build the match key.		:For each input column provided, an additional mapping is required to tell the component the format of the incoming data. This allows you to process tables in various formats without having to pre-parse input data to satisfy matchcode component datatypes. For example, a matchcode requiring a last name can receive a FullName, LastName, InverseName, etc. as inputs. The component will correctly parse and extract the input data needed to build the match key.


	[[Category:Contact Zone]]		[[Category:Contact Zone]]

Admin: Created page with "← Contact Zone Reference {| class="mw-collapsible" cellspacing="2" style="background-color:#f9f9f9; border:1px solid #aaaaaa; font-size:9pt; c..."

2014-06-23T17:56:13Z

Created page with "← Contact Zone Reference {| class="mw-collapsible" cellspacing="2" style="background-color:#f9f9f9; border:1px solid #aaaaaa; font-size:9pt; c..."

New page

[[Contact Zone:Reference|← Contact Zone Reference]]

{| class="mw-collapsible" cellspacing="2" style="background-color:#f9f9f9; border:1px solid #aaaaaa; font-size:9pt; color:#0645ad; padding:8px 8px;"
! style="text-align:left; color:black; border-bottom:1px solid #aaaaaa;"|'''MatchUp Navigation'''
|-
| style="padding-right:220px;"|
|-
|[[Contact Zone:MatchUp|Overview]]
|-
|[[Contact Zone:MatchUp Editions|Editions]]
|-
|[[Contact Zone:MatchUp Tutorial|Tutorial]]
|-
|
{| class="mw-collapsible mw-collapsed" style="width:100%;"
|- align="left"
! style="color:black;"|[[Contact Zone:MatchUp:Component Settings|Component Settings]]
|-
|[[Contact Zone:MatchUp:Component Settings#Show Details (On-Premise)|Show Details (On-Premise)]]
|}
|-
|
{| class="mw-collapsible" style="width:100%;"
|- align="left"
! style="color:black;"|MatchUp Tabs
|-
|[[Contact Zone:MatchUp:Matchcode|Matchcode]]
|-
|[[Contact Zone:MatchUp:Field Mapping|Field Mapping]]
|-
|[[Contact Zone:MatchUp:Options|Options]]
|-
|[[Contact Zone:MatchUp:Source Pass-Through|Source Pass-Through Columns]]
|-
|[[Contact Zone:MatchUp:Lookup Pass-Through|Lookup Pass-Through Columns]]
|-
|[[Contact Zone:MatchUp:Output Filter|Output Filter]]
|}
|-
|
{| class="mw-collapsible mw-collapsed" style="width:100%;"
|- align="left"
! style="color:black;"|Result Codes
|-
|[[Returned Result Codes:Enterprise Solutions#Contact Zone|Returned Result Codes]]
|-
|[[Result Codes]]
|}
|}

{{CustomTOC}}

This tab maps which source column and its corresponding datatype will be used for each matchcode component.

[[File:CZ_MU_FieldMapping.png|link=]]

==Source Mapping==
These are the mappings for the table used to provide the records to be deduped for output. For a single table process, this Source is required. You cannot configure the component with a single Input source mapped into the Lookup pin.

==Lookup Mapping==
These are the mappings for the table used as a filter when matched against Source records. The Options tab allows you to specify whether only the Source records matching the Lookup records (intersected) will be output, or whether these matches will be suppressed from the output. When there is only a single input source connected to the MatchUp Component, this section will not be visible.

===Matchcode Data===
For each component in a matchcode, this is the associated data type.

===Input Column===
For every matchcode component, you must map in the table column which will provide the data needed to compare records. You are only required to map one address line if the source contains a single address column.

===Input Data Type===
For each input column provided, an additional mapping is required to tell the component the format of the incoming data. This allows you to process tables in various formats without having to pre-parse input data to satisfy matchcode component datatypes. For example, a matchcode requiring a last name can receive a FullName, LastName, InverseName, etc. as inputs. The component will correctly parse and extract the input data needed to build the match key.

[[Category:Contact Zone]]