Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin 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.
Hello,
I'm trying to expedite my refresh time for a large report with lots of tables. There are 3 or 4 which are causing most of the issues which I'm trying to tackle.
In Power Query I want to copy a table (T1), and carry out subsequent applied steps to produce another table (T2), however I just want to copy T1, I do not want T2 to refresh from the source in SQL on my scheduled refreshes, as this file takes a long time to refresh.
I can find documentation online which explains Copy/Paste, Duplicate and reference but all of these then go to the source in SQL when I run a data refresh, is there any way to avoid this so T1 refreshes and T2 just takes the latest data from T1.
It's worth mentioning producing the new table in SQL is much slower than what can be achieved in power query, and I also know I can create a DAX table, however I am unpivoting 150+ columns which is not really practical.
If anyone has any experience with the above scenario I would be extremely grateful.
Thanks
Use the Reference option in Power Query.
Unless you made it a table of records, but you can't use Dax on that.
--Nate
No, you cannot dynamically stopped that source table from refreshing.
--Nate
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
15 | |
12 | |
8 | |
8 | |
7 |
User | Count |
---|---|
15 | |
13 | |
9 | |
7 | |
6 |