New expression editor in Power Automate

Hello everyone and welcome to my blog. Today I will discuss about the new and improved expression editor in Power Automate.

Before you read further, a quick word of caution – This is an experimental feature and should not be tried on production instances.

Navigate to your Power Automate flow window. Did I tell you it’s no longer https://flow.microsoft.com? Well, that’s a subtle change but now similar to Power apps maker portal, you have Power Automate maker portal which can be browsed using https://make.powerautomate.com.

Let’s focus back to our topic. On your Power Automate screen, you have the Settings option on top right menu. Select that and then click on View all Power Automate settings.

Improvement in expression editor and SharePoint connector in Power Automate

Here you get an option to enable the Experimental feature and change the display language. Enable it and save your changes.

Improvement in expression editor and SharePoint connector in Power Automate

So let’s see what’s in the experimental feature? The first and most exciting thing to discuss is the new expression editor.

When you want to enter a dynamic expression, you now get couple of options. The first option is to enter Dynamic content.

Improvement in expression editor and SharePoint connector in Power Automate

And the second option is to enter formula expressions.

Improvement in expression editor and SharePoint connector in Power Automate

I hope you can clearly distinguish the difference. The expression window has more real estate now rather than the cringy and constrained UI we had earlier where you can’t even see your entire expression in one glance.

Another great advantage is you can select dynamic content in your expressions without switching tabs.

So that’s about the expression editor. The next noticeable difference is the improved and intuitive Query editors for SharePoint connectors. Look at the below Get Items action for SharePoint connector.

Wonderful isn’t it? Especially for someone who does not like to write those complex expressions in OData query syntax.

Hope this helped. You will also like the below posts.

Debajit Dutta
Business Solutions MVP