Forum Discussion
Power Query slows down after merging two queries
Hi 09 ,
Difficult to say without understanding the actual data and source.
Whilst there are a number of ways to speed up merges when the data and source are understood, my first recommendation will always be: don't do the merge at all. Merging is very expensive in Power Query (obviously excluding when folded to source), so I would do the following:
1) In both Table1 (#"HISTORIQUE MB52") and Table2 (#"UPS STOCK") create a merged column, called something like 'CLE_Date'. In Table1 this will be [CLE] and [Date] merged together, in Table2 it will be [material_Sloc] and [Date]. In both I would also add a delimiter, such as '-', between them to help avoid false positives.
2) Remove any columns from Table2 that you don't need, keeping at least your new [CLE_Date] column.
3) Send both tables to the data model and relate Table1[CLE_Date] to Table2[CLE_Date].
Pete
Hi 09 ,
Difficult to say without understanding the actual data and source.
Whilst there are a number of ways to speed up merges when the data and source are understood, my first recommendation will always be: don't do the merge at all. Merging is very expensive in Power Query (obviously excluding when folded to source), so I would do the following:
1) In both Table1 (#"HISTORIQUE MB52") and Table2 (#"UPS STOCK") create a merged column, called something like 'CLE_Date'. In Table1 this will be [CLE] and [Date] merged together, in Table2 it will be [material_Sloc] and [Date]. In both I would also add a delimiter, such as '-', between them to help avoid false positives.
2) Remove any columns from Table2 that you don't need, keeping at least your new [CLE_Date] column.
3) Send both tables to the data model and relate Table1[CLE_Date] to Table2[CLE_Date].
Pete