- All input records written to the output file
- Matched ID's/fields will be listed in columns appended AFTER the input data
- Columns will be created for the number of matches per line specified (see below)
- For Example: Match_1, Match_2, Match_3, etc.
- Users can choose to write up to 10 matches per line
- Input records that DID NOT match any existing records will be written to the file also
- MatchCount & UniqueMatchCount columns will show "0", all other "Match" fields will be blank.
Export Options: Multiple Matches Per Line of Export File
1. Select the radio button for Multiple matches per line of export file
2. Specify the Maximum number of matches per line
- Can be as low as 1 and as high as 10
- Use Up/Down arrows to change the count
3. Specify which match step to write matches for
- Write all unique matches from first matched step up to maximum
- Returns all the unique matches from the first matching step where at least one match was found
- The Match Step that caught the matching record may not be from Match Step 1
- If a match was not able to be caught in match Step 1, but was found in Match Step 2, then the result from Match Step 2 will be written out to the file.
- Write all unique matches from all matched steps up to maximum
- Returns all unique matches from all matching steps
- Only up to 10 matches can be written to the export file
- Each match is written to a separate set of match columns, e.g.
- First matched record data written to "Match_1" columns
- Second matched record data (if there are additional matching records) written to Match_2 colums etc.
- To determine which step found the match, see the Match_#_CRMfusion__MatchStep field (see below)
4. Optionally specify additional Export File Name Additions
- Allows the user to Append the Date and/or Time of the export automatically to the name of the file
Example Match Data/Resulting File:
1. Data from Input file
2. Informational columns added (see below for details)
- If additional fields were requested to be added to the output file (in Step 1, Fields to show on final output file) they will be shown after the Match_#_Id and the column names will be "Match_#_{fieldname}.
3. Match_#_Id: The Unique ID's for any matched records
Columns Added (by DemandTools) to the Export File
DemandTools will automatically add fields to the export file between the input file fields and the selected fields to return for the export, e.g. to the right of the input file fields and to the left of the selected fields to return.
- CRMfusionField_MatchCount
- TOTAL number of times a match was found across all matching steps for the record in that row
- This MAY NOT BE THE SAME as the total number of existing records matched (UniqueMatchCount)
- TOTAL number of times a match was found across all matching steps for the record in that row
- CRMfusionField_UniqueMatchCount
- Number of UNIQUE existing records matched for the record in that row
- If an input record matches to the SAME Salesforce record in Match Step 1 and Match Step 2 the MatchCount will be 2 and the UniqueMatchCount will be 1.
- Number of UNIQUE existing records matched for the record in that row
- Match_#_CRMfusion__MatchKey
- The duplicate key created based on the Match Step #
- Matched Fields and Mapping Types used to find the resulting match
- If the MatchCount is 0, this field will be blank
- Example of a key from a match found in Match Step 1, Matched on AccountName and Account BillingStreet: 1@abercrombie and associates_3377 compton rd ste 120_
- This information can be useful in determining what matching was used in the step, especially if the scenario was NOT saved
- The duplicate key created based on the Match Step #
- Match_#_CRMfusion__MatchStep
- The number of the match step where the match was caught
- Match_#_CRMfusion__MatchStepName
- The name of the match step
- Will use a custom name if one was provided, otherwise will just indicate the default step name
- For Example: "Match Step 1"
- Will use a custom name if one was provided, otherwise will just indicate the default step name
- The name of the match step
- Match_#_Id
- The Salesforce 18 digit ID for the matching record
- This is the field that will be used by MassEffect Update to update the existing matched records
- Mapped to the "id" field in that table when performing the update
Note: If additional fields were requested to be added to the output file (in Step 1) they will be shown next and the column names will be "Match_#_{fieldname}.