Forum Discussion
RLS and USERELATIONSHIP problem
Hi ju97,
Thank you for bringing this issue to our attention. We understand that the error related to the UseRelationship() and CrossFilter() functions has recently impacted your report, despite it functioning well previously.
As this is a known issue that is currently being addressed, we are unable to keep this thread open indefinitely.For official updates, you can check for more information through the provided link : Known issue - Reports that use functions with RLS don't work - Microsoft Fabric | Microsoft Learn
In the meantime, if you continue to experience difficulties, we kindly encourage you to create a new thread. This will allow us to assist you more effectively.
Thank you for your understanding, and please know that we are here to help!
Best regards,
Atheeq.
We experience the same issue as many of you do. We have started redesigning the measures. I use an alternative solution. I see some of you are stuck on how to continue, maybe you can use this example on how to accomplish the same result without using (inactive) relationships.
I use this solution with [selectcolumns in a var, and then filter where value IN var] quite a lot and it performs well and gives you the flexiblity to also get data from tables that aren't even related via relations. I hope this helps those of you who are stuck on how to fix it.
//OLD WAY
//CALCULATE(COUNTROWS(dim_FinancialProject), USERELATIONSHIP(dim_Company[Company_NK], dim_FinancialProject[Company_NK]))
//New Way
VAR SelectedCompanies = SELECTCOLUMNS(dim_Company, "CompNK", [Company_NK])
RETURN
IF(
COUNTROWS(SelectedCompanies)=0
, 1
, IF(
CALCULATE(
COUNTROWS(dim_FinancialProject)
, dim_FinancialProject[Company_NK] IN SelectedCompanies
) > 0
, 1
, 0
)
)
Thank you for sharing this bypass. Unfortunately it does not work for us. I think because our situation is not the same. I will try to explain. In short: There is one group of people who can see everything and a second group who can see everything EXCEPT one table which they cannot access.
The optional relationship between that special table and the fact table is essential because otherwise the second group will not see anything at all because Power BI always actives all relationships. Even if you do not select an item (column) from a table.
There was a solution for this but unfortunately since a couple of days it is broke.
Hi AlexNL ,
Please consider reaching out to Microsoft Support. You can provide them with all the troubleshooting steps you've already taken, which will help them understand the issue better and provide a resolution. They might be able to identify something specific about your admin account setup or provide a solution that isn't immediately obvious.
Below is the link to create Microsoft Support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft LearnIf this helps, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details.
Thank you.