AnsweredAssumed Answered

Run Script With Full Access Privileges fails to run with full access when hosted

Question asked by user9890 on Jan 6, 2012
Latest reply on Jan 31, 2012 by TSGal

Summary

Run Script With Full Access Privileges fails to run with full access when hosted

Product

FileMaker Pro

Version

11

Operating system version

OSX 10.6.8

Description of the issue

A script is set to run with full access privileges (RSFAP).  When a user with limited record access logs into a system, I had a script set to run with full access privileges set a $$_Var with ValueListItems over a set of records that this privilege set was restricted from viewing.  Setting the script to RSFAP technically should allow the $$_Var to be set with the value list items.  It does not.  This only fails when the file is hosted.  This only fails on a file created in v11 and opened in v11.  After the hosted file has been opened in a previous version, the bug goes away.  I've received confirmation of this bug with FMDiSC and with Steven Blackwell.

Steps to reproduce the problem

Create a file in v11.
1 table
1 field - set field to auto-enter serial
create 10 records
create value list to this field, all records in this table
create privilege set
in the new privilege set, set view access to this table to "no"
enable the guest account (or create a new account)
assign this privilege set to this account (guest or other)
create one script with the following steps (pauses may be omitted)
     Pause (1 second)
     set variable ($$_this_variable) with: ValueListItems ( Get(FileName) ; "value_list_name" )
     Pause (1 second)
Turn off auto-authentication in file options so that you're forced to enter a user/pass
select the script you created to run on open
upload file to FileMaker Server
attempt to open in v11 with the guest or other new account you created above

Expected result

a $$_Var set with 10, return delimited serial numbers.

Actual result

nothing

Exact text of any error message(s) that appear

none

Configuration information

none

Workaround

Open file in v10, then, it is magically cured.

Outcomes