Button State Changes when Database Property Changes

I’m trying to figure out a way to have the button state change be based on when a value in a database property changes, but since the screen doesn’t auto refresh when data changes, the button state change doesn’t trigger. We are trying to link out to Stripe’s checkout page to allow customers to enter their payment info securely and have it be saved in Stripe, then return to the checkout process on our Adalo app and go on to the next step, which is why we want to have the button state change after we update the database via the api and then have the button become “Actionable” when that property changes.

Hi @delgesu1745

You can make the button a list then filter it. set it to refresh. maximum number of items 1. ALSO, maybe you can use change input value and input field and set the visibility conditions of the button based on the input field.

Thanks for responding @nicoledalo! I’m not sure I follow on the button list refresh suggestion. So if it’s a list of buttons then you mean set it to auto refresh when a user adds and item in the advanced settings? I guess I don’t see how this would work as the user has to add the item then. It can’t be driven by if we change a field in the database. Maybe I’m misunderstanding though.

On the second suggestion, we don’t really have fields they fill in on this screen. This action is based on something they do outside of the Adalo app, which is why it’s proving hard to achieve.

what i suggest is you having another button but you change the visibility of the button to be visible only when a certain criteria is met

you can use a boolean function for this and am sure it will work as expected

Hi, if you are using Windows 11, this may be the cause.
It is happening that some screens are not updating when values ​​in the database change only if you are using Windows 11.
Could you try to run your application on Windows 10 and Windows 11 and evaluate the results?
I am having this kind of problem, and I see that it only occurs in these situations.
I have already reported the bug to support, and they are evaluating it.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.