This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
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
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.