This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
Hi,
I have a fact table:
AccountType
| 1 | A |
| 2 | B |
| 3 | B |
| 4 | C |
| 2 | C |
| 1 | C |
| 1 | A |
| 3 | A |
| 1 | D |
| 4 | C |
With an Account dimension:
AccountName
| 1 | W |
| 2 | X |
| 3 | Y |
| 4 | Z |
So there is 4 Accounts (W, X, Y and Z) and the fact table has 4 Types (A, B, C and D).
I want to create a table showing the Account names that filters with a slicer for Type. The problem is that I don't want Type to be one of the columns displayed in the table. But if I don't include it in the table, the slicer won't apply and the table will just show a list of all accounts.
Does anyone know a way around this?
Solved! Go to Solution.
It sounds like you want bi-directional filtering on the relationship between the tables (I'm assuming you have a one-to-many relationship from Dimension[Account] 1 -->-- * Fact[Account] ).
Bi-directional relationships can cause relationship ambiguities though so it may be better to do the cross-filtering within whatever measures you are using.
It sounds like you want bi-directional filtering on the relationship between the tables (I'm assuming you have a one-to-many relationship from Dimension[Account] 1 -->-- * Fact[Account] ).
Bi-directional relationships can cause relationship ambiguities though so it may be better to do the cross-filtering within whatever measures you are using.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 33 | |
| 25 | |
| 23 | |
| 20 | |
| 15 |
| User | Count |
|---|---|
| 64 | |
| 41 | |
| 27 | |
| 22 | |
| 22 |