AnsweredAssumed Answered

OnObjectModify with Drop-down object is fired too late

Question asked by Fred(CH) on Sep 4, 2013
Latest reply on Dec 4, 2013 by Fred(CH)

Summary

OnObjectModify with Drop-down object is fired too late

Product

FileMaker Pro

Version

12.0v4 (and older)

Operating system version

Mac OS X

Description of the issue

When the OnObjectModify Script Trigger is fired by drop-down lists and drop-down calendar, the triggered script can be performed AFTER the object is leaved (exited), with, of course, unpredictable effects.

This issue only affects drop-down lists and drop-down calendar objects.

Steps to reproduce the problem

STEP 1
Create a file that contain one text field, one populated custom value list and one layout.
STEP 2
Define the triggered script with for instance a custom dialog box
STEP 3
Define your layout with multiple occurrences of your field. First as a simple edit box and second as a drop-down list.
STEP 4
Attach the triggered script to all the field's occurrences
STEP 5
Test your database and be careful what is the active field when your script is triggered after you entered data with the drop-down list

Expected result

The script must be triggered after modifying but BEFORE exiting the object

Actual result

The script is triggered AFTER exiting the object

Exact text of any error message(s) that appear

None

Configuration information

Mac OS X 10.8.4

Workaround

Good news... there is one :

Create another script with... hum... maybe only one comment, and trigger this with OnObjectValidation event...

And the trick is done !

Outcomes