web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Suggested Answer

Dashboard Error: The maximum record limit is exceeded. Reduce the number of records.

(0) ShareShare
ReportReport
Posted on by 135

Hello Team,

I'm getting an error message in the dashboard- The maximum record limit is exceeded. Reduce the number of records.

How do i increase the limit in online instance.

2308.Capture.PNG

Regards,

Hima 

I have the same question (0)
  • Suggested answer
    ba365guy Profile Picture
    2,950 on at

    The maximum record limit is 50,000 by definition.

    If you are using on-premise CRM, you can increase the limit from DB / Via custom console app

    If you are using online, please contact Microsoft.

  • LuHao Profile Picture
    40,892 on at

    Hi HimaM,

    For charts and grids displayed in dashboards, your apps allow users to run queries that have a dataset that has fewer than 50,000 rows. Should a user run a dashboard query that spans a dataset of 50,000 or more rows, the message "The maximum record limit is exceeded. Reduce the number of records" is returned. The dataset practical setting helps to ensure optimal performance of the app.

    To make sure that your users do not exceed these settings and to improve report querying performance in general, consider the following best practices.

    • When you create custom reports or dashboards, design them to query smaller datasets over shorter periods of time by adding a time-based filter in the report, such as the current month or quarter, to limit the results.

    • We recommend that you limit the number of entities that are needed to return the result. This helps reduce the time required to run the query and return the result set.

    • We recommend that you reduce the number of records shown in detailed reports. Suitable filtering can be used to reduce the number of records returned by the query to reduce timeouts.

    • For aggregated or summarized reports, queries must be used to push the aggregation to the database and not fetch detailed records and perform aggregation in the SQL Server Reporting Services report.

    • When appropriate for your business, users should run the default (out-of-the-box) reports and dashboards. These reports and dashboards are typically designed to query per user datasets, so in most cases will not exceed the dataset limit.

      If users must run reports that exceed these settings, we recommend that you review the following options for assistance with complex reporting needs. Both options effectively offload reporting workloads from Common Data Service to another datastore by using a data integration solution.

    • Adapters are used in conjunction with SQL Server Integration Services (SSIS) to extend the capabilities for integration with your apps data.

    • Extract transform load (ETL) tools provide a new tool set for creating analysis of data by combining multiple data sources or extracting data to the data warehouse solution if SSIS is not in use. ETL tools provide comprehensive solutions for connecting with common data service to move data.

    For details, please refer to: https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/reporting-considerations

    If reducing the number of records shown in the dashboard is not suitable for your needs, please submit a support ticket and the Microsoft team will help you resolve this issue.

  • Suggested answer
    ashish12 Profile Picture
    3,079 on at

    I would Suggest to use some of the best practices and reduce your chart data set. Here are the list of few:

    When you create custom reports or dashboards, design them to query smaller datasets over shorter periods of time by adding a time-based filter in the report.

    We recommend that you limit the number of entities that are needed to return the result. This helps reduce the time required to run the query and return the result set.

    We recommend that you reduce the number of records shown in detailed reports. Suitable filtering can be used to reduce the number of records returned by the query to reduce timeouts.

    For aggregated or summarized reports, queries must be used to push the aggregation to the database and not fetch detailed records and perform aggregation in the SQL Server Reporting Services report.

    When appropriate for your business, users should run the default (out-of-the-box) reports and dashboards. These reports and dashboards are typically designed to query per user datasets, so in most cases will not exceed the dataset limit.

    Thanks

  • Suggested answer
    PS Profile Picture
    23,577 on at

    Hi Hima

    Solution explained here: diyd365.com/.../

    Download here: github.com/.../OrgDbOrgSettings

    *Consider the performance impacts as explained by @Lu Hao before installing the solution

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
ManoVerse Profile Picture

ManoVerse 180 Super User 2026 Season 1

#1
ManoVerse Profile Picture

ManoVerse 180 Super User 2026 Season 1

#3
CU11031447-0 Profile Picture

CU11031447-0 100

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans