How are you replacing that feature in your new Automate Flows? I know I could technically use it. But I don't want to use legacy triggers. Thoughts, recommendations and ideas appreciated.
Solved! Go to Solution.
Why would someone need to 'submit an idea' for an existing feature? Why is it not simply carried through to the next version of the connector?
Thanks for this. How exactly did you do this? Did you use the 'When a row is added, modified, or deleted' trigger's Select Columns or Filter Rows attributes?
Nice. I am just now seeing this feature.
Are you using a model-driven app? If so, does your Flow toolbar button show the Flow? Or did you find another way for the field to be invoked by the user? I want the user to do something explicit to invoke the flow... The model-driven app toolbar Flow button is a little cheesy, but useful in a pinch as an alternative to custom button commands.
They wouldn't need to select the Flow. The Flow would fire based on the changing of the Boolean from no to yes. In this example they select all the records they want and change a field from No to Yes and the flow fires in the background.
So many events happening this month - don't miss out!
Explore the latest innovations, learn from product experts and partners, level up your skillset, and create connections from around the world.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.