Description
This is our Client Portal. Clients belong to Companies.
Our Role column/Key Row Owner Column is the Company ID.
For Clients/Users to sign up, and when they click (Launch) (workflow action) a new row is added to the Companies table, and the Row ID is submitted into their user profile’s Company ID column (which is again the Role/Key Row Owner Column), the Row ID is then added to that field successfully, however about 40 seconds later it’s gone, deleted, or auto-removed.
I checked the community and there’s no problem with users editing their Row Owner Column fields. When I then add it manually through the Data Layer, it stays, and doesn’t get removed.
You mention Roles. Which column have you set as a Role column in your user profile configuration?
Few things to note:
Roles cannot be set from the app for security reasons. You can only set a rule via the data editor or via the API. Roles | Glide Docs
A row owner column should only contain an email address or a value that would match any value in the column designated as the Role column. I only point this out because I see that your RowID column is also set as a Row Owner column and I’m not sure what your intention is with that.
While you can set the Role column as a Row Owner column, I don’t usually recommend that because it leads to confusion. It works and and is probably fine in your case, but I usually prefer to have a Role column just to hold the user’s role, and a separate row owner column to designate which user roles have access to that row.
I’ve set Company ID as the Role column in the user profile configuration. Because what I want users to see is their company content.
Even if I followed your hypothesis I’d still need to manually add each new company’s roles in that new column for each new company, and that is not scalable. Users should be automatically enrolled into their own company and company team, so eventually there must be a way to do it.
If you have access to Glide API, I would suggest using the API to do it.
As part of this flow, use an API call (I see you have Business plan) through the Call API action to set the ID, instead of using the built-in set columns action.
Thank you Darren, this is very helpful. Just to confirm, when Make edits the Row Owner column, the edited, added values will stay there and not get deleted, correct?
Yes, that’s correct. But you don’t need to use Make to set owner columns - it’s only required if you want to edit/set either the Role or Email columns. It works because it uses the Glide API.
