By now you know not to trust triggers and recapture their output in the step immediately after the trigger. That way you fix only one step when trigger is replaced. Do not use trigger output beyond the first step in your flow Sulking Enabler But do you want more? Do you want to keep the […]
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 I’m a sucker for some open source goodness. This time the goodness is from Aiden “President” Kaskela. (Got something to share? Send your wares to jar@crmtipoftheday.com). The Common Data Service (Current Environment) trigger in Power Apps allows you to run your cloud flow when certain fields are updated, but there are two shortcomings: […]
It’s not every day one gets to chime in on a post from Jerry, the lifetime tipster and Power Automate connoisseur. In this post Jerry talks about When a record is created, updated, or deleted trigger in CDS (current environment) connector and how to tell the event that triggered the flow using a clever combination […]
Power Automate is very handy to serve as a webhook. Add When a HTTP request is received trigger and you’ll get a URL to call after you save the flow. (Genuinely curious if it should be “an HTTP“ instead.) Any flow triggered by HTTP request executes asynchronously, i.e. it returns to the caller immediately after […]
I have a flow on Account, and sometimes I want to trigger that flow to run when a related contact is updated. Given we don’t have child Flows yet, how can I make a change to one record execute a flow on a different entity? One trick that I’ve used on workflow that is also […]
of the