title | description | ms.custom | ms.date | ms.reviewer | ms.suite | ms.tgt_pltfrm | ms.topic | applies_to | ms.assetid | caps.latest.revision | author | ms.author | tags | search.audienceType | |||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Improve report performance in Dynamics 365 Customer Engagement (on-premises) |
This page offers guidelines that can help you improve the performance of your reports in Dynamics 365 Customer Engagement (on-premises). |
06/28/2021 |
article |
|
dece910e-0712-4801-824f-d2aa1bed88d2 |
9 |
Mattp123 |
matp |
|
|
Here are some guidelines that can help you improve the performance of the report.
These guidelines are applicable for both Fetch-based reports.
-
Limit a report to display information from a specified time period, instead of displaying all records in the apps database.
-
Pre-filter a report so that the dataset is limited.
-
Calculate aggregate totals by using aggregations in a FetchXML query, instead of passing raw data to Reporting Services and grouping.
-
Limit the number of datasets used, if possible.
-
When you compare dates, use the UTC date fields for comparisons. For example, compare the
createdonutc
fields and not thecreatedon
fields in the FetchXML query or a filtered view.
Reporting and Analytics Guide
Improve report performance by using filters
[!INCLUDEfooter-include]