Regular Formula Fields vs. Pre-Computed Formula Fields

Regular formula fields are calculated when records are fetched, providing results in real-time. However, with the Is Pre-Computed toggle enabled, formula fields are calculated and stored as data during insertion.

The Is Pre-Computed toggle is for formula expressions that involve cross-object fields. It allows you to control how cross-object field values are handled during the evaluation of a formula expression. Formula expressions are typically evaluated at runtime, meaning their values are calculated when needed. However, when dealing with cross-object fields in a formula expression, the Is Pre-Computed toggle comes into play.

  • If the toggle is enabled, the cross-object fields used in the formula expression are computed before runtime.

  • If the toggle is disabled, the expression fetches the values of cross-object fields at runtime, just before evaluating the formula.

Once a formula expression is defined, you cannot change the Is Pre-Computed flag. If initially set as FALSE, you cannot change it to TRUE later.

Cross-Object Fields in Conga Platform

The Conga Platform allows you to create and use cross-object fields in formula expressions, supporting complex data relationships.

These expressions are enclosed in double braces, like {{Agreement.Account.AccountSource}}.

Creating cross-object formula fields may impact performance compared to standard formula fields.

Creating Cross-Object Formula Fields

When you define a cross-object formula field:

  • The expression within ({{ }}) must start with the current object's name.
  • Each subsequent field within the expression must be a reference or lookup field.
  • The final fields in the expression can only be certain data types: String, Long String, Integer, Double, Decimal, Currency, Boolean, DateTime, Identifier, or Picklist.

Limitations

  • You cannot use a formula field at the leaf level within the formula expression. Instead, include the formula directly within the required formula expression.
  • Expression hierarchies are validated against lookup and reference field metadata when creating formula fields.
  • Functions and other formula features can be used with cross-object formula fields.
  • Cross-object formula fields are evaluated at runtime, similar to regular formula fields, and do not store values persistently.

Here's an example:

Formula1 = Agreement.ContractValue % 10

  • Instead of creating Formula 2 as

    Agreement.TAV * Formula1 

  • Do
    Formula2 = Agreement.TAV * (Agreement.ContractValue % 10)