paginated report

144 Topics

Fabric F64 Paginated Report Capacity: Workarounds Besides Increasing SKU?
Hi everyone, I am looking for guidance on managing high-concurrency usage of a Power BI paginated report in a Microsoft Fabric F64 capacity. The report serves a large K–12 environment with tens of thousands of students across 80+ schools. Users can select a teacher and one or more of that teacher’s courses to generate student-profile-style output. They can also run the report by school and grade level. Under normal use, the report performs acceptably. The issue occurs during short, predictable high-demand windows—such as conference periods—when many schools access and export the paginated report at roughly the same time. During those periods, the workspace/capacity can reach its maximum capacity, affecting workspace and report availability and performance. Before pursuing a larger SKU, I would appreciate guidance on possible alternatives or design patterns. In particular: Are there recommended ways to manage a high number of simultaneous paginated-report executions on an F64 capacity? Are there report-design or dataset/query optimizations that tend to make the largest difference for this type of parameter-driven, teacher/course-level report? Would using subscriptions, pre-generated exports, or another distribution approach help reduce interactive demand during peak windows? Is autoscale/burst capacity a practical option for short, predictable usage spikes? Are there capacity metrics or thresholds you would recommend monitoring to determine whether the bottleneck is report rendering, dataset/query execution, or overall capacity? Thank you for any recommendations or examples of similar deployments.
syasmin25
8 hours ago Place Report Server
Views
0likes
Comments
PERFORMANCE ISSUES IN PAGINTED REPORT BUILDER
We have a materialized view in Databricks with about 1.5 million rows and 80+ columns. On top of that, I’ve created a semantic model in Power BI, and a paginated report that shows essentially all 80+ columns (so it’s returning the full 1.5 million rows). The report also has around 24 filters/parameters. Because of this combination (large dataset + many columns + many filters), the paginated report is taking a long time to load. The main dataset is generated using the Query Designer, which produces a large: `EVALUATE SUMMARIZECOLUMNS(...)` So far, to improve performance I have: 1. **Created lookup tables for parameter datasets** Instead of retrieving dropdown values from the large flattened dataset, I created lookup tables and updated parameter datasets to use these tables. In the Databricks view we have 3 date columns: **D1, D2, D3**. In the Power BI semantic model I’ve joined these to `dim_date`. In the paginated report I want to expose 6 date parameters: **StartD1, EndD1, StartD2, EndD2, StartD3, EndD3**. I have three main questions: **Q1. How should I handle these 6 date parameters in the main dataset?** Each date column has its own start/end range; I’d like an approach that is reasonable to maintain. **Q2. Is the current approach (one big flattened table from the view) the right one?** We actually started with a star schema in the Power BI semantic model and then moved to a single flattened view, as suggested by a senior data engineer. The issue was that many of the 80+ columns required calculated columns and a lot of transformations, so we pushed all of that logic into the Databricks view instead. **Q3. How else can I improve performance?** Right now the paginated report is effectively selecting all rows and almost all columns, with 24 filters on top. I’m looking for design patterns or best practices (e.g. alternative modelling, pre‑aggregation, splitting datasets, etc.) that would make this scenario perform better. Any guidance or examples would be really appreciated.
Solved
swatig2904
1 month ago Place Report Server
Views
0likes
Comments
Paginated Report - Missing horizontal scroll bar
We have a paginated report that is missing a horizontal scroll bar. (Unable to scroll left to right) When we acknowledge the "General" information banner at the top of the screen the horizontal scroll bar appears. The image below highlighted by the red box indicates the information banner. I can only show the top part of the report due to security reasons. The paginated report was created by importing a stored procedure from MySQL. Any thoughts how to disable the information banner?
CactusJackAZ
3 months ago Place Report Server
Views
1like
Comment
Paginated Report
Hello everyone, I have a Paginated Report that works just fine on the Desktop App but if i publish the report to the powerbi Service and want to use it, i get the error message, "Unable to render paginated report A data source used by this report returned an error. Received error payload from gateway service with ID 57703: Async operation a1ee1d60-b03b-4159-b802-8d902e4eef69 is faulted with [0]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.AdomdDataAccessErrorResponseException: AdomdException encountered while accessing the target data source. GatewayPipelineErrorCode=DM_GWPipeline_Gateway_DataSourceAccessError GatewayVersion=3000.242.9 ErrorCode=-1056308850 ---> [1]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.GatewayPipelineWrapperException: Substituted: AdomdErrorResponseException:The specified query is too complex to be evaluated as a single statement. GatewayPipelineErrorCode=DM_GWPipeline_UnknownError GatewayVersion=3000.242.9 InnerType=AdomdErrorResponseException InnerMessage=The specified query is too complex to be evaluated as a single statement. InnerToString=Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: The specified query is too complex to be evaluated as a single statement. " I get the error message when i select my filters and then click on view report. If i want to get only one customer at the filter the reports works but when i want to see all customers at one i get the error. In the Desktop App "Power BI Report Builder" i dont get this issue at all. How can i resolve this error? Any suggestions?
LaurenzR
4 months ago Place Report Server
Views
0likes
Comments
paginated report - drilldown, drill down, drill-down functionality setup
Posting for future reference. Found the information hard to find and search hits intermixed with drill-through functionality. Hence the title of this post "drilldown, drill down, drill-down" to help folks with a direct search hit. In short found this youtube video the most usefull, drilldown report in paginated report builder The microsoft official pages referenced throughout the forums points to: Drilldown action in a paginated report (Power BI Report Builder) which points to Tables in paginated reports (Report Builder) which points to Add an expand or collapse action to a Report Builder paginated report Now the key help here is the term ToggleItem which is found only in the 3rd child link above. Also do not make the mistake like I did of looking at Textbox cells. We are wanting to work our way up the children of the multi level group hierarchy. Each child group references its parent group. Set Hidden (Visibility) to True to set the initial toggle state to unexpanded (+) Youtube drilldown report in paginated report builder by SKRTDATAMUSIC (thanks bro 🙂 Screenshots
garythomannCoGC
9 months ago Place Report Server
Views
1like
Comments
How to default to Select All in a Report Builder Parameter
I have created a Paginated Report Parameter that displays a list of Legal Entities and the user can choose one and refresh the report. I want it however to default to selecting ALL of them - but this does not seem possible? Also - seocndary question - If ALL are selected I'd like it to say the word 'All' (or similar) in the textbox on the users screen, instead of showing the first Legal Entity even when they are ALL selected
Solved
Anonymous
10 months ago Place Report Server
Views
0likes
Comments
Paginated Report Fails to Load from Remote Client with Error NET::ERR_CONNECTION_RESET; Works Locall
We are experiencing an issue where a specific paginated report (.rdl) fails to load in the Edge browser on a remote client machine. The browser's developer tools (F12) show the following error for a critical POST request: POST http://xxx/ReportServer/Pages/ReportViewer.aspx?%2fnvhtest&rc%3ashowbackbutton=true net::ERR_CONNECTION_RESET Key Details and Troubleshooting Steps Already Performed: Environment: •Report Server: Power BI Report Server (Version: May 2024) •Client Browser: Microsoft Edge . The issue is reproducible with IE mode enabled and the server URL added to the Trusted Sites zone. •Data Source: The paginated report uses a SQL Server data source configured with stored username and password (not Windows Integrated Security). Error Symptoms: •The report page shows "Loading..." indefinitely. •The NET::ERR_CONNECTION_RESET error occurs on a POST request to ReportViewer.aspx during initial load/rendering. •Crucially, the Power BI Report Server logs show no corresponding error events, suggesting the server believes it processed the request successfully or the failure occurred at the network/transport layer. Contrasting Behavior (Core to the Issue): •The same paginated report opens successfully when accessed from a web browser directly on the report server machine . •Power BI reports (.pbix) that use the exact same data source (with stored credentials) open successfully from the remote client's Edge browser. •This confirms that general connectivity from the client to the report server and basic data source connectivity are functional. The problem is isolated to this specific paginated report type when accessed remotely. Critical Additional Information: •Server Firewall and Security Software Disabled: We have completely disabled the Windows Firewall and any third-party antivirus/security software on the report server itself. The NET::ERR_CONNECTION_RESET error persists. This confirms the connection reset is not caused by a security policy on the server actively blocking the request. Request for Support: The evidence suggests the issue is related to how the paginated report processor handles the initial rendering request (the POST) for a remote client versus a local one, potentially involving authentication handoff or data transmission. Since Power BI reports work fine, the problem is specific to the SSRS engine component. We request assistance in investigating: •Why the POST request to ReportViewer.aspx is being terminated/reset specifically for remote clients. •The potential difference in authentication or data processing context between a locally and remotely initiated paginated report session. •Any required configuration for Kerberos Constrained Delegation (KCD), even when using stored credentials, if the report is configured to "Impersonate the authenticated user" after connecting with those credentials.
Solved
zhouli
1 year ago Place Report Server
Views
0likes
Comments
RSCustomDaxFilter column name with square brackets
There is a table column 'Prod'[Product[Product Division Label]] in the data model I want to filter that column from the parameter @ProductProductDivisionLabel using the below, but error out during query validation -> No parameter match for multivalue placeholder How to properly escape the column name with square brackets in RSCustomerDaxFilter? RSCustomDaxFilter(@ProductProductDivisionLabel,EqualToCondition,[Prod].[Product[Product Division Label]]],String)
Solved
Max_WH
1 year ago Place Report Server
Views
0likes
Comments
Report Builder ( paginated report ) remove time from date field
Hello, In report builder, I have a datetime field which currently shows as: dd/mm/yyyy hh:mm:ss How do I remove the time section and have the field only show the date - dd/mm/yyyy Thank you
Solved
Ry5
1 year ago Place Report Server
Views
0likes
Comments
“Some parameters do not have valid values” Error for power BI Paginated Report
I have a Paginated Report with a subscription which has parameters with list of customers, products where I can select certain customers and products and see the sales for it. I’ve selected a set of customers and products from their respective parameter drop down and got a table with the selected customers, product and their total sales, I’ve created a paginated report subscription for the same and it works fine. Then a customer that I had selected to display in my report subscription was marked as inactive in the source database and ceise to exist in the sematic model. When I ran my subscription or when the subscription ran automatically I got an error where it said “Some parameters do not have valid values”. One simple fix to this is to edit my Subscription and unselect the Customer that was removed from my semantic model. If I do this the subscription works fine shows the remaining checked customers in the attachment. But is there a way for power bi to be less strict, where if customers no longer exists in the semantic model, then my Subscription shouldnt stop/break and automatically send the data of the existing customers that are checked and present in my semantic model.
Solved
Vallance
1 year ago Place Report Server
Views
0likes
Comments