11. Calculated fields and expressions

Calculated fields and expressions

Calculated fields transform existing data into new, reusable statements - such as margin, term, age group or status group.

Open Dashboard Designer on the desktop Administration.

Your goal

You can create a calculated field with name, type and expression, bind it in the dashboard and check it with known examples.

Why this is crucial in the dashboard designer

Not every statement required is available as a finished database field. Calculated fields close this gap without changing the X-ERP application or database structure.

Elements and settings at a glance

• Name: Meaningful, unique name of the calculated field.
• Field type: Result type such as text, number, date or true/false.
• Expression Editor: Editor with fields, parameters, constants, functions and operators.
• Field reference: Uses available data source fields.
• Parameter reference: Makes calculations dependent on a dashboard parameter.
• Features: Text, date, logical, mathematical and aggregate functions.
• Comment: Multi-line explanation within complex expressions.
• f symbol: Identifies calculated fields in the field list.

Here's how to do it

1. Define input fields, result and unit technically.
2. Create the calculated field in the data source or binding menu.
3. Select fields from the editor and build the expression step by step.
4. Handle zero values and division by zero consciously.
5. Bind the result and check multiple manually computable data sets.

Exercise

Create a margin, an age range from date, and a conditional status label. Use the actual field names from your X-ERP data source.

Check the result

• Result type and unit are correct.
• Zero, negative and limit values work.
• Calculation is correct with a manual sample.
• Field name describes the technical meaning.
• Expression is understandable for later customizers.

Typical errors and their solutions

• Calculation based on already aggregated values: Check whether you need to calculate per row first or by aggregation.
• Division without zero check: May produce errors or empty visualizations.
• Create identical logic multiple times: Use a common calculated field.

Your result

You expand the analytical language of the dashboard in a controlled and comprehensible way.

Further information / source

Related topics

1. For customizers – customize screens and forms › Dashboard designer › 05. Dimensions, key figures and aggregations
2. For customizers – customize screens and forms › Dashboard designer › 13. Parameters and filter logic
3. For Customizer – Customize screens and forms › Dashboard designer › 15. Conditional formatting and color scheme

Frequently asked questions