Forum Discussion

otets's avatar
otets
Advocate I
3 years ago

RLS and CROSSFILTER Error. Table has two join paths to table

Hi, I try to use the CROSS FILTER function to avoid bi-directional relationships, and it works fine without RLS. But when I try to use the same measure with RLS then, I receive the following error:...
Need Help
sturlaws's avatar
sturlaws
Resident Rockstar
3 years ago

Hi, otets,

 

so something to do with how RLS is propagated from the "RLS"-table to the fact tables, I don't understand fully why it happens. 

But you have a couple of opportunities to rewrite it, like this:

 

Measure =
CALCULATE (
    SUM ( Revenue[Revenue] ),
    TREATAS (
        CALCULATETABLE ( VALUES ( Metric[ProjectID] ), Metric[TypeID] = 10 ),
        Org[ProjectID]
    )
)

 

 

Cheers,
Sturla

If this post helps, then please consider Accepting it as the solution. Kudos are nice too.

 

 

otets's avatar
otets
Advocate I
3 years ago

Hi, sturlaws 

Thanks for your comment.
It works fine with RLS but not without it. It is a bit confusing for me.

The result without RLS

The measure RevenueByMetricType_1 with TREATAS solution
The measure RevenueByMetricType I have written recently. Here is the code

RevenueByMetricType = 
    CALCULATE(
        SUM(Revenue[Revenue]),
        SUMMARIZE(
            CALCULATETABLE(Metric, KEEPFILTERS(Metric[TypeID] = 1)),
            Org[ProjectID]
        )
    )


When I view it with RLS, the result is


I still don't understand this mystery with RLS and CROSSFILTER.