Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
My understanding is that when you join multiple tables with many to many relationships, it treats them as one large table. The issue I'm having is shown in attached screenshot. Please advise.
@akruzel Check out this video. The real relevant part for your question starts at about 9:45, but the whole thing may help in understanding models and the things you have to do.
Also, regarding the video, I would disagree with the presenter at 10:25 where he says there is no connection between the two dimension tables. How can he say there's no connection now, in then later in the video he talks about having these tables connected with bi-directional filtering we can treat the three as if they're one big table? For these three to be treated as one big table, there has to be a connection between the two dimension tables which is through the fact table.
I think the key issue is I'm treating a fact table as a dimension table and I'm trying to figure out how to implement this correctly. In the Manager WO Hdr Store query, I can have one manager assigned to multiple stores and I want to be able to filter the actual fact table on those stores depending on the manager that's logged in.
Thanks for the quick response Eno!
The key issue I'm running into is setting up a data model for row level security. The query that is filtered by the logged in user should allow for a user to be assigned one or two values to filter on.
For example, the 'Manager Hdr Stores' query is where I identify what stores to filter on by the user logged in. In the case with the new screenshot, when abc@123.com logs in, they should only see WO Hdr Store 0 and 3. I then want that filter to flow to the Store/JC query to show what Respare are assigned to the the same store of the user that just logged in.
User | Count |
---|---|
103 | |
87 | |
78 | |
71 | |
69 |
User | Count |
---|---|
113 | |
99 | |
97 | |
72 | |
68 |