AnsweredAssumed Answered

Calculation fields using Custom Function do not re-evalute when custom function is updated

Question asked by philmodjunk on Jul 22, 2010
Latest reply on Jan 2, 2015 by LaRetta_1

Summary

Calculation fields using Custom Function do not re-evalute when custom function is updated

Product

FileMaker Pro

Version

11.0v2

Operating system version

Windows XP SP3

Description of the issue

Stored calculation fields do not automatically re-evealute if a custom function they reference is updated nor is any mention of this made in the filemaker help system released with filemaker 11.02.

At the very least, a note identifying this issue and describing a work around should be made in the help system.

Steps to reproduce the problem

Define a simple custom function:  AppendA ( t ) as t & "A".
Define a calculation field as AppendA ( fieldname ) set to return text.
Leave Manage | Database and redefine AppendA to be t & "Aa".
Examine calculation field.

Expected result

Fields should now all end in Aa

Actual result

Fields still end in A

Configuration information

This was originally discovered when implementing a fairly sophisticated recursive text parsing function and then replicated with the simple function posted here.

Workaround

Search a database design report to locate each calculation field where the function is used and modify the expression in a manner that does not affect the final value such as adding + 0 or & "" to it. This forces the field to re-calculate when you exit Manage | Database.

A simple improvement, which I will put in the suggestion box, is to add a button in manage | custom functions that forces a recalculation of the fields in the current file.

Outcomes