AnsweredAssumed Answered

Fields Set in a Portal using a [Full Access] Script For non-[Full Access] user don't update until...

Question asked by alecgregory on Jun 4, 2013
Latest reply on Jun 6, 2013 by philmodjunk

Summary

Fields Set in a Portal using a [Full Access] Script For non-[Full Access] user don't update until commit

Product

FileMaker Pro

Version

12.0.4

Operating system version

All

Description of the issue

If, in an open record (i.e. Get ( RecordOpenState ) = 1 or 2), an attempt is made to set a field from a related table in a portal by a script set to run with full access privileges when the logged in user is NOT assigned the [Full Access] privilege set, the changes are not shown in the field until the record is committed.

Notes:
1. A refresh window (flush cached join results) script step does not help
2. The field can be directly on the layout or in the portal

I'm using a data-entry pattern based on the ideas in this soliant article http://www.soliantco...ollback-support, The idea being that changes aren't committed until the user hits save. The changes will be rolled back if the user presses cancel. Some of these changes will be made by scripts, and will need full access privileges. So it's pretty important that uncommitted changes are shown on the layout.

The steps to reproduce the bug are below, and an example file is attached.

Steps to reproduce the problem

Let me know where I can send the example file

TO CONFIRM A USER WITH [FULL ACCESS] PRIVILEGE SET CAN SEE DATA IN UNCOMITTED PORTAL RECORDS

1. Open Database “full-access-bug.fmp12”
2. Login as “Admin” with no password
3. Create a new record
4. Click on the button titled “Set Field in Portal”
5. Confirm a new row has been added on the portal
Click “Save”
6. Repeat steps 3 through 6 as desired, then close the Database.

TO CONFIRM A USER WITHOUT [FULL ACCESS] PRIVILEGE SET CANNOT SEE DATA IN UNCOMITTED PORTAL RECORDS

1. Re-Open the Database “full-access-bug.fmp12”
2. Login as “User” with no password
3. Create a new record (by going to ‘Records’ then clicking on ‘New Record’)
4. Click on the button titled “Set Field in Portal”
5. You will notice that the new row does not appear in the portal
6. Click “Save”
7. Now the new row(s) will appear in the portal

Expected result

Data shows in portal before commit

Actual result

Data doesn't show in portal until after commit

Exact text of any error message(s) that appear

No error messages appear

Configuration information

Seems to happen in all environments on all platforms

Workaround

None

Outcomes