Calculated fields can now use nested linked fields to pull in data from an entity linked to your first linked field, letting you query your data one level deeper.
For example, on a Task, you could already reach a linked Shot's status with {entity.Shot.sg_status_list}. Now you can also reach that Shot's linked Sequence's status, with {entity.Shot.sg_sequence.Sequence.sg_status_list}.

Because nested linked fields add an extra lookup, a non-blocking warning appears in the field configuration dialogue to help you anticipate a possible impact on page load times as your data grows. Analyze Page Performance flags calculated fields that use a nested linked field, so you can spot them later if a page slows down.
In addition, available Linked Fields picker now shows nested, collapsible groups for linked fields.

Existing linked fields are unaffected by this change.
To learn more about calculated fields, check out our documentation here.
8.87
July 2026