Is it abug when I can edit a row which the Edit action is disabled?

AppSheet AppSheet Q&A
,
1

I have an app to assign user with daily task.

Whenever the due date is gone by, I don’t want the user to edit the row anymore.

Currently, at Edit action in “/Action/Behavior” section, in Only if this condition is true, I have inputed the condition “1>2”; and the Edit button is gone. The user does not see the Edit button to click.

However, when viewing the disable-to-edit row, if user manually adds “&page=form” in the url of the browser and enter, he CAN STILL edit and save the row.

My question is: Is it a bug, or appsheet just “hide” the Edit button for non-experienced users?

Capture.JPG
Capture.JPG1159×490 56.8 KB

2

In your condition its clearly mentioned 1>2 which not true. 1 is less than 2 so the condition does not match and hence it hides the action.

They can still edit the form because you have not controlled user from editing in table level but on action level only.

Have a look at this. This might help you.

Control add, update, and delete operations - AppSheet Help

1 Like
3

There is a difference between creating a condition for the edit action and setting the row as editable or not.

I suggest you go to the row setting in data columns in the editor, click on the little pencil to edit the settings of this row, and use the following formula in the “Editable”:

[Due date] <= TODAY()

PS: I do not know if the column name is DUE DATE, if not just replace the name with yours.

4

Thank you. But this is table level restriction. I wonder if appsheet have any row level restriction that user can edit all the row, but cannot edit row with (example) column named: [COMPLETED] = ‘DONE’

5

Conditionally allow column edits (Editable_If) - AppSheet Help

2 Likes
6

Thank you @Steve . But is there option to disable users from opening the form for those not-editable-rows?

I want user to view all the rows.. Rows that have [COMPLETED]<>‘DONE’ is editable. Rows that have [COMPLETED] = ‘DONE’ is not editable (user can not open FORM page).

I can achieve this as in my 1st post, but, I am paranoid that, some experienced user, if they add “&page=form” at the end of the detail view, he can STILL edit the row, even when “Edit” button is hidden.

7

There is no way to prevent the user from doing that.

1 Like
8

With a smart Valid_If setup, those kind of “edits” won’t generate any problems

1 Like
9

Yes, I am doing that way. But letting user opening the form make them “feel” that they can edit the record.

If I have let’s say, 30+ column in my table, it take quite times to disable all 30 columns. Of course, I can just “Valid_if” 1 single column, and send error message to the users to tell them that the record (all column) is not editable, but it’s great if we can event prevent user from opening the form.

10

I understand, it’s just that this behaviour is a core part of the platform and you do more harm than good by disabling it

1 Like