Content of the Article
- The Advanced Condition Builder in Microsoft Flow
- Peek Code in Microsoft Flow
- Conclusion – Condition Builder in Microsoft Flow
In the past, it was necessary to use expressions when multiple conditions were used in Microsoft Flow. Expressions are functions, processes or methods written in a common programming language. In Microsoft Flow, you can use expressions for actions, conditions, or any switch to process data. In combination with variables, it is possible to execute some very useful commands such as calculate dates, manipulate strings, extract parts of a string, and much more.
Recently, Microsoft introduced an advanced Condition Builder for Microsoft Flow that makes it easy to insert multiple conditions without writing expressions. This Condition Builder is very intuitive and will seem familiar to most Microsoft Dynamics 365 users, because of the similarity to the advanced search in Dynamics CRM.
If a step is added, a condition can be selected.
By clicking on the plus symbol, rows or groups can be added. Theoretically, you can add as many conditions as you like.
The conditions can be grouped with the commands "And" and "Or".
For more complex circumstances, a blue line shows which conditions are contained in which group and how the query order looks like.
One of the most exciting features is certainly the ability to query conditions from multiple sources. For example, a value can be checked within Dynamics 365 and the existence of a document on a SharePoint. Or whether a file created with Microsoft PowerApps already exists on the SharePoint.
This feature reduces manual work and takes automation in Microsoft Flow to the next level.
The advanced Condition Builder is available for all newly created conditions that you add to a flow. It is not available for existing conditions. If you want to use the new Builder with existing flows, you must add a new step and drag the actions from the old conditions to the new ones.
For larger actions with many interfaces, it can be difficult to keep track. For a better overview of which data is sent via the flow connectors, a look into the code can be taken.
With this option you will see the full JSON of this action. This includes all input for the action, such as the text entered and the expressions used. For users with programming knowledge, the flow can be validated in detail.
Conclusion – Condition Builder in Microsoft Flow
The advanced Condition Builder makes it even easier than before to create complex flows. The automation features are becoming more and the Condition Builder is certainly not the last of them.
Do you have any further questions? Contact one of our consultants or leave a comment.