Hi all,
I noticed this behaviour and simply wanted to report it because I am not sure if this is expected behaviour or not.
When creating a record in an app if the first field on top is not populated some calculation fields won’t display. I saw that calculation fields used as section breaks (like these) are not working. This both happens if the record is created manually and/or automatically. This is still the case if another field is modified but not the first one on top.
It is important to note that other calculation fields are visible and correctly displayed without following this pattern (so from the very beginning). And also the mentioned “problem/expected behaviour” is not always happening. Sometimes randomly this is not happening even if the first field is not populated and/or happening initially but then changing some time after this. Maybe there is some other hidden pattern that can explain this apparent randomness in these cases.
I noticed this as well. Sometimes, we build a related items table and in the presence of no related items, the calc field shows as blank rather than reading our final “else if” statement. We would expect the calc field to produce a full calculation upon item creation regardless of what tokens are used.
thank you for sharing your issue. Currently, by design calculations will only calculate for a new record when the referenced fields (inside the calculation script) have a value, or at least had one at some point in time and were cleared. Is it possible, that in your scenario the “first field” is exactly the field that you are reaching to with the calculations in question?
For headlines, you could now reach for the new “Record ID” static token instead, that would yield a calculation for created records in any case. That token is new, announcement is yet to come soon.
