When to use reporting snapshots
Key Takeaway
Standard reports show only current data. When a business needs point-in-time or trend reporting, use a reporting snapshot. A reporting snapshot runs a custom source report on a schedule and saves each run's results as records in a custom object.
A reporting snapshot runs a custom report on a schedule and saves the results as new records in a custom object. Each run adds more records, so over time the custom object holds a history of point-in-time data. Users can build reports and dashboards on that history to spot trends. Standard reports can't give you that history because they show only the current state of your data.
When to use a reporting snapshot
Standard reports give up-to-the-minute results on the current state of your business. Because they show only the current state, they can't tell you how things looked last week or last month. A reporting snapshot keeps that history by saving a report's results on a schedule. Use one when a business needs point-in-time or trend reporting, not just a view of today.
A warehouse manager tracks stock in a custom object called Inventory Item. Her custom report "Stock by Product" shows how many units of each product are in stock right now, but the numbers change all day as orders ship. She wants to know whether stock levels are falling over the month. She sets up a reporting snapshot that runs "Stock by Product" every day and saves the results in a custom object called Stock History. After 30 days, Stock History holds 30 sets of records, one set for each run. She creates a report on Stock History to compare stock levels across the month, and she adds that report to her dashboard. Meanwhile, "Stock by Product" still shows only today's stock.