Prepare Reporting Snapshots

Tips on Source Reports for Reporting Snapshots

• If you save a tabular source report with its details hidden, the report will not be available to include in a reporting snapshot. Furthermore, if you hide the details of a tabular source report included in a reporting snapshot, the reporting snapshot will fail when it runs. To verify that the details of the tabular source report are not hidden, view the report, click Show Details, and save the report. The Show Details button only displays if the report's details are hidden.
• When creating the source report for your reporting snapshot, note the names of the fields you added to the report, as those field names may be useful to you when you create fields on the target object in which to store the report results.
• You can choose any custom tabular or summary report as the source report, except legacy forecast reports, Quota vs Actual reports, and Leads by Source reports. The Source Report drop-down list does not display standard reports..
• You can include up to 100 fields in your source report.
• You can delete the schedule of when a reporting snapshot runs. You can’t stop or pause a reporting snapshot when it is running, nor can you delete its source report. To delete the source report, you must first remove the report from the reporting snapshot by changing the report in the Source Report drop-down list..
• If you select Load No Data in the Fields from Source Report column, no data will load into the corresponding field in the Fields in Target Object column when the reporting snapshot runs. .
• The (No fields with compatible data type) field displays in the Fields from Source Report column when a field on the target object does not match the data type of a field on the source report..

Tips on Target Objects for Reporting Snapshots

Consider the following when setting up target objects for reporting snapshots:

• In Professional, Enterprise, Unlimited, Performance, and Developer Editions, use field-level security to make the target object's fields visible to the appropriate users.
• You can’t delete a custom object if it’s a target object in a reporting snapshot.
• The fields on the target object determine field mapping availability. For example, your source report may include ten fields, but if your target object includes one field, then you can only map one field in your reporting snapshot.
• You can add up to 100 fields to the target object.
• Target objects cannot contain validation rules or be included in a workflow.
• Reporting snapshots cannot contain target objects that trigger Apex code to run when new records are created..
• When a reporting snapshot runs, it can add up to 2,000 new records to the target object. If the source report generates more than 2,000 records, an error message is displayed for the additional records in the Row Failures related list. You can access the Row Failures related list via the Run History section of a reporting snapshot detail page.

Tips on Reporting Snapshots

• Be aware of the type of license your Running User has. For example, if the Running User of a reporting snapshot has a Salesforce license, users who have Lightning Platform or Salesforce Platform One licenses will not be able to view it. Alternatively, if the Running User has a Lightning Platform or Salesforce Platform One license, users who have Salesforce licenses will be able to see the reporting snapshot. If you have users with Lightning Platform or Salesforce Platform One licenses, we recommend creating a separate reporting snapshot for them with a Running User that has a Lightning Platform or Salesforce Platform One user license.
• You can only map fields with compatible data types. For example, you can map a currency field to a number field.
• If you change the source report or target object on a reporting snapshot with existing field mappings, the field mappings are deleted when you save the reporting snapshot. You can also view Summary Fields in Source Report and Fields in Target Object to see the number of summary or target fields, respectively..
• You must map at least one field from the source report to one field on the target object or data will not load from the source report to the target object when the reporting snapshot runs.
• When a reporting snapshot is defined, deleted, or its source report or target object is changed, it is tracked in your organization's setup audit trail history.
• The Run History section on a reporting snapshot detail page displays details on when the reporting snapshot ran. Details include:
  • The date and time at which the reporting snapshot ran
  • The name of the source report, target object, and running user
  • The time it took for the reporting snapshot to run
  • The total number of detail or summary rows in the source report, depending on the report type
  • The number of records created in the target object
  • Whether or not the reporting snapshot ran successfully