[Create Thing if Doesn't Exist] Doesn't Set Search Constraints When Creating

Need help
1

Make changes to a thing: Do a Search For… (some constraints) Create when thing doesn’t exist

On the first run, the search doesn’t find the thing (expecting to not find)
Then creates the thing (good)
The fields for that thing that I was originally constraining are empty (bad)
I am expecting it to set those fields to the respective constraints

Is this a bug or is this a limitation on Bubble’s capabilities?

Thanks

2

I don’t think it’s a bug because you told bubble:

If you don’t find this thing create it. It doesn’t use the constraints as inputs to create, only to find.

Can’t you add those in the same or another step?

1 Like
3

Is there a way to fire that separate step only if it created it?

This works, but unnecessarily updates the item if it existed. Not too big of a deal, but inefficient.

Thanks

4

Ah - I see…

The other way I would investigate would be to first check if it exists - ie run a do a search. If it’s not found update an indicator to say that. Then use that indicator to tell which step to run. Store it either in the database or as a custom state that you can track.

5

This topic was automatically closed after 70 days. New replies are no longer allowed.