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.
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.
[…] Last week I was wrong when I said You only need one template to get started. […]
[…] a regular basis I refer Microsoft Flow developers to my Try-Catch-Finally-patttern, but what if you need to use LogicApps. Can you use the same […]