Stored vs. unstored calculations: performance impact
ExpertUnderstand when FileMaker stores calculation results, when it must recalculate on access, and how to design fields for the performance profile you need.
What you'll learn
- When FileMaker forces a calculation to be unstored
- How stored calculations affect find and sort performance
- How to make a time-sensitive calculation behave correctly
A stored calculation writes its result to disk like a regular field, enabling fast finds and indexed sorts. An unstored calculation is recomputed every time it is displayed. The choice between stored and unstored affects find speed, server load, and data currency — understanding the tradeoffs is critical for large solutions.
When calculations must be unstored
FileMaker automatically makes a calculation unstored when it references: a related field, a global field, a Summary field, Get() functions that return runtime values (Get(CurrentDate), Get(AccountName), etc.), or another unstored calculation. If any ingredient is not deterministic, the result cannot be stored.
Sign in to track your progress and pick up where you left off.
Sign in to FM Dojo