It sounds pretty obvious really, you build a solution and you give it a meaningful name or next time you return to your environment you cannot remember what on earth your automatically named flow does or what it was for?
I tend to include 3 things in my flow name (where applicable)
- The owner or purpose of the solution as sometimes you can have multiple flows for one solution
- An order and total number of flows in a solution. For instance, if I have 3 flows for a solution and if they were to run in some sort of order, I would call them 1 of 3, 2 of 3 etc.
- The main purpose of the flow – a brief description of the flow
At the moment there is nothing you can do to sort or organise your flows, therefore keeping the naming convention strict means you will be able to find what you are looking for and recall what each flow does should it develop problems in the future.
What’s your top tip for Power Automate house keeping? Leave a comment below.
Back to Top Tips
