Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowJuly 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more
Hi all!
I am trying to move a lot of work done in Power Query Desktop (Excel) to Power Query Online and while testing this I experiance some limitations.
E.g. Expression.Evaluate(#shared) does not return correct values for defined queries and parameters.
Works fine in the desktop version.
Is there anywhere defined what limitations apply to the Power Query Online and also of these limitations are permanent or temporary?
If limitations are temporary I can live with it and migrate to Power Query Online, but if permanent I need to change a major part of the design which will be quite an effort....
Grateful for any light on this!
Thanks @ImkeF ! Will dig down in your suggestions and see if I can reach serendipity 🙂
Hi @tswm00 ,
unfortunately this is a general problem with PQO (see: Alternative calling function with text string (microsoft.com) ).
But this function might help with the conversion: Automatically create function record for Expression.Evaluate in Power BI and Power Query – The BIcco...
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.
Join Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.