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.
If you have created a Salesforce report you have probably used a report filter. Whether this has been by time period, such as created date, or by sales rep or … Continue Reading Two Additional Ways to Filter Your Reports
Formulas are a valuable tool within Salesforce to help with calculating values. You have probably created formula fields on your objects, but did you know that you can also use … Continue Reading Getting Started with Report Formulas
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.
The report engine in Salesforce relies on the relationships that are explicitly defined in order to join together data from multiple objects. This means your data architecture determines what native Salesforce reports will be capable of producing. Here are four concepts to consider for data modelling that will allow you to build the reports you desire.