The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
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.
@Anonymous
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
@Anonymous
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 |
---|---|
82 | |
81 | |
35 | |
32 | |
32 |
User | Count |
---|---|
93 | |
79 | |
62 | |
54 | |
51 |