Enhancement request: Stop flow if lookup retrieves no records
Crossposting Steve Klett's request for upvoting and wider Product team visibility:
I've got a few flows that will fail miserably if a previous lookup failed to yield results. I've looked through the lookup settings page and don't see any way to indicate minimum result count or anything that could be used to catch this. I've thought about a script that could throw an exception, but that adds complexity.
What is needed is an option on the lookup to tell it zero results is NOT a success.
6
Comments
Hi Stephen Brandt,
Is the mentioned enhancement achieved? I am facing the same problem. I need to ignore/disregard the records that do not give a result on the Lookup step and prevent it from passing on to next step in the flow.
Please suggest a solution.
Thanks
Hi, Aishwarya M J. The original suggestion was captured for our customer-requested features, and I'm adding your upvote to it. Thanks for taking the time to let us know.
I've asked around a bit, and it seems that Steve had correctly narrowed down the solutions to a JavaScript hook, if that's an option to get your flow unblocked.
I'd like to upvote this as well. I had assumed that a "no-results found" on lookup would trigger a lookup failure but that is not the case. Stephen Brandt you mentioned a solution using a Javascript hook? Do you have more details on that?
The feature request is still active in our product insights, Eric Leung.
For your hook, you would want to look at the preSavePage function stub and push an error based on the expected lookup results.
Please sign in to leave a comment.