[ad_1]
Most knowledge fashions have RLS in place, the place some customers can see just some facets of your entire knowledge set. However what occurs after they should see their outcome in comparison with the general outcome? This isn’t that simple.
11 hours in the past
Let’s take a look at the next situation:
My Salespeople can see solely the outcomes for his or her assigned geographic areas.
On this situation, it’s the continent.
For benchmarking, they have to be capable to evaluate their outcomes to the outcomes of the opposite continents and the overall.
That is inconceivable when RLS (Row-Degree-Safety) is in place, because the customers should not allowed to see the outcomes for the opposite continents.
A change to the info mannequin is critical to make this attainable.
So, let’s take a look at easy methods to implement such a change.
SQLBI has already written an article and created a video on this matter:
Theoretically, we are able to cease right here: Learn the article or watch the video. All OK, isn’t it?
Not that quick, my younger horse.
Whereas Alberto has constructed an answer utilizing DAX, I want to create the extra tables for the info mannequin earlier, ideally within the supply (database) or Energy Question.
As not everybody shops their knowledge in a database, I don’t wish to dig into SQL code to construct the required tables, despite the fact that creating the answer in SQL can be fairly easy.
So, I’m going to Energy Question to create the answer.
Identical to my earlier article:
[ad_2]