When you create a new Model Driven App today, you will find that you have an options between the Modern app designer and the Classic
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
After yesterday’s post about environment variables in Power Automate, today it is time to look environment variables Power Apps. Environment Variables As I showed in
When you create flows inside a solution you might have noticed these Environment Variables. What are they and what can you do with them? Environment
Power Automate and Power Apps use the same connectors. So do you use a flow or app code? It can be an important choice. An
Recently I was asked about creating a team template in Microsoft Teams and apply this team template to a team created using Power Automate. Education
Load More