If the Edit action Only if this condition is true is set to only:
ISBLANK([Signature])
Does that work?
If the Edit action Only if this condition is true is set to only:
ISBLANK([Signature])
Does that work?
Yes that works.
Let’s try this:
ISNOTBLANK(
FILTER(
"Employees",
(USEREMAIL() = [User Email Address])
)
)
This should allow you to edit any row.
Yes that allows me to edit any row
Are any User Email Address column values blank? If so, LOOKUP() might be returning the Administrator column value from the first row it finds with a blank User Email Address value. If so, we’ll have to work around this. Instead, try:
OR(
ISBLANK([Signature]),
ANY(
SELECT(
Employees[Administrator],
(USEREMAIL() = [Email])
)
)
)
There are no rows with a blank [User Email Address]. There were 3 without an [Administrator] value which I have subsequently set to ‘FALSE’ anyway.
The expression above is allowing me edit all records.
MauriceWhelan:
The expression above is allowing me edit all records.
Correctly, or incorrectly?
Incorrectly if it should be doing so only if the value in [Administrator] for the logged in user is TRUE. I changed the value from TRUE to FALSE and it still allows all records to be edited.
Are you testing this with the same email you use to log into the editor? Because if that’s the case, if the table is editable at all by anyone, I believe you (as author) are ALWAYS allowed to edit. Which means you should be testing all of this with a completely separate email, if you haven’t been already.
@Bahbus
I am not sure this is the case because I had the condition set initially to ISBLANK[Signature] and I couldn’t edit records where [Signature] had a value.
Could be. Actions sometimes work differently, than Editable If conditions on the column itself.
Want me to take a look? sc2758g@gmail.com
That would be great @Steve, thank you. I have granted access as co-author.
I’ve spent some time looking at it and tinkering (no changes were saved). I can’t find any explanation for the odd behavior. All the expressions I tested worked as expected–except in the app itself.
Looks like a bug to me. I recommend engaging support@appsheet.com on this one.
Sorry I couldn’t help more.
No problem @Steve. Many thanks for the support on it.