Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
FelipePalomino
Frequent Visitor

Edit query after it is referenced by another query

Hello PBI Community! 🙂

 

I have a query (QueryA) where I need to extract two columns (date and description), and I create a calendar based on this two columns.

I am doing this using "=QueryA", and then I remove the columns/rows I don't need.

This is working fine, but I want to do one extra step to improve the refresh performance.

 

"QueryA" is really big, and receives around 150k new rows each month.

In the description column, I have two categories that I use ONLY to create the calendar, and I want to remove all rows that have this information after I create "QueryB".

The point is, after I create "QueryB" (=QueryA), if I remove the rows I don't need from "QueryA", they won't appear on "QueryB", as ="QueryA" references the last step I created on "QueryA".

 

Is there any workaround?

Removing this rows would remove around 50k rows/month, so in the long term this would make a huge difference...

 

Thanks in advance! 🙂

1 ACCEPTED SOLUTION
Ehren
Microsoft Employee
Microsoft Employee

Have you tried creating a non-loaded common BaseQuery, which is referenced by QueryA (which removes the data that's only needed by QueryB) and QueryB (which creates the calendar table)?

View solution in original post

2 REPLIES 2
Ehren
Microsoft Employee
Microsoft Employee

Have you tried creating a non-loaded common BaseQuery, which is referenced by QueryA (which removes the data that's only needed by QueryB) and QueryB (which creates the calendar table)?

Helo Ehren!

I actually didn't think of it... 🤐

Thanks for your help!!

Helpful resources

Announcements
September Hackathon Carousel

Microsoft Fabric & AI Learning Hackathon

Learn from experts, get hands-on experience, and win awesome prizes.

Top Solution Authors