Home > DemandTools for AppExchange Modules > DemandTools - Discovery Module > Find/Report IDs - Compare External Data to Salesforce
Find/Report IDs - Compare External Data to Salesforce
The DemandTools FindIDs module was developed to allow for the comparison of an external data source, such as a spreadsheet, to the contents of any table of information in Salesforce.com.
Step 1. Choose an input file to compare to an object in Salesforce
1. Select the file by clicking the "Select File" button
2. Browse to find the file
3. If an .xls, .xlsx or .mdb file has been chosen the user must select the worksheet/table name to process by clicking on it (will highlight in blue). Click the "Use" button on the right or double click to select.
4. The number of records loaded will be displayed in red
Step 2. Selecting the object for comparison and the fields to show on the output file.
1. Choose the Salesforce object in which to compare the external data to, using the drop down box.
2. Click the "Use Object" button (this will populate the left side of the table with fields from the selected object as well as fields from tables related to that object).
3. Check the boxes next to the Salesforce fields to include them in the output file (Tip: select the fields that will aid in verifying a true match) The selected fields will be listed on the right side of the screen.
4. (Optional) To reorder the selected fields, click on the number in the order column. Use the arrows to change the order. (Tip: If field order is changed on one field, it will need to be updated manually on the others).
5. Click the "Step 2 - Conditions & Settings" button to continue (The button is on the lower right side of the interface).
Step 3. Selecting the Salesforce data for comparison & match conditions.
1. Select the "Use All" or "Use Conditions" radio button

Step 4. Create mapping - fields in the external data to match against fields in Salesforce.
1. Click the "Add Mapping Condition" button.
2. Choose the field from the external data in the Input Column.
3. Choose the Salesforce field in the Field to Match column.
4. Choose the Mapping Type and apply Fuzzy, Transpose or Alpha Clean if so desired.
Example: The external data has a company name field, match that field to the name (account name) field in Salesforce and use the Cleaned Account Name mapping type to find a match between the information.

|
Type Description: |
Found in Category: | ||
|
The Cleaned Account Name mapping type uses the built in Account Name Cleaning List. To see the Cleaning list tool select the "Edit Account Cleaning List" button.
The cleaning list standardizes punctuation, spaces and removes common business prefixes and suffixes. These lists are customizable for language(s) and/or line of business. |
All, CRM | ||
|
The Country Match mapping type is used to standardize field values for the recognized countries of the world. It will recognize the long name of a country, the 2 digit ISO short form, the 3 digit ISO short form and the numeric ISO country value as possible matches of each other. |
All, GEO | ||
|
The Domain mapping type is used when mapping web pages and/or email addresses. It allows for the independent analysis of the domain information contained within the URL or the email address. For email addresses it uses any information to the right of the @ sign. For web pages it parses the XXXXX.com portion. This mapping types allows for easy comparison of web page field vs. web page field or email field vs. email field. It also allows for the comparison of email addresses to web pages and vice versa. |
All, Internet | ||
| The Exact mapping type is a 100% match of every character (assuming no options apply (see Fuzzy, Transpose & Alpha Clean)) |
All, Alpha, Numeric | ||
|
The First Name mapping type uses the built in Nickname List. To see the Nickname list select the "Edit Nickname List" button at the top of the interface.
The Nickname list will see Bill, William and Billy as potential duplicates/matches of each other. This list is also customizable by the end user for localization or for non contact substitution on any field by replacing the nickname list with synonyms. |
All, Contact | ||
| The First XX Letters mapping technique is used to compare the first XX letters in a field. When selected a pop up box will appear in order to specify the number of letters on which to match. Applicable to text fields only. |
All, Alpha | ||
| The Numeric mapping type is used to compare only the numeric values in a field. All other characters, such as spaces or punctuation, will be ignored by the deduper. A field with a value of "Apt # 31" is seen by the deduper as the numeric characters "31", ignoring "Apt #". |
All, Numeric | ||
|
The Relaxed Address Match mapping type parses the street address to the lowest common denominator. Based on North American standards it has also proved effective with most country address formats. Example: |
All, CRM | ||
| The Relaxed NA Phone Match mapping type removes all non-numeric characters and spaces, leading 0's and 1's, area codes and extensions on the back end, returning the 7 primary digits of the phone number. If just 7 digits are left use those 7 digits, else just return digits 4 - 10. It will not match the "Phone-word" values and will trim off the "SPOT" in the phone number and only look at the numeric portion. Example: +1 879 555 1212 ext 500 (879) 555 1212 1.879.555.1212 ext 408 Are all seen as "5551212" Note: This is based on a 10-digit North American phone number. Although it can be used with international phone numbers (will just return 7 digits in the middle), the Numeric mapping type is the recommeded mapping type to be used with international phone numbers. |
All, CRM | ||
| The Salesforce.com ID Match mapping type is used to match any Salesforce.com objects 15 digit ID to its 18 digit equivalent ID and vice versa. |
All, CRM | ||
| The Street Address Match mapping type is a slightly more rigid criteria than the relaxed address match mapping type. The deduper will ignore the differences in street type short forms such as crescent - cres, road - rd, street - st, etc. |
All, CRM | ||
| The Zip 5 and 9 mapping type will automatically match USPS 5 and 9 digit zip codes without the need to standardize them to a common number of digits. |
All, CRM |
Additional Mapping Options
| Option: | Description: | Applicable Mapping Types: |
| Fuzzy | Phonetics engine capable of analyzing words for how they sound when pronounced. Through a technique of removing vowels and analyzing the remaining consonants the fuzzy engine works well for matching fields with spelling mistakes. | Cleaned Account Name Exact FirstName |
|
Transpose |
The transpositional engine allows for fields to appear as duplicates even when there are differences in their word order. For example, "Jones, Smith and Jackson" will appear to be a duplicate of Jackson, Smith and Jones. |
Cleaned Account Name Exact FirstName Street |
|
Alpha-Clean |
The alpha cleaner extends some of the capabilities of the account name cleaner to other fields for easier matching. The alpha cleaner is used for ascii (north american) data to ensure that the only characters that are analyzed are the 26 characters of the english alphabet and the numbers 0-9. Any other character that the field may contain will be ignored by the deduplication matching algorithms. |
Cleaned Account Name Exact FirstName Numeric Street Zip 5 and 9 |

FindID's Results File
The FindID's results file starts with the original columns of information from the incoming data source. DemandTools FindID's appends additional columns to the right of the original input data. In the example above, Columns A,B and C were original data and D,E,F, etc. were added by DemandTools. The first added column shows the duplicate key that was used to locate the match. The next column, Match_1_sf, holds the Salesforce ID's for the first matching Salesforce record(according to the users matching conditions). The remainder of the columns show the data from the selected fields in Step 2. There is the possibility that more than one record in Salesforce matched to the input data; this is very dependent on the selection of match conditions. DemandTools FindID's will report data sets for the first 5 returned matching records. Note: This is/could be seen as a symptom of duplicates in the existing Salesforce database.
If there is no ID in the Match_ID_1 column then there were no matching records (according to user conditions) found in Salesforce.
See also