Why I prefer to fail forward?
Why I push forward to fix problems instead of rolling back to a safe version
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.
SharePoint: MONTH function
Returns the month of a date as a number from 1 to 12. Empty date fields return 12
How to stop an infinite trigger loop in Power Automate?
Stop a flow from re-triggering itself with trigger conditions, flag columns, or a create-only trigger.
Dynamic Content Troubleshooting in Power Automate
Power Automate: Teams - When I'm @mentioned
Fires when you are mentioned in any Teams chat or channel. Webhook-based.
Power Automate: Teams - When I am mentioned in a channel message Trigger
Fires when you are mentioned in a specific Teams channel. Polling-based.
Nuggets of Wisdom
Power Automate: sort Function
Sorts an array in ascending order by value or property.
How to fix the "InvalidOpenApiFlow" issue when Enabling an Imported Flow
Lookup and reverse lookup tables
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.