Problem with my table update

[BOMEXPORT_ADMIN]

Hello Community,

Something weird is happening with my App,
I can’t delete or uptade any details with a specefic table despite the limitation formula i’m using that should allows me to make ALL CHANGES :

IFS(
USERSETTINGS(“USER ROLE”)=“SUPER ADMIN”, “ALL_CHANGES”,
USERSETTINGS(“USER ROLE”)=“ADMIN”, “ALL_CHANGES”,
USERSETTINGS(“USER ROLE”)=“CHEF ATELIER”, “UPDATES_ONLY”,
USERSETTINGS(“USER ROLE”)=“MAGASINIER”, “READ_ONLY”
)

i’m using USERSETTINGS formula to limit access to the table DETAILS CMD

Bellow some captures in order to get more details about this issue :

1- as you can see on this view i can’t modify anything on the table "DETAILS CMD"

2- this is capture of formula i’m using to limit access to the table "DETAILS CMD"

3- the table “DETAILS CMD” is a part of another table name COMMANDES bellow is a capture of limitation formula i’m using with the table COMMANDES i’m thinking that this informationmaybe be usefull…

Thanks in Advance

[MultiTech]

Are you using an initial value or app formula to determine the user role?

[BOMEXPORT_ADMIN]

Hello,

YES i’m using App Formula to determinate the user Role :

ANY(SELECT(USERS[USER ROLE], ([NOM D’UTILISATEUR]= [_THISROW].[USER_NAME])))

[BOMEXPORT_ADMIN]

Hello

Any Feedback Please @MultiTech_Visions

[MultiTech · Accepted solution]

Wait… you have a User_Role column in your user table?

- Then why are you using UserSettings? #NoPoint

INDEX(Current_User[User_Role], 1)

Current_User (Slice) - How to conform your app around WHO is using the app Tips & Tricks 💡

One of the core basic functions, included in just about EVERY app I make, is the ability for the app to know WHO is using the app. If the app knows who’s using it, then I can easily control many different aspects of the app: Add/edit/delete permissions How data should be filtered What views are shown What buttons, or Actions, are visible Which workflows should fire off Which columns should be shown or editable etc. Requirements To accomplish this functionality in your app, you need the follo…

---

To answer you question

• What’s happening here is a long-known see-saw bug with UserSettings.
  • UserSettings often has problems with initial values, often requiring a user to open the Settings page in order to populate the value of that formula.

The solution is to stop using UserSettings for anything other than extra settings people can change - which your system doesn’t rely on for basic functionality - and even then you’re better served by creating a space in your User table to hold any of these settings.

All and all, Usersettings was a great idea but poorly executed; it was implemented at a time before actions were a thing, so we needed a way for people to store temporary variables easily.

• Now it’s much easier to handle situations like this with a regular table, actions, slices, quick edits on detail views, etc.

[BOMEXPORT_ADMIN]

Thank You so much !
Those details helped me a lot