Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
I'm used to working in Access where I can do inner joins everywhere, but DAX relationships don't do this. So often my slicers have a ton of useless data - Customers in the DIM tables for example that we haven't sold to in years.
Looking for the best way to limit the data in my DIM tables to the data that is in my FACT tables. Our sales report, for example, only uses sales data from the last 4 years for comparisons.
#2 is easier, but I am generally loathe to add caclulated columns.
Any ideas from others on how you do it?
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingHi @edhans
You may try to select ODBC import option, choose the DSN you created and then you may put your sql query into SQL Statement.
Regards,
Cherie
Try turning on bidirectional relationships. It comes at a cost (overhead) but maybe it is ok for you.
Yeah... that is definitely a third option. I'm not comfortable with how DAX handles bi-directional. It makes some relationships go inactive, and there is some overhead. It is almost to the point for me I'd rather use a CROSSFILTER() inside a CALCULATE() if I need bi-directional, but of course I cannot put that in a filter, or I would.
Thanks though. I'll need to look at my model, but given I want to do this on the customer and product table, I'll probably it some snags in other relationships.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingUser | Count |
---|---|
140 | |
113 | |
104 | |
77 | |
65 |
User | Count |
---|---|
136 | |
118 | |
101 | |
71 | |
61 |