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
Data Pipelines - Run only selected activities
For debugging and testing pipeline activities during development, allow us to select one or multiple activities and run only the selected pipeline activities. For example, I'm working on editing ...frithjof_v6 hours agoCommunity ChampionNew612Views11likes2CommentsSemantic model connection bindings should be in source control (Git)
Semantic model data source connection bindings should be source controlled. A semantic model can contain multiple data source references, each of which can be mapped to a separate Fabric data connec...frithjof_v13 hours agoCommunity ChampionNew17Views1like0CommentsBulk changing column names in Visualizations Pane
We often use raw/api column names or measures with a set nomenclature to be consistent and to keep track of them but we do not want to display these names in the visuals. Currently we have to change ...vishal14019717 hours agoFrequent VisitorNew6Views0likes0Comments