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.

What's the worth of «Go to Field []» ?

Featured Replies

Hi,

 

I'm not very familiar with the user interface possibilities that FileMaker offers when it comes down to navigating the user to the next field that he needs to fill in for a specific task. Imagine the following scenario:

 

A user types in a value, say «iPad», into a field «Table::Item».

An onObjectSave script checks this value, and sets the next field (tab order) «Table::Price» to «$399».

Then fills a couple of other fields that are further down the tab order in the current layout, to spare some time for the user.

Then, after all Set Fields are done, onObjectSave wants to allow the user to be able to directly enter the next logical value for him. So it ends with a «Go To Field [Table::Color]» and makes this field active.

 

Sound good, but this doesn't work as expected. FileMaker remembers that the user closed his field input in Table::Item with a tab key and now makes Table::Color inactive, even though Go To Field was specifically specified. FileMaker now goes to the previously (way back in Table::Item) next field and makes it active, which is Table::Price, thus making more work for the user.

 

In this scenario, Go To Field [] is completely worthless. Or am I overlooking something? What do you do in such a scenario?

 

Thanks a lot for any hints.

 

Gary

 

If you want your script to cancel the triggering event (in this case the tab keypress), then your script must exit with a false result. Otherwise the tab keypress will be executed immediately following the script.

Your expectation may be off.  The onSave event happens before the onExit, the onExit is triggered by the tab so that that one is the last in the queue of events and when it exits the field it will tab to the next field in the tab order.

 

As comment indicates: cancel the original event or handle this through the onExit event.

  • 2 weeks later...
  • Author

Makes sense, I didn't know that onExit is triggered by the tab (and probably by the enter key or mouse click somewhere else and maybe a bunch of other stuff).

 

So, when I use Go to Field [] in any previous Script Trigger, I just return a False in onExit. Cool.

 

Thanks a lot,

 

Gary

Another possibility is to change the tab order in the layout...

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.