Always stash trigger output into variables or compose before continuing with the flow. If your trigger output contains a record from the underlying storage (Dataverse, SharePoint, etc) get that record and use the output of the get step downstream. Why? Because when you need to replace or recreate a trigger (happens more often than you […]
You know who are the most relentless follow-uppers? Super Simple Flow users, that’s who. Thank you everyone for your answers to my previous question. I have a follow up question. Is it possible to get the value of an attribute off of an entity dynamically instead of declaratively? E.g. instead of blah?[0]?.fullname something like blah?[0]?[someattributenameIgotinapreviousstep] […]
I wanted to name this tip “Do not use variables in Flow” but then it would have been a click-bait, not a tip. Yesterday we worked our way through the concept of getting an attribute of the first record from the list. The very first step we avoided was to “declare the variable”. Yes, it […]
of the