This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreGet Fabric Certified for FREE during AI Skills Fest. This week only. Secure your voucher now.
Hello,
We are currently migrating reports from SSRS to Fabric and encountered an issue in one report that we cannot figure out a solution for.
Issue:
Search is greyed out for users with non-admin workspace roles.
We have a pretty straighforward paginated report with expandable rows, several parameters, and a DirectSQL connection.
If we select every option available in every parameter, the report runs fine, but the search field is greyed out as you can see on the screenshot.
If I sign into the workspace as an admin, run the report with all parameter optiosn selected, and expand one of the rows, the search becomes available. However, anyone with Member, Contributor, or Viewer roles cannot reproduce this behavior.
If we only select a few options in our parameters and run the report, the search becomes available for any user, regardless of their workspace role.
We have about 200 reports and have only seen this behavior in one of them.
This feels like a bug/limitation based on the amount of data being returned, but I cannot find any documentation about this and the only other thread that mentions this issue has no resolution.
Has anyone encountered this odd behavior? We see this behavior in Chrome and Firefox.
Solved! Go to Solution.
Hi @eslna,
This looks like a limitation in Fabric paginated reports rather than a permissions issue.
The search box is only enabled when the rendered dataset is small enough for the client to index. In your case, when all parameter options are selected, the result set is large and the search control is disabled for non‑admin roles. Admins sometimes see different behavior because of caching or elevated privileges, but the underlying trigger is the volume of returned rows.
That’s why search works fine when fewer parameter values are chosen, and why it only affects this one report out of 200.
At present there’s no documented setting to override this — it’s tied to the rendering engine. If search is critical, you’ll need to reduce the dataset size (filtering, paging, or breaking the report into smaller slices). Otherwise, this is expected behavior until Microsoft updates the Fabric paginated report viewer.
If this helped, a kudos would mean a lot!
Thank you
Sunita
Thank you for confirming my suspicions!
Hi @eslna,
This looks like a limitation in Fabric paginated reports rather than a permissions issue.
The search box is only enabled when the rendered dataset is small enough for the client to index. In your case, when all parameter options are selected, the result set is large and the search control is disabled for non‑admin roles. Admins sometimes see different behavior because of caching or elevated privileges, but the underlying trigger is the volume of returned rows.
That’s why search works fine when fewer parameter values are chosen, and why it only affects this one report out of 200.
At present there’s no documented setting to override this — it’s tied to the rendering engine. If search is critical, you’ll need to reduce the dataset size (filtering, paging, or breaking the report into smaller slices). Otherwise, this is expected behavior until Microsoft updates the Fabric paginated report viewer.
If this helped, a kudos would mean a lot!
Thank you
Sunita
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
| User | Count |
|---|---|
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 |