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
3 thoughts on “Microsoft Forms – The hidden options of branching in Forms”
Can we create a flow to that we can pass the MS Form id dynamically .
For ex If I have 4 forms do I need to create 4 different flows to analyse the response
Yes but in that case if I have 4 MS Forms I will have to create 4 different flows right.I want a generic solution so that I can manage all the form responses using one flow by the passing the form id dynamically i.e. using dynamic content.
Is there any way to achieve the same
Can we create a flow to that we can pass the MS Form id dynamically .
For ex If I have 4 forms do I need to create 4 different flows to analyse the response
Hi Ashtosh,
You could use the trigger When a response is submitted from the Microsoft Forms connector.
Yes but in that case if I have 4 MS Forms I will have to create 4 different flows right.I want a generic solution so that I can manage all the form responses using one flow by the passing the form id dynamically i.e. using dynamic content.
Is there any way to achieve the same