Exports information from any standard or custom object in Salesforce
- Export is the only operation in MassEffect that DOES NOT REQUIRE selecting an input file to begin
- By default, the tables shown in MassEffect will be based on the selected operation on the right
- To show ALL tables, even read-only tables (e.g. those that CANNOT be directly inserted/updated) select the operation Export Records
Common Uses
- Find the Salesforce ID fields of the users and roles to use for inserts/update
- Find the Salesforce ID's of objects that will become parent ID’s for other objects being inserted/updated
- Export data for reporting
- Find the Salesforce ID's of objects to mass delete
- Export data, make modifications in the spreadsheet and then upload the changes
- An unlimited number of records can be exported to a csv file
- Export deleted records or archived activities
- DECODE Documents, Attachments and Content Files and save the files locally to the PC Content
Compatible Data Sources
• .xls
• .xlsx
• .mdb (NOT AVAILABLE in 64bit DemandTools)
• .accdb
• .dbf
• .csv
• .xml
• .tab
• .sql
Step 1. Select the Export Operation
To export the contents of a table, right click on the table name and the export table dialog box will appear.
Step 2. Select Which Records to Export and Fields to Download to Output File
- Where Condition: Choose Use all or Use conditions to specify which records should be exported
- Add Conditions: If Use conditions selected, build conditions by selecting the field name, an operator, and the value
- Fields to Download: Check the boxes for fields to download to the output file or by click Check all to include all fields for that table
- Quick ways to find a desired field:
- Right click in the list of fields to bring up a Filter field option
- Type the first letter of a field name to scroll to the first field with that character.
- Quick ways to find a desired field:
- Export Deleted/Archived Objects: This option determines if deleted records or archived Tasks/Events should be included in the export
- Unchecked: Only active records, and un-archived Tasks and Events will be exported
- Checked: Deleted records AND archived Tasks/Events will be included in the export along with the active and un-archived records
Note: The specific conditions regarding IsDeleted or IsArchived equal True will ONLY work when the Export Deleted/Archived Objects box is ALSO checked. Hard deleted records that have been "marked for deletion" but not physically removed from Salesforce will be included along with soft deleted records (those still in the recycle bin).
Step 3. Specifying the Output File and Exporting the Data
- CSV Custom Settings: Specify the CSV separator and desired encoding
- the dropdown contains Comma and Tab, but you can manually type a character (e.g. |)
- Export File Name Additions: Optionally check the appropriate box to append either the current date and or current time to the export file name.
- Helpful when running as a batch process so as to NOT overwrite a previous export file with the same name
- Export Data: Select to specify the output filename and start the export
- Enter the output file name and location in which to save the file and select a filetype
- Supported file types include xls, xlsx, dbf, csv, mdb (32bit only), accdb, xml, tab and sql
- Object Download Status: Shows the status of the download and reports how many total records were exported
Once complete a pop-up will display a direct link to the exported data file.
Scenarios
Export routines can be saved and reloaded. Exports can also be scheduled using DemandTools JobBuilder.
Decoding Documents, Attachments and Content
Option available to decode the files and save them locally in a specified directory. If this option is not selected, then the files will be exported as 64-base encoded. The Document/Attachments Settings will ONLY be shown when exporting one of these objects. The option appears just below the field to display on the output file on the right.
Decoding these files is only recommended when exporting a small subset of files as the actual files will be saved on the PC and the storage usage could be significant if exporting a large amount of files. When exporting Attachments, Documents or Content for a data migration to another Salesforce instance it is recommended to export as 64-base encoded (the default) as these can be re-imported easily without having to re encode them.
- Check to decode the files as they are being exported
- Select Directory: Specify a directory where the files should be created/saved
- A file name will still need to be specified when Export Data is selected
- This file will contain a list of the files that were exported
- When the export is complete the decoded files will be in the specified directory
- For Documents and attachments, the file names will use the "Name" field from the table
- For Content, the file name will be extracted from the pathname in "VersionData" field
- If multiple files are exported with the SAME NAME, they will not be overwritten, but rather will have an _X number appended to the filename (e.g. image.jpg, image_2.jpg, image_2.jpg etc.)
Note: Only Content Files will be decoded and written to the PC. Content URL's will be included in the list of files that were exported (the file name specified when exporting) but there will be no actual files written to the specified directory on the PC.
