Custom Action - Set Column Value weird reset

Hi Everyone,

I’m trying to set a role value in the user profile depending on which button someone clicks and which form they submit.

For example, if they click “newly wed” then after they submit their onboarding form, I want to have as a role “newlyWed” but if someone goes through the “vendor” path, I want them to have vendor set as the role in the user table.
The value set in the Role column is without the quotation marks.

For some reason, I do manage to set it and I see it in the user table but then, a few second later, it seems to disappear from the cell and it goes blank,

Not sure where the problem is ?
if you have any pointers, that’d be great.

Thanks

Unfortunately, you can’t change the role column from the app. It might work when previewing from the builder, but it won’t work in production.

You could use manual or webhook trigger workflow. But keep in mind that you must add verifications to make sur that the user has access to change these properties.

I will soon share a tutorial on how to share row owners based on row id and multiple roles. That might interest you.

1 Like

As @MaximeBaker mentioned, you’ll want to add in some verifications, but this is a brief demo of the process:

3 Likes

Thank you all for the help and guidance and apologies for my late reply to this thread.

I realised that I didn’t explain myself as well as I should have.
My goal was to find a way to identify certain user either being newly wed or professionals/vendors.
I never actually wanted to touch the “Role” column in Glide.
Watching @Robert_Petitto 's video I realised that I could use a choice element and have them select who they are when they onboard.
Then I set different actions based on their profile types and now it’s all good and working !

Thanks again @MaximeBaker and @Robert_Petitto !

I know I already said this a few weeks ago. Been busy. But a video will soon be out to show you how to implement the row owners sharing method!

This is really helpful! I have been experiencing the same issue. :100:
Thank you Robert!