How to optimize Salesforce reports and dashboards
Salesforce Reports and Dashboards are the final output required for any business.Key performance indicators (KPIs) for an organization may be represented graphically and tabularly in Salesforce reports and dashboards. Salesforce Dashboards show information about the company in real time. With a lot of data, reports and screens start to run slowly over time. Few Salesforce reports are sometimes so slow that it takes more than two hours to render them. We need to speed up these slow reports by making them better. This post will show you how to use Salesforce Reports and Dashboard in different ways.
- Use Index and Custom Index
- Use Proper Date Filter
- Take out fields from reports that aren’t needed
- Divide Reports
- Use Skinny Table
- Use Report on Schedule.
- Empty the recycle bin.
- Custom Report with a Selective Query
- Speed up Source Report
- Separate Dashboard Parts
Let’s look more closely at all of the above ways to improve.
1. Use the Index and Custom Index
When an object has a lot of data and we try to load a report made from that object, it might take a while to load. This could be because the report filter doesn’t have an index field. Filter criteria may include values from any index column (including but not limited to the primary key, audit fields, external id, record type id, lookup columns, etc.).
If we can use any of the fields listed above, our question will go faster. Even if we use the normal index, results should load faster. If they don’t, we should think about making a special index. We should ask Salesforce for a tailored search and explain why it’s good for business.
2. Use the Proper Date Filter
It can take a long time to load a lot of different kinds of info. In this case, we might want to think about getting less info. Let’s look at an example. It will take time to make reports on business data without any filters or data from many years. It would be better to make a study that looks at the last 1-2 years rather than the last 5β10 years.
Instead of CONTAINS, we should always use EQUALS. EQUALS take less time to do. CONTAINS runs a filter for each letter, which means that data has to be queried more than once.
We shouldn’t use a filter in the report that says DOES NOT CONTAIN. It checks the filter for each letter, which takes a lot of steps and slows the report down. NOT THE SAME AS carry out in fewer steps, which speeds up the report.
3. Take out fields from reports that aren’t needed
We make special report types and add many features to them so that they can be used in the future. The report will take longer to load because of these fields that you don’t need.
When information is grouped in the summary and stats report, these extra fields will also make it harder to run. It would be best to only include fields that are needed for the report or special report type.
4. Divide Reports
Instead of making reports with a lot of different kinds of data, it would be better to narrow down the results and make reports with fewer data sets. Instead of showing account reports that include all of the data, make several reports that focus on different areas, departments, or countries. This way, there will be fewer data, and results will load faster.
5. Use Skinny Table
If none of the above suggestions work, we can make the report with a skinny table. Skinny tables are tables that blend the fields of two related items into one table. These tables are used to make reports. We don’t have to join two or more items together when we use a skinny table. We just use one small table with only the values that are needed by objects. So, no join query is needed, and the query will load faster on the report.
6. Use Report on Schedule
We can use the planned report if we want a report on a wide range of data. When our organization isn’t doing a lot of routine work or side jobs, we can plan reports. So, users will get the report in their email address instead of having to log in to Salesforce Org.
7. Empty the Recycle Bin
When we remove records, we can still look at them for 15 days in the recycle bin. When we load the report, those reports that have been removed will also be searched, which could slow things down. So you should also take those records out of the recycle bin.
8. Custom Report with Selective Query
When the normal report isn’t enough for our needs, we make unique reports with the Visual Force page and lightning components. We should make our query more specific for the special reports so that it will load data faster.
9. Speed up the Source Report
The most effective method to speed up a screen that is slow is to speed up the information it is based on. If results run more quickly, the screen will run quickly. The method described above will help speed up results.
10. Separate Dashboard Part
If there are a lot of parts to a dashboard that takes a long time to update, we should split the dashboard in two. This will make panel parts load faster.
Salesforce Trailhead unit for Reports and Dashboards.
You might also be interested in
-
How to Utilize Salesforce Labs for Maximum Efficiency
-
The Essential Guide to Salesforce Solution Architect Responsibilities
-
salesforce interview questions and answers β Basic
-
Salesforce Developer Interview Questions and Answers
-
Restriction Rules in Salesforce with Example
-
The Best Trailhead Badges in 2023
-
What does Salesforce data skew mean?
-
Highlights of TrailblazerDX β23
-
How long will Salesforce be in the market?
-
Lightning Web Components Explained