TAG
Best Practices
Here I share the best practices I use for the Power Platform tools, drawn from my own experience and plenty of learning from other people's mistakes so I don't repeat them. None of this is set in stone, so adjust it to fit how you work. Consistency matters, especially when several people share a platform. I see it constantly: SharePoint sites with mismatched naming, lists with convoluted names, and flows nobody can follow. When you agree on rules, everyone always knows what something means, and onboarding a new person becomes far easier. Even if you never adopt my conventions, at least write your own down. And even if you work alone, building your own reference makes you think, and you will often spot places where things could be better. That reflection is half the value.
Power Automate: reverse Function
Reverses the order of items in an array.
Why you need the question mark operator in Power Automate expressions
Returns null instead of crashing when a referenced property might not exist.
Parse JSON Action
Turns raw JSON into typed dynamic content. Schema-driven.
Do 2 Things at Once by Doing 1 Thing Right
You can't do two things at once, but you can group tasks so one action completes many. A simple mindset shift for getting more done without burning out.
SharePoint - Create File Action
Creates a file in a SharePoint document library from text or binary content.
How to fix the changes conflict error in SharePoint
Power Automate: How to change the run history from 28 days
How to call Microsoft Graph API from Power Automate?
How to generate an Excel ID to access data in Power Automate
Power Automate: How to Get Your Flow’s Name
Power Automate: coalesce function
Returns the first non-null value from a list. Null if all are null.