Skip 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.

Access Priveleges - Field Level

Featured Replies

I have an interesting problem. In the implementation of an external function (plugin) I need the access privileges to be reevaluated on each field change within a layout. Specifically, I am using EventScript for this task.

Here's the gotcha, in the example file provided by the developer, FileMaker reevaluates the record Level access priveleges after each field change. In this way, the attached script runs every time a field is entered. It works, I totally demolished the example file to prove that my functions work in it also, and that's all well and good.

Except! In my version of FMP7 (current version) I attempted to duplicate the action in two different files that I created and there is a failure in the record access validation. In my files, the record level access only calculates ONCE on entry into the record (barring a forced record commit which adds problems to the bin on this one). So, does anybody know why in one file a record would validate the access privileges on each field change whereas on another file it validates only on record entry?

Possibility that I'm ddoing something wrong (however obscure that thing may be) : It's possible.

I'm wondering if this is a file level difference between FMP and FMD...

  • Author

Since nobody finds this very interesting, I'll post the answer also. I emailed the dev with the problem in detail and with his reply I realized that my problem was also the answer to this question. Since FM only evaluates a record once upon entry, the layout used in the example uses all globals except for ONE data entry field. Therefore if one tabs from field to field, the record commits and then reevaluates when the NON global field is entered again by any method. In this way the OnEntry event can be simulated.

  • 3 weeks later...

Since nobody finds this very interesting, I'll post the answer also. I emailed the dev with the problem in detail and with his reply I realized that my problem was also the answer to this question. Since FM only evaluates a record once upon entry, the layout used in the example uses all globals except for ONE data entry field. Therefore if one tabs from field to field, the record commits and then reevaluates when the NON global field is entered again by any method. In this way the OnEntry event can be simulated.

So, are you saying that when you tab from a global field into another global field the record is committed or are you saying that if you tab from a global field into a Non global field the record is commited, or both?

Create an account or sign in to comment

Important Information

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

Account

Navigation

Search

Search

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.