Prior to the Wave 1 2020 release, the allocation of charges capability was available only on the Purchasing side of F&O processes. In this blog, we’ll review the Current State process and share some exciting news about Future State process.
When creating Flows, there are various scenarios in which we need to check for multiple conditions before performing a certain action. In the past, multiple conditions could be combined by using expressions. However, just recently, Microsoft introduced a new advanced condition builder that lets you easily add multiple conditions in your Flow without having to write expressions for them. This condition builder is extremely easy to use, and if you are a Dynamics 365 CE user, you will find it similar to something you probably use on a regular basis: Advanced Find!
In today’s post, we’ll explore the advanced condition builder through a real-life business example. Let's say our business inspects roofs for houses. We prepare different estimates for different types of damages; if a roof has physical damage, we prepare an estimate document for the repairs and share with the customer. Technically, what we are doing is checking for a value for Physical Damage in Dynamics 365 and also looking for a document titled "Physical Damage Estimate" in the associated SharePoint folder.
When we add a "Condition" step in our Flow, we now this new condition builder:
The advance condition builder allows us to do the following:
Note that there’s a terrific feature in this tool for when the groups are getting complex: the blue line to the left shows how the groups are contained, making it easy to ensure we’re adding conditions to the correct group:
The most exciting and useful ability of the advanced condition builder is that it lets you set conditions that address multiple sources! Coming back to our roofing example – we can set a condition that checks for both a field's value in Dynamics 365 AND the existence of a document in SharePoint. This makes automation a lot easier and more efficient – and reduces human involvement in the process.
Our conditions will look like this in the condition builder:
As you can see, we are checking for items in both Dynamics 365 and SharePoint in our condition. Imagine how amazing this will be when you are working with more than two sources and you need a check in place for all sources. This will eliminate a lot of manual work for end users!
The advanced condition builder makes building complex Flows even easier than it was before. In addition, it takes automation to the next level by allowing us to set conditions in multiple sources. Try it out and tell us what you think!
Don't forget to subscribe to our blog - happy Flow’ing!