Does this increase overall refresh speed or the stability? I have a great project to test this on in a dataflow, very curious to see if it speeds up anything.
Referencing another table does not prevent the "raw" table from being refreshed. Each table has an option in power query to enable refresh enable load. I uncheck the "enable load" option so the raw table isn't available for the report designer, but it will still refresh the data. I hope that makes sense and answers your question :)
@@quietstrm07 thank you for the reply. So how does referencing the “raw” table make the refresh faster? If you’re referencing a table that doesn’t have refresh enabled then the data would be static and you’d just be referencing static data. But if you’re referencing a “raw” table has refresh enabled, then wouldn’t that mean that both tables will now need to be refreshed and causing 2x more time to refresh. Please help me understand because I’m getting errors in my dataset that I think this would help but I’m just not fully understanding the benefits of doing it this way. Thank you!
@@Htxcustom Ive heard theres no performance improvement for referenced tables. But id like to see more evidence. If a table load is disabled, it still needs to be loaded into cache memory. Referencing just removes the need for duplicating the same logic/steps
Any explanation on why the failures before and if this prevented the failures in this new case?
Does this increase overall refresh speed or the stability? I have a great project to test this on in a dataflow, very curious to see if it speeds up anything.
That's like one of the first things he said in the video that it does.
Thanks for sharing ❤
How would this work with multiple data tables within one Folder, or 'Get data -> From Folder?
Just To confirm this method is only good if your data is static and does it need to be refreshed correct?
Referencing another table does not prevent the "raw" table from being refreshed. Each table has an option in power query to enable refresh enable load. I uncheck the "enable load" option so the raw table isn't available for the report designer, but it will still refresh the data.
I hope that makes sense and answers your question :)
@@quietstrm07 thank you for the reply. So how does referencing the “raw” table make the refresh faster? If you’re referencing a table that doesn’t have refresh enabled then the data would be static and you’d just be referencing static data. But if you’re referencing a “raw” table has refresh enabled, then wouldn’t that mean that both tables will now need to be refreshed and causing 2x more time to refresh. Please help me understand because I’m getting errors in my dataset that I think this would help but I’m just not fully understanding the benefits of doing it this way. Thank you!
@@Htxcustom Ive heard theres no performance improvement for referenced tables. But id like to see more evidence. If a table load is disabled, it still needs to be loaded into cache memory. Referencing just removes the need for duplicating the same logic/steps
Not clear why it should improve the update... and why do you reference two tables to each other
It is really work??
This guy explains something not correctly and BOOM is disapear ! Static tables or not !