You are here:
Map Reporting Snapshot Fields
After you create a source report, target object, target object fields, and define your reporting snapshot, you can map the fields on your source report to the fields on your target object. You map source report fields to target object fields so that when the report runs, it automatically loads specific target object fields with data from specific source report fields.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: Professional, Enterprise, Performance, Unlimited, and Developer Editions |
- From Setup, enter Reporting Snapshots in the Quick Find box, then select Reporting Snapshots.
- Select the name of the reporting snapshot whose fields you want to map.
- Click Edit on the Field Mappings section.
- For summary reports, select the Grouping Level at which summary data is extracted from the source report. Data loaded into the target object is taken from summary fields at the grouping level you specify. The Grand Summary summarizes on the total for all grouping levels.
- In the Fields from Source Report column, click a Load No Data drop-down list and select a field from the source report to map to a custom object field in the Fields in Target Object column. Only summary fields can be mapped for reporting snapshots based on summary reports. Note that the fields for summary reports may vary depending on the grouping level selected.
- Click Quick Save to save field mappings and continue mapping fields, or click Save to save field mappings and return to the reporting snapshot's detail page.
- Next, schedule the reporting snapshot to run.
Consider these tips for mapping reporting snapshot fields.
- 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.
- You can only map fields with compatible data types. For example, you can map a currency field to a number field.
- A custom summary formula can be mapped only if the grouping level in the reporting snapshot and the grouping level in the custom summary formula match.
- 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.
- 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 cannot map fields from the source report to the following fields on the target object: Created By, Last Modified By, Created Date, and Last Modified Date.
- When you map fields from the source report to the target object, some data may lose its context when loaded to the target object. For example, if you map a date and time field from the source report to a text field on the target object, the date and time load to the target object without the time zone.
- When executing a reporting snapshot, if the running user does not have “read” or “write” access to a mapped field in the target object, that field is dropped from the mapping, but does not cause the execution to fail. If a required field in the target object is not mapped, the execution fails. To ensure that fields are always mapped, make them required or set default values for them.
- To map a field in the source report to a lookup field on the target object, you must map to the ID of the object associated with the lookup. For example, to map to an opportunity lookup field, you must map to the Opportunity ID. To get the Opportunity ID in the source report, you may need to use a custom report type to include ID and other related fields.
Did this article solve your issue?
Let us know so we can improve!
