To encourage a potential new AppSheet customer I have given a copy of one of our apps to this new user. As a new user testing out the platform, they have a free account.
It seems that using an expression to limit table updates 'DATA > TABLES > “Are updates allowed?” does not function as it does with a paid account.
Is this intentional or is there potentially a bug or something else I should consider?
Typically, I use a SWITCH statement to determine user rights. In this app copy, this does not work. Even a simple statement such as IF(USEREMAIL()=“this@email.com”,“ALL_CHANGES”,“READ_ONLY”) does not work. Any expression seems to make the table READ_ONLY.
The expressions evaluate correctly in the builder but the table is still READ_ONLY.
While I definitely appreciate your input Steve, I have ruled out both of the possibilities you list AND I have tested the expression multiple times. Each time, the expression evaluates as expected.
In the two images I posted, the views depicted, and the app in general, the only differences are the email addresses and the user name. Basically, I copied the app to a gmail account I setup for this person. Then I added their new account to the Person’s table. In the Person table, I duplicated the row that listed my information and substituted my name/email with their name/email.
Ah! Did you also give them a copy of your spreadsheet? Or is their copy of the app using your spreadsheet? If their app is using your spreadsheet, their app is subject to the sharing permissions of your spreadsheet. If your spreadsheet isn’t shared with them and doesn’t allow them to make changes, they will have read-only access. Could this account for the behavior?