AnsweredAssumed Answered

Problems with Commit[ment]

Question asked by ChuckPelto on Feb 20, 2009
Latest reply on Mar 9, 2009 by TSGal

Summary

Problems with Commit[ment]

Description of the issue

TO: WhomeverRE: FMP10a Has Difficulty with Commit[ment]  FileMaker Product(s) involved: FMP10aOperating System(s) involved: Mac OS X 10.5.6Detailed description of the issue: Commit does not 'commit' records, i.e., exit, when used in a script that is called on by the new Script Trigger functionality and involves changes in a Custom Function field.Exact steps to reproduce the issue:[1] Create a field that uses Script Trigger to call upon a ScriptMaker script when data in a pop-up menu field is changed.[2] Have a custome function field triggered by a change in the pop-up menu field of that same table.[3] In the ScriptMaker script, put a Commit call as the last item.[4] In a related table create a field that is supposed to be modified based on values in the first table's pop-up menu field, when it changes.[5] Go into browse mode and change the value in the pop-up menu.Expected Result: That the record will be exited by the Commit call.Actual Result: The record is not exited by the commit call. Fields are still in dotted outilne. The data in the related table record that depends on the value in the pop-up menu field and custom function does not change.Exact text of any error message(s) that appeared: None.Any additional configuration information/troubleshooting that is relevant to the issue:Might be something to do with the call to a custom function that does a complex calc which populates another field in the pop-up menu field's table, based on what changes in the pop-up menu. It seems to be a possibility.The pop-up menu activates a calc field in the same table to go after a custom function. The custom function returns information based on the value selected in the pop-up menu. That information is used by the second table to update records within itself.But no action is taken until I physically click on a blank area, i.e., someplace without a field, in the record where the pop-up menu has been changed.I've run a test and if I use the Commit function in a script that is activated by the Script Trigger function and the Custom Function field is NOT called upon or modified, the Commit function acts as advertised. The record is exited.Any workarounds that you have found: Nothing yet......working on it.

Outcomes