[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 423
  • Last Modified:

FM - Problem with default Find field.

When first going into Find Mode, the cursor no longer defaults to the field set as Tab #1.  In fact, no field is selected since when I try to enter text, I obtain the error "Before typing, press Tab or click in a field...."  It is almost as if it does a commit record on entry into Find Mode.  I've checked any script triggers, but none have the Find box checked, so do not set off in Find mode.  Any suggestions.  Note:  If I press Ctrl F again, then the cursor does go to this field.
0
rvfowler2
Asked:
rvfowler2
1 Solution
 
Will LovingPresidentCommented:
Well, I believe FM does do a Commit Record when you enter Find Mode, however it should go to the first field in the tab order. Also, the fact that a script trigger is not set to run in Find mode doesn't mean that it won't run if you're starting in Browse mode. I would think that something is happening that is causing it to not enter the first field.

Does it do this on every layout? (Perhaps on one with no script triggers…or in a similar layout in a test file?)

Have you over-ridden the default Find Mode menu item (and shortcut) to use a Find script that you've developed instead, for instance to take the user to a special Find layout?

Are you using OnModeEnter or OnModeExit script triggers?
0
 
rvfowler2Author Commented:
Thanks, you helped me find it.  Thought I had checked all Script Triggers, but missed one, OnModeEnter, that had the Find box checked.  Works now.
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now