Jump to content
View in the app

A better way to browse. Learn more.
FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Bug: Setting a Field in a Portal using a [Full Access] Script

alecgregory
in Layouts

Featured Replies

I think I've found a bug related to setting fields in related records using scripts.
 
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:
A refresh window (flush cached join results) script step does not help
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.soliantconsulting.com/blog/2012/08/easy-filemaker-modal-edit-dialogs-full-rollback-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.
 
Has anyone encountered this before and / or have any ideas how to solve it without breaking the pattern? It's pretty easily reproducible so I fear it's a FileMaker bug.
 
The steps to reproduce the bug are below, and an example file is attached.
 
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
  6. Click “Save”
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”
  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

full-access-bug.zip

Create an account or sign in to comment

https://fmforums.com/topic/88697-bug-setting-a-field-in-a-portal-using-a-full-access-script/
Go to topic listing

Important Information

By using this site, you agree to our Terms of Use.

I accept

Configure browser push notifications
Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.