Salesforce reports, dashboards, and analytics
In the final post of this series, we’ll discuss some advanced considerations that I’ve been compiling over the years. These are suggestions you may want to implement right away or tuck away in your toolbox if you haven’t encountered these scenarios.
While it may take some time to clean up existing reports, you can start enjoying the benefits of deluxe report types right away. Only create new reports with deluxe report types (or other styles with a better understanding of how object relationships work).
At the heart of every report is one of the following seven query scenarios. Recognizing the query scenario when you first hear the report request will allow you to identify the best report type configuration for the job.
Imagine if you had a single custom report type per object that could address a majority of the requests you have to create a report using data from that object. This is similar to the concept of “one process builder per object” or “one trigger per object” – you create one custom report type per object that you want to report on.
When working with reports in Salesforce, you will find that report types have a major effect on what you are able to manipulate. Report types control what report results have the potential to show, what objects you have access to, what fields are available, and how certain report features will behave. This is the first filter being applied to the data.
ReportForce 