OData: And Operator
Combines multiple conditions where all must be true.
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: Run a Child Flow Action
Calls a reusable child Flow.
SharePoint: Automatic Document Management
OData: Equals Operator
Filters records where a field exactly matches a value.
Power Automate: Condition Action
Routes the Flow into a true or false branch based on a comparison.
OData Reference: An Introduction
Introduction to OData filtering for Power Platform data sources.
Power Automate: Apply to each Action
Loops through an array. Use item() to reference each element.
Microsoft Forms: Voting in Meetings
Microsoft Teams: You’re on mute - optimize meetings
Ten habits that make online meetings worth attending, from mute etiquette to being upfront about Copilot.
Microsoft Teams: Don’t want to use a SharePoint Site or your OneDrive?
Tools: 1Password
