Summary
I was very tempted to write this chapter much earlier in the book but felt that you need to understand the tools before mastering how you can improve logic app performance. In this chapter, you have been able to consider running code in parallel and the benefit of doing this. You have also considered that branching your logic app will also scope the data to entities on the same branch and above the action, as well as to any sections that are not in a branch. You have also learned to use branches that will only be used based on the status of the previous action – if the earlier action failed, follow, and use the fail branch. The default setting for all branches is that the earlier action passed. This is referred to as the run after state.
We considered a Common Data Service (Dataverse) action called List rows, which filters the entity by performing an OData query. Alternatively, we have the Get row action, which although similar relies on you knowing the primary GUID...