A rookie question and mistake from me?

Hi. I’m completely new to AppSheet (and I like what I see so far!) so please be gentle :slight_smile:
I have a question that will probably be very easy to be answered:
Looking at the Wind Turbine sample, I wanted to make ALL_CHANGES of Turbines records be available to all users, not only the ones in the Admin table. For some reason it didn’t work for updates by Inspectors, which I expected to be included in all changes clausula. It just added the trashbin to delete Turbines, and that worked.
No luck with replacing “ALL_CHANGES” with UPDATES_ONLY, or “TRUE” or “YES” either. It just messed it up for the Admin users too. I assume regarding CRUD rights, TRUE and YES are not in the options. the expression for various users worked as expected too.

What am I missing and how to remove any condition for Editing? Snapshots attached. Admin: abraham, Inspector: peter. Admittedly, I put an equal sign between Inspector and User in here. I created an user of the sample up to test that.

Thanks in advance,
Sime

Edit: I realized as a new user I can upload only 1 picture to the forum (why?) - hope I presented the scenario well.

Click this button to get rid of the expression functionality, and get the simple buttons back:
image

Then just select all 3 buttons:

2 Likes

Marc, thanks for the quick reply! Seems logical. I did that and still no luck. Did it work for you?
I don’t think any slices or security settings are involved.

What do you mean it didn’t work? Looks like it worked in your screenshot. Is there some issue?

1 Like

When peter, I see the glasses to do inspection for that turbine but not the Edit (with pen) icon for doing updates.
abraham, being an Admin has that showing up, on this screenshot.
Thanks again!

Oh I see.

Check the Behavior condition for the Edit Action

Make sure you’re looking at the Edit Action for the right Table, too.

2 Likes

Thanks Marc - will check that! Gotta go to the church now but will do it after.

Marc , I just went to that place, thanks for your guidance!
Didn’t even know those settings exists in Behavior. It worked like a charm!
Thanks again, have a great week!
PS to me it still looks redundant (and what supersedes what vis-a-vis the all_changes option) but I understand that is a system edit property. And it seems in Behavior is on a record level, whereas in “Are updates allowed” works on the Table level. I’ll try to digest the functionality behind that.

Table access controls access levels for the entire Table.

Behavior > only if condition controls when that particular Action will be available. These can be specified per record, but not exclusively.

2 Likes

Makes sense now, got it. Thanks Marc!

1 Like