As a best practice, if you append in Power Query, should you turn off enable load on the original queries so that only the full table gets loaded? If you don't do this, when you load the tables, will it effectively update the data twice for each table?
Hi there great question! So queries no set to load will still be used by Power Query to process your steps, it just won’t be loaded to your final results, which does reduce the load time (since power bi has less tables to load) as best practice you should only load data that you’ll use for any calculations or visualisations
If you need to both Append and Merge, is it better/more efficient/effective (from a memory standpoint, etc.) to Merge and then Append, or Append and then Merge? Thanks.
Hey JJ, super amazing question! From your logic it sounds like a Merging and Appending would result in incorrect and fewer data (Appending after will not match any values in your second table). A more efficient way to handle this correctly is to append your data then create a relationship between your two tables
Append then Merge, if not you'll be doing a very similar merge multiple times....i.e. merge on country from region table to sales table for month 1 and then do it again for month 2 and then do it again for month 3, so 1 append and 3 merges. As opposed to Appending Month 1/2/3 and then doing the merge, so it'd be 1 append and 1 merge, also as mentioned a dynamic relationship is even better.
Thanks a lot, I didn't know how to make a SQL Select/Union in DAX and you demonstrate it with excellence.
This was perfect, exactly what I was looking for :-)
Great, glad it helped!
Awesome thank you so much 🍀🍀🍀
Thanks! Very good tip and very well explained.
Really helpful, thanks a lot.
VERY HELPFUL!
As a best practice, if you append in Power Query, should you turn off enable load on the original queries so that only the full table gets loaded? If you don't do this, when you load the tables, will it effectively update the data twice for each table?
Hi there great question! So queries no set to load will still be used by Power Query to process your steps, it just won’t be loaded to your final results, which does reduce the load time (since power bi has less tables to load) as best practice you should only load data that you’ll use for any calculations or visualisations
great video, tks so much :)
Every insightful.
Thanks for your support David!!
Thanks for your support David!!
Thanks for your support David!!
Can we update , insert two table in dax
Can we append a table and power bi dataset other report
whats the difference between merge, append, and union? thanks
Append & Merge is Power BI's version of Joins & Unions. Append = Union & Merge = Join.
If you need to both Append and Merge, is it better/more efficient/effective (from a memory standpoint, etc.) to Merge and then Append, or Append and then Merge?
Thanks.
Hey JJ, super amazing question! From your logic it sounds like a Merging and Appending would result in incorrect and fewer data (Appending after will not match any values in your second table). A more efficient way to handle this correctly is to append your data then create a relationship between your two tables
Append then Merge, if not you'll be doing a very similar merge multiple times....i.e. merge on country from region table to sales table for month 1 and then do it again for month 2 and then do it again for month 3, so 1 append and 3 merges. As opposed to Appending Month 1/2/3 and then doing the merge, so it'd be 1 append and 1 merge, also as mentioned a dynamic relationship is even better.