You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is not (easily?) possible to store a checkbox prompt value as a user attribute. The first problem seems to be that the backend returns the initial value as Python's True or False, but the frontend treats both as strings, so the checkbox is always set as checked. The second problem is that when the checkbox is unchecked, it is not even sent in the user-settings query, so the later User Write Stage does nothing and keeps the attribute enabled. And when it is checked, it seems it's saved as a string on rather than boolean.
This first problem happens when the initial value expression is set to:
This one solves the issue of checkbox being checked when attribute is not true, but it still has the problem of not saving the result when unchecked.
How to reproduce
Create a boolean attribute passwordless_login on the user object.
Create a checkbox prompt user-settings-field-passwordless-login with field key attributes.passwordless_login and initial value from above, with initial value as expression enabled.
Add this prompt to the default-user-settings stage.
Expected behavior
It should correctly store the attribute value as true or false, depending on whether the checkbox is checked.
Activity