Hello!
I’m experiencing an issue where the Role
column in my Users
table — which is used to distinguish between “Store” and “Customer” users — is repeatedly being cleared or reset to blank.
How it’s currently set up:
- The
Role
column is a basic text column in theUsers
table. - I am using User Profiles, tied to this same table.
- The
Role
is initially set in one of two ways:- Via a Choice component bound to
User Profile → Role
(initially tried but removed after I thought the Choice component was causing a reset). - Via a button workflow using
Set Column Values → User Profile → Role = "Store"
or"Customer"
- Via a Choice component bound to
- This value is written directly into the user’s row (confirmed via User ID), and works at first.
Observed behavior:
- After successfully setting the
Role
, it will occasionally disappear (reset to blank), even without further input or overwrite actions. - Other user data in the same row (e.g. Full Name, Email) persists correctly.
- The issue occurs across sessions and screen transitions, without a clear pattern.
- When I implemented a temporary workaround by duplicating the Role column into a
Temp Role
orLocked Role
column, that value persisted briefly — but it has since also exhibited similar reset behavior.
Steps I’ve already taken:
- Confirmed that User Profiles are enabled, and the screen is filtered by
User ID = signed-in user
. - Verified there are no duplicate user rows in the Users table.
- Confirmed that all actions use
Set Columns → User Profile → Role
— not “This item”. - Avoided use of Form Containers for role assignment (which might create new rows).
- Ensured the
Role
column is not computed, not part of a template, and not overwritten by any lookup or relation. - Added debug fields to display
User ID
,Role
, andThis Item → Role
for live testing.
What I need:
- Clarity on what might be triggering the reset of this specific column.
- Recommendations on how to prevent Glide from overwriting or blanking this column, assuming no workflows are actively changing it.
- If this is a known bug or edge case, I’d greatly appreciate any timeline or workarounds.
Thank you for your help — I’m happy to provide app access, screenshots, or screen recordings if needed.
Thank you,
Samir