When I start developing a new flow there are a few things that I put in place first. For me Microsoft Flow development all starts with making the process robust. Therefore I start with the try-catch pattern as I described in Microsoft Flow – Implementing a Try, Catch , Finally in a flow.
As I wanted to make things easier for my self I submitted this as a template in Microsoft Flow
Try Catch Template
You can find this template by visiting the Try, Catch and Finally Template. One click and you will have the base process in place.
As always, if you need any help implementing the rest of the process please feel free to contact me. Alternatively, if you are looking for people to implement business processes for you then let me know and maybe I can help, even if you don’t completely know what you need.
Discover more from SharePains
Subscribe to get the latest posts sent to your email.
Pieter Veenstra
Is your business still running on paper trails, sprawling Excel files, or ageing Access databases? There's a better way — and I can show you exactly what it looks like. I'm the Technical Director of Vantage 365, a Microsoft solutions consultancy working with clients across the UK, the Netherlands, and worldwide. For over 30 years I've been turning messy, manual business processes into clean, automated systems that save time, reduce errors, and give teams the visibility they need to make better decisions. SharePains is not just any blog run by a Microsoft MVP. Have you ever used Try-Catch in Power Automate? The original post about Try-Catch in Power Automate can still be found on this site, https://sharepains.com/2018/02/07/try-catch-finally-in-power-automate-flow/ Or have you ever used the Pieter’s method to avoid variables and speed up your flows? https://sharepains.com/2020/03/11/pieters-method-for-advanced-in-flows/ You can contact me using contact@sharepains.com
Hi, can you explain for Power Users who don’t use .Net or advanced programming, what this does? What is this concept and how does it work?
Hi,
I think of it is covered in my post other https://veenstra.me.uk/2018/02/07/microsoft-flow-implementing-a-try-catch-finally-in-a-flow/
I short:
I’m running actions in the try section. If anything in any of these actions goes wrong then the catch section will kick in. The catch will not run if the process in the try is successful. So the Catch section is often used to correct or report the issues that occurred in the try section.
Then finally you can use the finally to do things that need to happen when the flow completes. So this could be an email saying that the flow has completed.
Could i move my approval section into the try to help catch errors when people dont fill out the approver field? Its required but SP does not enforce it.
Yes, that is exactly where I would expect you to add the actual process that you want to implement.