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.
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.
Power Automate: max function
Returns the highest value from numbers or arrays. Type mismatches break it silently.
Power Automate: Converting Strings to Integers
Power Automate: mod function
Returns the remainder of a division.
When a new email arrives in a shared mailbox trigger
Fires when a new email arrives in a shared Outlook mailbox.
Power Automate: dateDifference function
Returns days.hours:minutes:seconds between two dates as a string.
Power Automate: Convert Time Zone Action
Converts a timestamp from one timezone to another.
Power Automate: workflow Function
Returns the running Flow's name, ID, region, and run details at runtime.