Excellent presentation, clear and simple! Ready to use for anyone wondering how to handle security. Thanks
@thrillerteller
3 жыл бұрын
Can you please make a video on Row Level Security for comparison reports. For example when in line charts we are comparing one customer performance against all customers. That will be so helpful. Thanks
@SQLBI
3 жыл бұрын
We have this article: www.sqlbi.com/articles/implement-non-visual-totals-with-power-bi-security-roles/
@analistax
Жыл бұрын
As always, perfect explanation. i must say we have to have more videos unplugged hahahha. because you are amazing and you make it seem like you never look at the documentation and know everything. I feel more relieved haha.
@ArifulIslam-gs6uy
2 жыл бұрын
OLS is Really Very Interesting
@GL_Peppe
3 жыл бұрын
Excellent explanation, I was looking for this for a while, tante Grazie Marco
@brokensprog
3 жыл бұрын
The problem I have with the OLS implementation is that it doesn't support rules like RLS. I'm using an external system that has its own per-table permissions for all data in my reports that ties to Azure users, so I have a single Role in PowerBI for everyone and a lookup table for their permissions. Without something like that for OLS it's not usable to me which is unfortunate.
@BIGorilla
3 жыл бұрын
Seems a useful feature. I just wished that the visuals would still render if a field is inaccessible. For example, if HR data and finance data is combined, and one shouldn't see hr data, it would be great if the visual showed just the finance data instead of an error. Is this a stable feature yet?
@SQLBI
3 жыл бұрын
The feature in the engine is stable, it has been there for several years. The consumption experience in Power BI is bad, you should ask Microsoft to change it!
@rerangelt
3 жыл бұрын
Great video Marco. I see this usefull when you create and share datasets so the users create their own reports with only what can they see. I asume this work with dataflows
@SQLBI
3 жыл бұрын
Yes, it works regardless of the data source.
@StoianDstefan
2 жыл бұрын
just love this!
@abhijeetghosh27
3 жыл бұрын
Brilliant...Would be really very useful..thanks for sharing @Marco and @SQLBI😃👍
@roadtech6472
3 жыл бұрын
Great video as expected! Thanks for sharing knowledge.
@ezpowerbi5268
2 жыл бұрын
Thinking of use case when DAX can have feature like isExist to check if column is available in the model so our Calculated Column or Measure should not break. But as per my finding such feature is not available. May be you can comment if there is any workaround. ifError is not applicable as far as I know.
@SQLBI
2 жыл бұрын
The column is hidden from the data model when OLS is in place, so any function pointing to a non-existing column would have a wrong column reference. No workaround - and for security reasons!
@robertbarkovicz800
3 жыл бұрын
Thank you very much for your valuable content! So this means using OLS is a good reason to use perspectives as well?
@SQLBI
3 жыл бұрын
Objects hidden by OLS are already invisible in perspectives - not sure we get the point.
@robertbarkovicz800
3 жыл бұрын
Oh sorry, that was nonsense. I was thinking of hiding visualizations which is clearly not covered by perspecitves. Too late to post :-) The consequence of the behaviour seems to be that there have to be reports specialized for each role. That's kind of inefficient.
@SQLBI
3 жыл бұрын
Yes, but the real purpose of OLS is to limit the visibility to people who create a report in the first place.
@goldwhispers
2 жыл бұрын
I love the unplugged :) - dax enjoyed as usual!
@MatthiasK-qp9bf
3 жыл бұрын
Thank you Marco. I must say I find it much better solved as shown in Excel, where limited data is simply not shown. Broken Reports in PBI make users very unhappy. Is it to be expected in PBI any time? Or is it impossible due to PBI infrastructure?
@SQLBI
3 жыл бұрын
It's a choice they made in Power BI. Technically it would be possible to remove the measures, but depending on the visual, the final result might be different. However, it's an implementation detail in Microsoft hands.
@HariBI
3 жыл бұрын
It would be good if Power BI also shows same result as excel instead of error message. What do you think?
@SQLBI
3 жыл бұрын
We agree, but it's a different implementation and it depends on Microsoft. Unfortunately, we cannot change it.
@hulltl
2 жыл бұрын
Thanks , and know im watching this some time after creation, I have added an idea to the PBI ideas to allow the selection in Object level security of returning a blank (or zero) in addition to the read, default none options, as a way to combat the visual not displaying option.
@SQLBI
2 жыл бұрын
Good idea!
@BernatAgulloRosello
3 жыл бұрын
Good to know in advance! Thank you
@kalinduSekara
3 жыл бұрын
Thanks Marco
@akhilannan
3 жыл бұрын
Can we do some DAX tricks in measures to ensure the visuals don't break for OLS users? Maybe show as blank?
@SQLBI
3 жыл бұрын
No, the measure disappears and Power BI doesn't manage it well.
@arnohoedelmans
3 жыл бұрын
Would be great if the Power bi Team could make this work like excel!
@emirtuncer
3 жыл бұрын
The question what i looked for and the answer from Marco. Thanks all :)
@ezpowerbi5268
2 жыл бұрын
Also seems it is not applicable on Direct Query connections
@SQLBI
2 жыл бұрын
OLS can be applied to DirectQuery, check again!
@danningkong5794
3 жыл бұрын
Maybe I didn't get it right but it seems a broken visual trades off the benefit of hiding one column? And as always, MS does not make the error message meaningful enough so I wouldn't expect end users to understand what's going on. It should skip the column but still show the rest.
@SQLBI
3 жыл бұрын
We totally agree. However, you have to push Microsoft for this! Submit your suggestion to ideas.powerbi.com/
@joefuller6489
3 жыл бұрын
@@SQLBI Hi Marco, I can't find if the idea has already been submitted so I can add my vote. Could only find column level security. what can I search for to up vote, thanks
@pdadey
3 жыл бұрын
Would Power BI Perspectives be an viable alternative for handling these scenarios?
@SQLBI
3 жыл бұрын
Perspectives are not a security feature, they only limit the visible fields, but the user can always write a DAX expression that access "hidden" objects. With OLS the objects are not part of the model for the users that have no access, no matter the technique used to query the model.
@lbarbyery
3 жыл бұрын
would it be possible to obtain a similar result using perspectives? but what are the main differences between these features
@SQLBI
3 жыл бұрын
Perspectives is not a security feature. All the columns/measures/hidden by a perspective are just hidden in the metadata list, but you can access all of them in DAX.
@NicholasEnslow
3 жыл бұрын
Hey Marco! Great video as always. I know you say there isn't a system in Power BI where it simply removes the references to invalid Columns or Measures. Would you suggest a SWITCH() function that returns BLANK() if a user isn't in a Dynamic RLS (using a table in the model to suggest permissions) role that can view the data? I'm looking for a best of both worlds solution as a Sales Manager and a Sales Team Member might have different viewing capabilities - but I don't want to have to maintain two separate reports.
@SQLBI
3 жыл бұрын
The lack of objects in OLS generates invalid references, it's hard to workaround that. Not sure whether the SWITCH would help here - you can try, but the problem is how to avoid the DAX error, also IFERROR could have other side effects.
@riazuddin7493
3 жыл бұрын
I have created a report and in this report there are two visuals i.e. Exits by Grade and Exits and Turnover by Department. The former visual displays the grade wise number of leavers whereas the latter displays the data related to number of leavers and turnover percentage. If I select a articular grade in Exits by Grade then the visuals of Exits and Turnover by Department displays data correctly related to 1. Overall Turnover percentage of departments. 2. Highlighted Turnover percentage of the particular grade which was selected from the previous visuals for a particular department. 3. The total number of leavers of the department. But I also want to see 4. The total number of leavers in selected grade for the particular department. How can I achieve this?
@SQLBI
3 жыл бұрын
The question is unrelated to the video. Please, post the question in related articles on www.sqlbi.com using the model of the article, otherwise you can post generic questions in community forums community.powerbi.com/t5/Forums/ct-p/PBI_Comm_Forums or request direct assistance on your specific data model through remote consulting: www.sqlbi.com/p/remote-consulting/
@batava
3 жыл бұрын
How can I hide information from a column for only some rows? Say I want to hide the text information about products in Asia for everyone, but I want product information to be available for other regions. RLS does not work because it removed all info about Asia, OLS does not work because it hides all product information. My actual use case is to hide information about wages, but make available the account information for other accounts. Is it possible? An OLS RLS combo?
@SQLBI
3 жыл бұрын
You should split the text information about products into another table (ProductInfo) and then apply the row level security over that table only. By applying a 1:1 relationship between Product and ProductInfo, users not authorized will se BLANK for product info text column.
@batava
3 жыл бұрын
@@SQLBI Thanks!! :)
@shootinsasha
3 жыл бұрын
hi there, great video thanks! Does anyone know if it's possible to do the reverse? I.e. hide a table by default and only make it accessible through object level security? I have a user case where I want one group to only have permissions to two tables rather than the other way around....
@SQLBI
3 жыл бұрын
No, the logic in OLS is to list what is not visible. You may write a macro in C# with Tabular Editor to automatically make invisible all the objects.
@shootinsasha
3 жыл бұрын
@@SQLBI there might be a way around it. You create two roles, one who has access and one which doesn't. You assign a group to the role that does not have access. You then also assign those you wish to access the tables to the other role which has access. Initial tests work...
@SQLBI
3 жыл бұрын
Yes, but at this point there is no need of the first group, unless it provide access to other tables.
@Psrk4287
3 жыл бұрын
If we specifically add a read role to a table, will it automatically exclude access to everyone else not part of that role. Also, if we use object level security, will that be overridden if the user has admin, member, contributor access to the workspace (like rls behavior) ?
@SQLBI
3 жыл бұрын
Administrators always bypass security, both row-level and object-level security. Users who are not in a security role have no access at all, unless they are included as member in a Power BI workspace and you publish the dataset on Power BI service.
Пікірлер: 55