So I have a searchbox with a workflow to when the value is changed, create a thing with the searchbox’s value (which is a geographic address). Apart of this workflow is to go to another page using that step (creating the thing).
Now, this flow is perfect for when we dont already have the thing (address) in the database, but when we do have the address in the database already, the step to go to another page does not send any data (which makes sense because the go to page step is supposed to take the property from the previous step which creates a property).
So only create the Property if “Do a Search for Property” first item is empty
Click “Do a Search” and add the constraint" Address= This searchbox`s value.
(Currently you are doing Do a search for properties address doesnt contain)
For the Go to page. Set up 2 workflow actions for go to page.
The first one with an only when the “Do a Search”:first item is empty (ie no similar address exists yet)
For the Go to page nr 2. Data to send: Do a Search for Properties where constraint Address= Searchboxs value: first item.
That will send over the address that you already have to that page.
but do that second go to page only when the first item is not empty
Hey yes this makes sense. I get stuck at the Search for constraint though. Because its a geographic address being input, it only allows these parameters.
Add Only When Search for Property’s Address DOESN’T contain This SearchBox’s value on your Go to Page action.
Now copy that action and change to Only When Search for Property’s Address CONTAINS This SearchBox’s value. The data source could then be This Do a Search for Address with condition address = SearchBox’s value.
Stop thinking about If/Then and start thinking about Case statements. That is how Bubble works.
The only issue I see with this is that I am taking the user to the page after the property has been created. So the first “doesn’t contain” statement will not work because the workflow prior creates a property with that searchbox’s address.
So it almost needs to be, go to page using the result of step 2 if the property was just created, otherwise go to the property thats address is the searchbox’s value
OMG I think I figured it out I was resetting the input before going to the next page and so during debugging realized when it was searching for the searchbox’s value nothing was showing! DUHHHH thank you both!
I was resetting the input before going to the next page and so during debugging realized when it was searching for the searchbox’s value nothing was showing! DUHHHH thank you both!