Your plan is require different queries for the same data set! this is what you are saying if you are granting select on columns. I can no longer have one query/report where one user runds the query and can see the column level data, and the other user runs the exact same query but the column returns nulls. By making the query fail for users without select rights makes this option unusable, way too much governance/cost. You force the creation and management of views which has less overhead than managing two queries ie two reports for the same purpose. Just make the engine return nulls for columns people don't have access to, don't fail the query, or come up with another approach becuase this one is no bueno. Thanks!
No CommentsBe the first to comment
Recent ideas
Exported PDF from PowerBI to not have any indents/borders
Currently, using the "Export to PDF" option in PowerBI results in two consistently buggy results: A white border/indent is generated, increasing the size of the page from 8.5x11 to 9x11.5 Sometime...EliShalev42 minutes agoNew MemberNew1View0likes0CommentsAdding a Container for Logical Grouping of Activities in Data Pipelines
Dear Team, I would like to propose a feature enhancement for Data Pipelines in Microsoft Fabric that allows the logical grouping of activities into a container. This container would serve to: Im...lukas_karlovsky1 hour agoNew MemberPlanned868Views15likes5CommentsSupport Native SQL LIKE / NOT LIKE Wildcard Filtering Across Power BI Reports
Description Currently, Power BI does not provide a native way for report consumers to perform dynamic SQL-style wildcard filtering using patterns such as LIKE '____' - Above return all values wit...Seeralan3 hours agoNew MemberNew4Views0likes0Comments