Flows from the field: Renaming steps; PSA to-dos; Guard conditions; Converting leads; Vacation requests

Reasons to rename steps in Flow

Writing on the CRM Tip of the Day blog, Joel Lindstrom wrote that it can be tempting to launch a Flow project and start adding triggers and actions. But one important detail is so basic it can be easy to miss—renaming the steps. Any step in a flow can be clicked to rename.

Changing the names of action is important for several reasons, from avoiding rework to reducing errors and helping the next person to look at your flow. Lindstrom explains his thinking around the benefits and a bonus tip, too.

Creating to-dos with Flow and Dynamics 365 PSA

Returning from the MVP Global Summit, Antti Pajunen drew inspiration from Teams MVP, Vesa "Vesku" Nopanen, about using Flow with Dynamics 365 Project Service Automation (PSA). Routinely, PSA users want to see their Resource Assignments and Bookable Resource Bookings. Some options do exist using Power BI, but Pajunen noted that they're not always the most convenient.

According to Pajunen, it's best to think about this approach for to-dos in context of personal flows rather than generic flows. He laid out steps to set triggers that fire off a flow whenever a Resource Assignment is made and demoed a default environment for two users, as well as a personal approach in Customer Engagement to test the flow.

Guard Conditions: Protecting against nested conditionals

Nested conditionals in almost any form of code, but particularly Flow setups can be difficult to understand and might even lead to errors. Drawing on 25 years of software experience, ...