- 30 Jun 2021
- 6 Minutes to read
- Updated on 30 Jun 2021
- 6 Minutes to read
Cloudingo's Find Data feature lets you upload data from a spreadsheet (like names) to find corresponding data in Salesforce (like record IDs) for any object, any field - including related object data. Simply upload your file and scan it to see if the information already exists in Salesforce, specify what field values you want to pull back from Salesforce if we find a match, then download the results into a .csv file to further manipulate, import, or update Salesforce records.
To navigate, choose Find Data from your Dashboard menu options.
Tab 1: Choose Object and Upload File
This is where you will upload your file and choose which object you need to scan to identify if a matching record exists.
- Description: Name your upload
- Salesforce Object: Select the object (type of record) that you will be performing your scan on to look for existing records. In this example, we are loading a file to attempt to find the Account ID (based on Account Name), so the object would be set to Account. You can select any standard or custom object from the list. Your file can contain values from other related objects and that data will be retained in the Export file.
- File Data Source: File must be in CSV format.
- File: Browse and find the CSV or tab delimited file on your local computer.
- File Options:
- Leave the "Has Column Headers" box checked if your file contains a header row.
- If your file contains European date format (dd/mm/yyyy) instead of US date format (mm/dd/yyyy), check this box.
- Decimal separator for numeric values default is to use comma separators for numeric, choose 'Period' if your file contains Period separators instead of comma.
Click the Load & Continue button.
Tab 2: Select & Map Fields
Cloudingo will attempt to auto-map all columns in your file to the corresponding fields in Salesforce.
All fields in your file that are not mapped will automatically appear in the 'Upload Column(s) Not Mapped' section. Click the Upload Column(s) Not Mapped box to expand the list of column header names for a full view (seen above).
You must map at least one field in your file to continue with the scanning process. You only need to map fields that you intend to use as part of your matching criteria (for example, if you are looking to find the Account ID based on Account Name, City, and State, you must map all three of those fields to the corresponding Salesforce field).
All other fields can simply be set to 'Export Only' for values you just want to retain in your final export file. (Note: It is fine to map other file columns to fields, and it is fine to leave correctly auto-mapped fields mapped; it is not required.)
Check auto-mapped fields for accuracy.
To add fields for mapping or for export, find the field name in the list of available fields (on the left hand side) and check the box next to the field name.
In the example above, we are using Account Name in our file as one of the matching fields to identify existing Account IDs. Check the box to the left of the field, and it will be added to the selected list on the right hand side. The default Matching Upload Column will be set to 'Export Only'. Match the Salesforce field with the corresponding File column in the list if you need to map the field for matching. As you map fields, they will drop out of the Upload Columns(s) Not Mapped list in red.
Add & map any additional fields you will be using in your matching criteria. All mapped and unmapped fields provided in your upload will automatically be included in your export file.
Add any additional fields that you want to include in the export if a match is detected by clicking the boxes to the left of the field name in the available field list column. Leave the Matching Upload Column selection set to 'Export Only'. Fields mapped for matching will be highlighted in gray. Export Only fields will display in white.
Related object field values can also be included for mapping or for export only. Related objects will display an arrow just to the left of where the checkbox would normally be. Click the arrow to expand the related object field list. Use the search options just beneath the headers to find the field name you wish to include. Click the down arrow in the search to see filter options (Begins with, Contains, Equals, etc.). In the example below, we are including information from the User object in Salesforce to capture the Created By Username for export.
When you check the box on a related object field, it will be added to your selected field list for you to map or set to add to the Export only.
Click Continue to move on to Step 3. Click Save as template to save configurations at this stage for future use on file uploads that use the same formatting.
Tab 3: Limit Results
Click Add Condition to set any conditions that you want to use to limit which records will pull into the results (such as Record Type, Country, etc.) You may set up multiple conditions if desired.
Click Continue to move on to Step 4. Click Save as template to save configurations at this stage for future use on file uploads that use the same formatting.
Tab 4: Matching Criteria
Check this box if you DO want to include the original rows from your file (even if no match is identified). If you do NOT want non-matched records to be included in your output file, leave the 'Include CSV duplicates in results' option unchecked.
Set up your matching criteria. Cloudingo will scan Salesforce for the field(s) configured here to identify if a record match exists for the field(s) specified. If you already have a dedupe filter configured using the matching fields you wish to use, select the filter from the 'Use existing filter to populate Match Criteria' list.
Once you choose the filter from the drop list, the fields and matching conditions will automatically populate in the Match Criteria section.
Make any changes as necessary.
Click Add Match Condition if you need to add another field match to the existing matching criteria. Note: You will receive an error if you have no more additional fields mapped (in Step 2) for matching.
Filters are only available for copying field match configurations for quick entry. The matching criteria here is completely independent of your filters. Changes made on this page will not impact existing filters.
You can run your file through two matching criteria scans if desired. Select a second filter from the filter list at the top of the page to pre-populate a second scan matching criteria. Or click the Add Another Scan option to manually setup your second configuration for matching.
Click Save as template to save configurations at this stage for future use on file uploads that use the same formatting.
Click Find Data to run the scanning process to obtain your results and export data.
Tab 5: Review Data and Export
All columns from the original upload, plus additional columns (if a match was detected) will be included in the retrieved data.
The first column (Match Count) will display how many record matches were detected. Counts include both Salesforce record matches and file duplicate matches. Each row in the output will display an arrow to the left of the Match Count column. Click the arrow to expand details for the record you wish to view on the screen.
You can make adjustments to your Find Data criteria in previous tabs if necessary and re-scan the file again from tab 4 (Matching Criteria).
Click Export Results to export all data to a new CSV file. Output can then be manipulated in Excel and re-saved to CSV for import if necessary.