This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
I have a complex report that does a lot of different transformations on several datasets before appending them all into one table. Issue I am running into is when something changes in one of the base dataset and we refresh the report it take a long time because it is refreshing all the other base queries too. Is there a way around that?
Ex
Query1 - (Enable Load unchecked)
Query2 - (Enable Load unchecked)
Query3 - has data and then appends Query1&2 to create a master table
If something changes in the data for Query1 is there a way to refresh just Query1 and have it reflected in the final table (query 3) without it refreshing Query2?
Solved! Go to Solution.
Hi @justingraff88
Thank you for reaching out to the Microsoft Community Forum.
In Power BI, when a query is refreshed, Power Query evaluates all dependencies. This means that if Query3 depends on Query1 and Query2, both queries will be refreshed before updating Query3, leading to longer refresh times due to query dependencies, as mentioned by @lbendlin .
To optimize performance, consider using staged queries to store intermediate results instead of directly appending Query1 and Query2 into Query3. Power BI does not automatically refresh referenced queries unless explicitly required.
Keep Query1 and Query2 with "Enable Load" unchecked, create Query1_Staging and Query2_Staging as references with "Enable Load" enabled, and append them into Query3.
If my response has resolved your query, please mark it as the Accepted Solution to assist others. Additionally, a 'Kudos' would be appreciated if you found my response helpful.
Thank You.
Hi @justingraff88
Thank you for reaching out to the Microsoft Community Forum.
In Power BI, when a query is refreshed, Power Query evaluates all dependencies. This means that if Query3 depends on Query1 and Query2, both queries will be refreshed before updating Query3, leading to longer refresh times due to query dependencies, as mentioned by @lbendlin .
To optimize performance, consider using staged queries to store intermediate results instead of directly appending Query1 and Query2 into Query3. Power BI does not automatically refresh referenced queries unless explicitly required.
Keep Query1 and Query2 with "Enable Load" unchecked, create Query1_Staging and Query2_Staging as references with "Enable Load" enabled, and append them into Query3.
If my response has resolved your query, please mark it as the Accepted Solution to assist others. Additionally, a 'Kudos' would be appreciated if you found my response helpful.
Thank You.
No, you don't have that level of control. If you refresh query3 it will need to refresh both query1 and query2.
That's one of the main reasons for trying to avoid query dependencies.
Check out the April 2026 Power BI update to learn about new features.
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.
| User | Count |
|---|---|
| 37 | |
| 29 | |
| 29 | |
| 21 | |
| 18 |
| User | Count |
|---|---|
| 69 | |
| 39 | |
| 33 | |
| 24 | |
| 23 |