DemandTools Find/Report ID’s - Single Match Per Line of Export File

• Separate output files will be created for matched records vs. non-matched records
• File of non-matches is optional
• The matched export file will contain a SEPARATE ROW for each unique existing matched record
  • For example: If a single input record matches to 2 DIFFERENT (unique) existing records then the single row in the input file will write out 2 rows to the export file

Export Options: Single Match Per Line of Export File


 
1.    Select the radio button for Single match per line of export file
2.    Specify which step to write matches for

• Write first match ONLY
  • Return the first unique match from the first match step that caught the record as a match (may not be from Match Step 1)
• Write all unique matches from first matched step
  • Returns all the unique matches from the first matching step where at least one match was found (may not be from Match Step 1)
• Write all unique matches from all matched steps
  • Returns all unique matches from all matching steps

3.    Save file of non-matches

• OPTIONAL:  Returns, in a separate file, all records where no matches could be found
  • The file name for this file will be the filename specified when Export Data is selected with _NonMatch appended ({filename}_NonMatch)

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 MATCHED 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.

Note:  The "NonMatch" file will JUST contain the input fields for the non-matched records.

• 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)
• CRMfusionField_UniqueMatchCount
  • Number of UNIQUE existing records matched for the record in that row
    • If an input record is matched to the SAME Salesforce record in Match Step 1 and Match Step 2 the MatchCount will be 2 and the UniqueMatchCount will be 1.
• Match__CRMfusion__MatchKey
  • The duplicate key created based on the Match Step #
    • Matched Fields and Mapping Types used to find the resulting match
    • 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
• 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"
• 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 object 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}.