March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
Hi,
Can someone explain what this error is about?
This is from any of the broken visuals on a published report in an App Workspace. The page with the broken visuals look like the following.
This is from a report which uses the Composite Model. Specifically, the report uses direct query tables in the row-level security filter expressions. While the business data are stored in imported tables, the user permissions are stored in on-premises SQL Server and accessed by direct query. This works beautifully on the desktop, and worked for a while as a published report in an App Workspace, until recently. Since last week our users have reported inconsistently errors like the above when viewing the report.
The errors are inconsistent i.e. different users with the same permissions could get different results. After refreshing the dataset, the problem occurs for a different set of users. This suggests the problem is not from the design or coding but possibly due to resource limitation (bandwidth, connections) which causes time-outs in the direct queries. How can we find out and how can it be fixed?
I have tried to increase the maximum connentions for direct query parameter to the maximum value of 1000, but it did not help.
Regards
wilx
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.