Forum Discussion
Object level security - Paginated Report (missing column)
Hi Abhinav,
thanks for the info and all the help, now report is working for me as I am in the Role without OLS restrictions but users under different roles are getting same error:
"There was an error communicating with Analysis Services. Please verify that the data source is available and your credentials are correct. Query (14, 84) The value for 'Val Stock Net Movement Amt' cannot be determined. Either the column doesn't exist, or there is no current row for this column.".
Hi PetrarteP ,
In Power BI, we can only limit data access on row level.
Support for OLS in Power BI is in Preview.
Visualizations referencing a dataset object with OLS configured display the same message as for a deleted or non-existing object.
Because users under OLS roles do not have access to the column in datasource, you cannot use DAX functions such as IFERROR to try to catch errors.
As a workaround, you could use import mode, and you could unpivot your source table to convert column headers into rows. Then you can control users' access to specific columns via applying RLS indirectly. And you can put the converted column into Column group within Matrix visual to make it appear like a "column".
Reference: Unpivoting Sensitive Columns in Power BI to Apply Row-Level Security
Best Regards,
Winniz
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.