Why does this privilege checking technique fail?

[skearton]

Hi,

I have a script in Filemaker 12 and want to check for privilege before proceeding with rest of it.

It looks like this:

Set Variable [ $AccountPriv; Value: Get(AccountPrivilegeSetName) ]

If [ $AccountPriv ≠ "Accounting" or

"Order Entry & Invoicing Master" or

"Database Admin" or

"[Full Access]" ]

Show Custom Dialog [ message: "you do not have privileges to delete this..."; Default Button: "OK", Commit: "Yes" ]

Exit Script [ ]

End If

Can I not check against multiple privileges like this?

[Kris M]

If [ $AccountPriv ≠ "Accounting" or

$AccountingPriv = "Order Entry & Invoicing Master" or

$AccountingPriv = "Database Admin" or

$AccountingPriv = "[Full Access]" ]

you gotta specify all the criteria for each evaluation of the contents of $AccountingPriv

[comment]

Alternatively, test for =

IsEmpty ( FilterValues ( Get (AccountPrivilegeSetName) ; "Accounting¶Order Entry & Invoicing Master¶Database Admin¶[Full Access]" ) )

[Steven H. Blackwell]

Alternatively, use a Custom Extended Privilege in the desired Privilege Sets to test eligibility for running the script. That's what custom Extended privileges were designed to do.

Steven

[skearton]

Thanks Steven,

Didn't even know about that. Found a good article explaining the technique in case anyone else wants to know more details.

http://www.supportgroup.com/explore/using-custom-extended-privileges/

[Steven H. Blackwell]

Yes, they are very useful. Custom Extended Privileges are a way to extend the business logic of a solution across one or more Privilege Sets. They were intentionally designed specifically for that purpose.

Steven