Alternative option for Dynamic Attributes with slicer (No bridge Table)

[perezco]

Good Morning/evening everyone,

Does exists an alternative option for Dynamic Attributes with slicer (a.k.a. Dimension) when the data is substantially to huge? Using the "bridge table" duplicate the query (consume twice of  resources to pull same data twice ) in my situation does not work for my requirements.

--Also I have to mention the main table doesn't have any Index key for any dimensions becuase this table come from a complex sql query. This query come with severals kpi, dimension of product, dimension of employee, etc..

Thanks for sharing your knowledge!!!

[cnweke]

How about bidirectional filters?

It mirrors SQL inner joins and I think it works for your use case.

If you select let's say Region A your fact table will get filtered and you'll only see attributes on other slicers that exist for Region A.

Like Filter Dim1-> FilterFact -> Filter Dim2

[perezco · Accepted solution]

after check the amount of record is not more than 200,000,

I end doing Bridge table, and also otpimize the sql query.

Thanks

[v-chuncz-msft]

@perezco ,

You may try Reference queries in the Query Editor.

https://community.powerbi.com/t5/Desktop/Help-me-get-rid-of-a-duplicate-table/td-p/602114