Create a Record Level Formula Field

Create a calculated field at the Record Level so the expression is evaluated per row in the selected Data Store. Record-level fields can be used like any other field in Views (filtering, grouping, cha

Access

1. Open the report’s Design page (Design canvas).

2. Click Create Calculated Field (right-hand toolbar).

   • You are redirected to the Create Calculated Field window.

   • The Formula tab opens by default.

Configure the Formula Field

In the FORMULA tab, set the following:

• Formula Name Enter a title for the calculated field (e.g., Upper_Customer_Name, Discounted_Price).

• Level Choose where the calculation is applied:

  • Record Level (per row; evaluated before aggregation)

  • Summary Level (post-aggregation; evaluated on grouped/aggregated results)

• Type Decide how the platform should classify the new field:

  • Dimension (categorical/text/date)

  • Measure (numeric)

• Fields Lists all columns from the selected Data Store. Click/tap to insert a field into the expression.

• Functions Lists available functions (text, numeric, date/time, conditional, etc.). Click to insert into the expression.

• Formula Expression Build the expression by combining Fields, Functions, and operators.

Note: You can also insert operators directly to complete expressions for Measure columns.

• When finished, click Save to create the calculated field.

• A notification confirms the Formula Field has been created and added to the Data Store.

Example: Create and Use the Field in a View

1. After saving, locate the formula column in the field list.

2. Select the formula column so it appears in the top panel (New UI) or drag it onto the canvas (Old UI).

3. Click GO (New UI) or place fields to render the View.

   • Example outcome: If you used an uppercase function (e.g., UPPER(Customer_Name)), the column data is displayed in UPPER CASE.

4. Click Save View to persist the View to the report.

5. A notification appears; you are redirected to the final report screen with the new View added.

Notes & Best Practices

• Record vs. Summary:

  • Use Record Level for per-row transformations (e.g., UPPER(Name), Price * 1.18).

  • Use Summary Level for post-aggregation logic (e.g., ratios of aggregated measures).

• Type selection matters:

  • Text/date outputs should be Dimension; numeric outputs should be Measure for correct chart behavior.

• Validation: Prefer clear names (no spaces or use underscores). If a Validate button is available in your tenant, run it before Save.

• Reusability: Once created, the field is available in the Data Store for all Views in the report and for other users who have access to the same Data Store.

• Performance: Complex expressions on very large datasets may affect render time—optimize where possible.

Troubleshooting

• Field not visible: Ensure you saved the formula and are viewing the correct Data Store. Refresh the field list if needed.

• Wrong bucket/type: If charts don’t behave as expected, confirm the Type (Dimension vs. Measure) matches the expression output.

• Unexpected results: Reopen the Formula tab and verify operator precedence and function