A Calculated Field is a virtual or derived field created dynamically at runtime using one or more existing fields through a formula, expression, or data transformation.

• Unlike physical columns in a database, calculated fields are not stored permanently — they are evaluated on the fly during query execution or data visualization.
• Calculated fields allow you to extend your dataset without modifying the underlying schema.

Calculated fields are essential for enabling dynamic analytics, reusable logic, and flexible data transformation.

Calculated fields provide several benefits:

• Create new insights without altering the original schema.
• Combine or transform existing fields for reporting and dashboards.
• Implement reusable logic across multiple queries.
• Improve flexibility and reduce dependency on the database.

Common scenarios for calculated fields include:

• Concatenating multiple fields (e.g., store_name + city).
• Performing string transformations (uppercase, lowercase, substring).
• Adding or subtracting date intervals.
• Applying conditional logic to generate values based on filters.
• Creating dynamic discounts, taxes, or derived KPIs.

Each flow can be applied individually or combined to create more complex calculations.

• Use meaningful calculated field names.
• Keep flows simple and modular.
• Test calculated fields using the Test Calculated Field API.
• Avoid unnecessary nested flows to maintain performance.
• Document each calculated field clearly for future maintenance.