Announcements
Hello!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.
Thanks!
Rich
Hi @Anonymous ,
You could submit your idea here.
Best Regards,
Wearsky
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?
I got around this limitation by using a yes/no column. If the column is yes it fires off the flow.
I got around this by using the trigger that goes off when you change a columns content. I used a Boolean column to trigger the flow.
Hi Rich,
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?
That's it exactly.
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.
Got it, thanks!
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Haque 594
Valantis 328
David_MA 281 Super User 2026 Season 1
