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.
OData: Lower Than Operator
Filters records where a field is strictly less than a value.
Power Apps: Choices Function
Returns the selectable values for a SharePoint or Dataverse choice column.
Power Automate: OneDrive for Business - Get File Content Action
Returns a OneDrive file by file ID.
Power Apps: Single Source of Truth
OData: Not Equals Operator
Filters records where a field does not match a value.
SharePoint: ISLOGICAL Function
Returns true when a value is a boolean.
Power Automate: Compose Action
Stores any data, expression, or computed value for reuse downstream.
OneDrive: More than a synced folder
OData: Greater Than Operator
Filters records where a field is strictly greater than a value.
Power Automate: Move Email Action
Moves an Outlook email to a folder.
