Calculations based on related data will not refresh when the related data change, just because they change. (This is done for performance reasons.) To force it to change, you need a "trigger" - a field in the local table that changes and thus causes the calculation to be re-evaluated. So for example, you might do something like this:
Let ( [
trigger = modifyTS
where modifyTS is a modification timestamp field in the current table.
P. S. You can check out "Shaking the Dependency Tree" (Google it) for an excellent presentation on how FileMaker evaluates dependencies.
+1 for the "Shaking the Dependency Tree" reference. A hugely valuable resource!
Another point is that the auto enter will only populate at the time the record is created, and not thereafter without some sort of refresh mechanism. You should be able to enter it by script if necessary.
"Refresh mechanism" being defined as "local predicate changes or script or user enters new data".
(You're right; just wanted to clarify.)
THIS forum can be searched for Darren's preso:
DevCon 2012 Session Recording: Shaking the Dependency Tree
About his article:
Darren's demo from Pause-on-error:
Spot on Mike. That's why you are a 15 and I am a mere 8!!
Meh. I've just been here longer.