Power Automate: Switch Action
Routes the Flow into multiple branches based on a single value. 25-case limit.
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: Try, Catch, Finally
OData: OR Operator
Filters records where at least one condition is true.
Power Apps: Color Function
Returns a named color value like Color.Burlywood instead of an RGBA code.
Power Automate: Delay Action
Pauses the Flow for a fixed duration.
How to auto-layout your elements in Power Apps?
OData: Lower Than or Equals Operator
Filters records where a field is less than or equal to a value.
SharePoint: WEEKDAY Function
Returns the day-of-week number from a date. Three return-type options.
Power Automate: Create new folder Action
Creates a SharePoint folder. Auto-creates missing parent levels.
OData: Greater Than or Equals Operator
Filters records where a field is greater than or equal to a value.
Power Automate: OneDrive for Business - Get File Content Using Path Action
Returns a OneDrive file by path.
