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] […]
Tip #1257: Learn Compose action in Flow
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 […]
Tip #1256: Get attribute of the first record from the list
This is probably a super simple question, but I’m a super simple flow user. After listing records from D365 how would I go about retrieving an attribute value of the first result returned? Michael “Super Simple Flow User” Ochs I won’t name the person who suggested the following: Declare variables to store values. Include top […]
Tip #1252: Creating a Planner task with Flow: wait a minute
If you use Microsoft Planner to plan your project tasks, you may want to automate creation of tasks. You can do this with Microsoft Flow. You will notice that you can’t update fields like the task description when you create a task–this is actually a separate step, called update task details. But if you try […]
Tip #1247: Why you should rename your steps in Flow
When you start using Flow, it is tempting to just add your triggers and actions and go, but there is one small detail you don’t want to forget–rename those steps. For those who don’t know, you can click the … on a step in Flow and select rename. This will then let you rename the […]
Tip #1246: Use “Get Record” to get all the fields in Flow
TIP UPDATE–after further testing, it appears that this tip may not be necessary. Get record is helpful if you need to get additional details from a related record, but you should not have to do get record after an update trigger. You create a Flow that runs when a record is updated. Occasionally the Flow […]
Tip #1244: CDS connector may not fire in administration mode
We did recommend using CDS Connector in Flow (more than once, actually) and most of the time it works great. However there have been some reports that CDS Connector does not trigger in the sandbox organizations while working fine in production. Turns out, there is a good explanation, straight from the source: With the new […]
Tip #1243: Forgot to turn off the Flow
Whoever decided that you shouldn’t be able to save a Flow in a solution if you haven’t turned it off first is a cruel, cruel person Save me please In case you haven’t head, you can add Microsoft Flow to solutions now (yay!) but if you edit a flow without first turning the Flow off, […]
Tip #1240: Trigger another entity’s flows
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 […]
Tip #1227: Use CDS instead of Dynamics 365 connector in Flow
People have been reporting that Dynamics 365 triggers in Flow are not consistent. Sometimes they fire twice, sometimes not at all, sometimes they fire after a manual test run. There are some other weird side-effects I did not even look into. Why? Because of one of them quick tips. Where possible, use Common Data Service […]