Yesterday I was asked about how to avoid variables when you want an index number of the item processed by an apply to each step.
Author: 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
Debug compose actions and condition steps can be difficult as flow runs will only show the output of your expressions. In this post a workaround,
Do you know what you can do when you purchased Power Automate licenses? Or what does that Trial that you enabled give you? Power Apps
This post is all about error handling in Power Apps with Azure Application Insight. Logging all events in your app (wanted and unwanted) within an
This post is all about Boolean logic in the ultimate Power Apps user guide. So that is all the true/false stuff within your app. true
Load More