Forum Discussion
Optimizar codigo power query promedio movil
- 1 year ago
Try a Table.Buffer over a as well
a = Table.Buffer(Table.SelectRows(BufferedTable, each [Mark_Real_Proyeccion] = "Real")),Basically - try using a buffer whereever you are refrencing an entiry multiple times.
Monitor resource utilization - Table.Buffer is not free.
- 1 year ago
remove some of the buffers again and add in other places. Sometimes buffers make it slower.
If you want real help then you would want to provide sample data that clearly shows the issue. So more than a handful of rows.
- Anonymous1 year ago
Hi luis-fer-va ,
Thanks for reaching out to the Microsoft fabric community forum.
Please check out this document: Best practices when working with Power Query - Power Query | Microsoft Learn
Especially check out the part containing "Create reusable functions" If you find yourself in a situation where you need to apply the same set of transformations to different values, creating a Power Query custom function that can be reused as many times as you need could be beneficial.
Check this document: Why does my query run multiple times - Power Query | Microsoft Learn and try disabling features like background analysis.
Please try these steps and check if they result in improvement of efficiency. I hope my suggestions give some ideas on how to improve efficiency.
If you find this post helpful, please mark it as an "Accept as Solution" and consider giving a KUDOS.
Thanks and Regards
remove some of the buffers again and add in other places. Sometimes buffers make it slower.
If you want real help then you would want to provide sample data that clearly shows the issue. So more than a handful of rows.
Saludos, lbendlin
Te comparto una muestra de los datos. Hemos identificado que Power Query (Dataflow) se queda corto para este procesamiento específico debido a la cantidad de iteraciones necesarias por fila. Este proceso se ejecuta cuando el usuario presiona un botón en Power Apps, lo cual desencadena un flujo en Power Automate.
Dado que este flujo es una "proyección", los usuarios suelen ejecutarlo múltiples veces al día, esperando una respuesta rápida para poder visualizar el informe inmediatamente después. Esto implica la necesidad de un procesamiento eficiente y optimizado.
¿Podrías, por favor, proporcionarnos una solución que permita llevar a cabo este procesamiento de manera más efectiva, basándote en tu experiencia? Adjunto una muestra de los datos en el siguiente enlace.
- Anonymous1 year agoNot applicable
Hi luis-fer-va ,
Thanks for reaching out to the Microsoft fabric community forum.
Please check out this document: Best practices when working with Power Query - Power Query | Microsoft Learn
Especially check out the part containing "Create reusable functions" If you find yourself in a situation where you need to apply the same set of transformations to different values, creating a Power Query custom function that can be reused as many times as you need could be beneficial.
Check this document: Why does my query run multiple times - Power Query | Microsoft Learn and try disabling features like background analysis.
Please try these steps and check if they result in improvement of efficiency. I hope my suggestions give some ideas on how to improve efficiency.
If you find this post helpful, please mark it as an "Accept as Solution" and consider giving a KUDOS.
Thanks and Regards