Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Hi All,
I'm new to the Forum so sorry if this is posted in a wrong place.
I tried to find a solution on Google, but unfortunately, it seems that no one has stumbled upon a similar issue.
I started using Power Query only recently, so I'm still learning. Anyway, I am trying to build an automated reporting for vendor expense map for my company. I have 4 data source files which are transformed and merged into one query with mappings applied.
Problem starts when I try to Merge my Left Table with a mapping table which contains duplicates. In order to avoid duplicated lines (which is not expected for a final result) I use Table.First function and then the issue starts. Up until the function, everything works smoothly. When I apply the function a whole query slows down and takes ages to calculate. Any ideas on how to fix this would be much appreciated.
Solved! Go to Solution.
Thank you very much! I did exactly this last night trying to figure out the way. This helped and now the query works way smoother, I also included Table.Buffer for all source tables and switched off the backroundupdates for queries. Now extracting 180k records takes approx 3-5mins.
Remove the duplicates from your (right) lookup-table before merging it: Faster merge and no need to select first values afterwards.
(Create an intermediate table if you need the lookup-table in its original state in the data model)
Imke Feldmann (The BIccountant)
If you liked my solution, please give it a thumbs up. And if I did answer your question, please mark this post as a solution. Thanks!
How to integrate M-code into your solution -- How to get your questions answered quickly -- How to provide sample data -- Check out more PBI- learning resources here -- Performance Tipps for M-queries
Thank you very much! I did exactly this last night trying to figure out the way. This helped and now the query works way smoother, I also included Table.Buffer for all source tables and switched off the backroundupdates for queries. Now extracting 180k records takes approx 3-5mins.
Good to hear!
Imke Feldmann (The BIccountant)
If you liked my solution, please give it a thumbs up. And if I did answer your question, please mark this post as a solution. Thanks!
How to integrate M-code into your solution -- How to get your questions answered quickly -- How to provide sample data -- Check out more PBI- learning resources here -- Performance Tipps for M-queries
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.
| User | Count |
|---|---|
| 48 | |
| 46 | |
| 41 | |
| 20 | |
| 17 |
| User | Count |
|---|---|
| 70 | |
| 69 | |
| 32 | |
| 27 | |
| 26 |