Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
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
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
61 | |
61 | |
55 | |
38 | |
27 |
User | Count |
---|---|
85 | |
60 | |
45 | |
41 | |
39 |