Set Up Historical Trend Reporting
Historical trend reporting allows you to track how field values have changed over time.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions |
| Available in: Enhanced Folder Sharing |
| User Permissions Needed | |
|---|---|
| To create, edit, and delete reports in private folders: | Create and Customize Reports |
| To create, edit, and delete reports in public and private folders: | Report Builder |
When setting up historical trend reporting, keep in mind that retaining historical data increases storage requirements. For effective historical reports, you need enough data for meaningful results but not so much that you risk exceeding space limits. Consider which fields contain useful historical data and which you can omit.
The effect of historical reporting on amount of data depends on the way your organization works. For example, historical trending data for the Status field on the Opportunity object takes up more space if the record changes one time per week vs one time per month.
- From Setup, enter Historical Trending in the Quick Find box, then select Historical Trending.
-
Select the object that you want to do historical trend reporting on.
You can select Opportunities, Cases, Forecasting Items, and up to 3 custom objects.
- Select Enable Historical Trending.
-
To narrow down the amount of data that’s captured for historical trend reporting, use
the filters under Configure Data.
You can narrow down historical data for Opportunities, Cases, and custom objects. For Forecasting Items, the available data is selected for you.For example, to reduce the data stored for Opportunities reports, you can forego historical tracking on deals that aren’t active opportunities by setting Stage not equal to Closed.
- Under Select Fields, choose up to 8 fields to make available for historical trend reporting. For Opportunities reporting, 5 fields are preselected: Amount, Close Date, Forecast Category, Probability, and Stage. You can add 3 more. For Forecasting, all 8 available fields are pre-selected.
- Click Save.
After you enable historical trending, a new report type is available when you create future reports. For example, if Opportunities is enabled for historical trending, a new report called “Opportunities with Historical Trending” is available when you create a report. If you enable historical trending on a new field, that field is automatically added to the historical trending report layout.
For opportunities, historical data is collected even if historical trending isn’t enabled. If historical trending is enabled, the historical reports include all the data for the specified time range, including data from prior to when historical trending was enabled. The collection is subject to data limits for historical trend reporting.
When you turn off historical trending, keep these points in mind.
- In Developer Edition orgs, you can’t turn off historical trending on a custom field that is part of a released managed package. This is to avoid issues that arise during subsequent installations of the package. To turn off tracking on a custom field that is part of an unreleased version of a managed package in a Developer Edition org, contact Salesforce support.
- Turning off historical trending for a field hides the historical data for that field. If you re-enable historical trending, historical data for the field can be viewed again, including data created after historical trending was turned off.
- Turning off historical trending for an object causes all historical data and configuration settings to be deleted for that object. The object’s historical trending report type and any reports that have been created with it are also deleted.
- If you turn off historical trending for a field and delete it, the field’s historical data is no longer available even if you re-enable historical trending.
- The historical fields available to each user depend on the fields that user can access. If your permissions change and you can no longer see a given field, that field’s historical data also becomes invisible.
- Each historical field has the same field-level security as its parent field. If the field permissions for the parent field change, the historical field’s permissions change accordingly.
