Object Level Security using SSAS in PBI Service

[anandraman]

Hi All,

I have a model created in SSDT and deployed to SSAS. In this Model i have 2 Roles:

1. SUper User--> No restriction on any column. Have access to column A, B, C, D, E

2. Restricted User --> Dont have access on few column. A, B

I have a report created  with all the columns A B C D E. and published to Service. When  a restricted user logs in ans tries to access the report he gets some column error. but when super user logs in he can see the report without any issue.

Is there anything else to be done at PBI level where if user does not have access to some columns report should compe up without those restricted columns?

Any suggestion?

[Anonymous · Accepted solution]

Hi @anandraman,

Based on researching, object level security is used to manage access permission of specific columns.  For specific users, they not have permission to access columns, so these security columns are 'not exist' for themselves.

AFAK, current power bi not support dynamic table structures, each structure need to corresponded with original one who generated by power query operation and cache in query table steps.

>>When  a restricted user logs in ans tries to access the report he gets some column error. but when super user logs in he can see the report without any issue.

In summary, when power bi try to load new table structure which can't correspond with previous structure, it will return error message.

In my opinion, I'd like to suggest you submit an ideas to add support for dynamic table structure.

Regards,

Xiaoxin Sheng