This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowThe Fabric community is now in read-only for platform upgrade. Learn more
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
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
| User | Count |
|---|---|
| 23 | |
| 22 | |
| 14 | |
| 14 | |
| 13 |
| User | Count |
|---|---|
| 47 | |
| 39 | |
| 24 | |
| 22 | |
| 20 |