The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
Hi,
I have a power query setup wherein the SQL query is contained in one query, and the transformations are done in a couple of child queries which talk back to it. I have then put in Table.Buffer custom functions in at the end of the Parent query, and also at the start of the child query - despite this, every time I change the M code, it is referringback to the SQL db and takes a long time.
How do i stop it from doing this? I'd rather the SQL query needed a manual push to refresh, and the child queries would only refer to the parent as a static table.
Below, you can see there's the Custom1 function [ Table.Buffer(Source) ] but the PostgreSQL is running in the progress bar anyway.
Any help would be greatly appreciated!
Solved! Go to Solution.
In your development phase apply a filter that severely limits the amount of data to just what you need to develop. Then in production remove that filter. You can do that with parameters, similar to how Incremental Refresh is designed.
Okay that's not what I expected, thanks for oyur reply. Is there a way for me to set this up the way I described - so that the SQL query doesn't get involved every single time?
In your development phase apply a filter that severely limits the amount of data to just what you need to develop. Then in production remove that filter. You can do that with parameters, similar to how Incremental Refresh is designed.
Table.Buffer will not prevent a reload of data from source. It does prevent chunking/streaming, so it does the opposite of what you want because now Power Query no longer can fetch previews.