I am new to Bubble and I am sure this has been asked before. I have searched the docs and this forum and have not found the answer.
I have a text input element that on exiting I need to run a workflow that may copy it’s value to another field. I am currently doing it when I save the thing (aka record). I would prefer that it happen on exiting the input element.
At this point I am using a free account to take Bubble for a test drive and would rather not purchase any APIs yet.
Hi there, @dev.wameaney… if I understand your post correctly, you should be able to use the An input’s value is changed workflow event to do what you described. So, check it out and see if it would work for your use case.
Hope this helps.
Best…
Mike
mikeloc, Thank you. I was searching for “on exit event” instead of “input changed”. I knew it should be there somewhere.
Bill
I mis-spoke in my original post. What I am actually trying to do is change the value of a disabled input element based on the value of two other enabled elements. I was able to make changes to a thing but not able to change the value of a different input.
The three elements are:
Name: enabled
Screen Name: enabled
Display Name: disabled
when on “is changed” of either Name or Screen Name :
if Screen Name is not empty then
Display Name := Screen Name
else
Display Name := Name
there is a Save and Cancel button at the bottom of these edits. If I use “is changed” and make changes to the thing then I need to undo those changes on Cancel.
Ah, okay… give these conditionals a shot on the input for the display name, and make sure you check the This input is disabled checkbox on the Appearance tab.
mikeloc,
Thank you once again. That is the behavior I am looking for.
I definitely have to think differently using Bubble. In this case the modifications go on the receiving (Display Name) input field rather than the current active (Name / Screen Name) input field.
This is a big help.
Happy to help, Bill. Oh, and one thing you will learn about Bubble is that there is pretty much always more than one way to do something. In this case, for example, you could have used the workflow event from my initial response to set a custom state when either the name or screen name fields are changed, and you could set the initial content of the display name field to the custom state’s value. Over time, you will get a better feel for when to use the different options that are available in each situation, but at the end of the day, if it works, it works.
This topic was automatically closed after 70 days. New replies are no longer allowed.
