Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Sam Duval]

Is anyone else having/had a problem where their paginated reports in a premium workspace are not loading? If I try and pull up a paginated report, in both chrome and edge, a message shows up that says report loading and a spinning wheel, but it never loads the report. I’ve tried creating a couple very simple paginated reports that load in a second or less from SQL and within the report builder, but can’t load in service.

any tools I can look at behind the scenes to see if there is something stuck on my end that needs cleared/stopped?

Thanks!

——————————
Sam Duval
Data Quality Analyst
Indianapolis
——————————

[Alex Carroll]

Hello,

I have had similar issues with paginated reports. The report works fast when ran in SQL server management studio (SSMS) but takes a long time or never renders when its published. There are a few items I have noticed that can cause problems.

Are you using a view or stored procedure or are you embedding the SQL? While each run well when testing they can run different when published.

Are you running a report that has a lot of columns / data returned or perhaps a lot of data processed while running? Had a few stored procedures that I had to re-write and break down some of the steps to reduce the amount of data being processed while running. I’ve also had to limit the number of columns being returned since the overall volume of data was large. Having a lot of rows and columns being returned combined with heavy processing to aggregate the data can cause issues. I tested this out by re-writing the query and only returned a few columns in the dataset.

You may need to review the code for efficiency. Do you see a lot of table scans? Are using Select * or you using only the columns you need?

Perhaps it’s a latency issue combined with processing / memory usage.

I’ve seen reports run slow during “peak” usage time in the office but run quick in the late afternoon or early mornings. That you can test by running the reports at different times during the day. Can certainly be the case if you are running reports on an internal / on-premises report service.

Is the data source connection for the report setup correctly? I had one occasion where the data source did not have permission to access all the database / tables. I believe that problem threw an error message but still your data source connection on the report server may be different than the one you used in the builder.

——————————
Alex Carroll
Business Intelligence Analyst
——————————
——————————————-

[Sam Duval]

Thanks for the reply turns out it was a systems issue that Microsoft had to resolve on their end. I am familiar with different performance issues running directly on SQL server compared to running in the cloud, and most my reports run off heavily refined SPs to squeeze as much efficiency as I can out of the query. In this case the report had parameters, so it? was failing to even render the report to where I could enter a parameter value.

——————————
Sam Duval
Data Quality Analyst
Elements Financial
Indianapolis
——————————
——————————————-

[Alex Carroll]

Glad it worked out.

——————————
Alex Carroll
Business Intelligence Analyst
——————————
——————————————-