UserSetting as a holding area for user-specific variables affecting app behavior

(mahesh G) #1

I am learning from various posts that UserSetting can be great holding area for not just “setting” but also user specific variables that control the behavior of the application. The really useful behavior of UserSetting is that it can be written by Actions and changing it does not affect any other user.

An alternative would be a table that is keyed by USEREMAIL to hold these variables. That approach would work well if the set of users is static and one is okay creating a row for each one of them ahead of time.

On the other hand UserSetting does not have this limitation and would be perfect except that there seems be only 10 of them. I do not see a way to add more. For most apps, where UserSetting is truly used to hold “settings” that should suffice. But when it is used as a holding area for user-specific variables, I can see how one could easily run out when the app has significant complexity.

May be a feature request for AppSheet? Curious what other alternative ideas others are using.

Update unrelated second table when row in first table is selected on View
(Aleksi Alkio) #2

I changed this as a feature request.

One workaround is to save more “variables” in one field than just one. For example you could fill the field like “Variable#1 , Variable#2 , Variable#3 , etc. Then you could read variables out of it like INDEX(SPLIT(Userettings(Variables),” , "),1)

1 Like
(mahesh G) #3

Thanks @Aleksi
Agree. I did think about overloading on lines you suggested, just that it would get harder to debug.

I am good for now but was just checking on possibilities. Thanks for making it a feature request.

1 Like