Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
Sometimes, for some use cases, you want the same table to be available more than once in the model instead of using (in)active relations with USERELATIONSHIP. Eg. a Order Date and Shipping Date table.
You can do that by referencing a table (using PQ) or by creating calculated tables in DAX.
I wonder what is the most efficient approach regarding speed, size (memory) and refresh times?
Solved! Go to Solution.
@__Marc__
Referencing the table in PQ is the best option. This way, when you load the queries to the model, you get a highly optimized model with good compression compared to creating Tables in the Model using dax
⭕ Subscribe and learn Power BI from these videos
⚪ Website ⚪ LinkedIn ⚪ PBI User Group
@__Marc__
Referencing the table in PQ is the best option. This way, when you load the queries to the model, you get a highly optimized model with good compression compared to creating Tables in the Model using dax
⭕ Subscribe and learn Power BI from these videos
⚪ Website ⚪ LinkedIn ⚪ PBI User Group
User | Count |
---|---|
140 | |
113 | |
104 | |
77 | |
65 |
User | Count |
---|---|
136 | |
118 | |
101 | |
71 | |
61 |