Creating computed columns
Computed columns derive new transaction values from fields you already import. They can be used in tables, filters, commission rules, Metric Definitions, targets, and reports without requiring another source file or custom code.
For: Authorised Admin and Finance users
Before you begin
Section titled “Before you begin”Prepare:
- A clear name and business purpose
- The imported fields used by the calculation
- The required output type: Number, Date, or Text
- Representative normal, empty, and boundary-value transactions
- A manually calculated expected result
Create a computed column
Section titled “Create a computed column”- Open Settings > Computed Columns.
- Create a computed column and enter its name and description.
- Choose the output type: Number, Date, or Text.
- Enter a formula. Reference transaction fields using braces, such as
{amount},{region}, or{transaction_date}. - Review the live preview against representative transactions.
- Resolve any validation error before saving.
- Save the computed column.
- Verify its value on imported transactions and in every downstream metric, rule, target, filter, or report that will use it.
Formula examples
Section titled “Formula examples”| Goal | Example formula |
|---|---|
| Convert a deal value | {amount} / 1.2 |
| Flag a large deal | IF({amount} >= 1000, "High", "Low") |
| Calculate days to close | DATEDIFF(day, {transaction_date}, {close_date}) |
| Build a combined label | CONCAT({client_name}, " - ", {region}) |
| Use a fallback amount | COALESCE({amount2}, {amount}) |
Supported functions include IF, ROUND, ABS, FLOOR, CEIL, DATEDIFF, CONCAT, LOWER, UPPER, COALESCE, and NULLIF, together with arithmetic and comparison operators.
How computed values are updated
Section titled “How computed values are updated”Each value is stored on its transaction using the selected output type, so it can be sorted, filtered, and aggregated like an imported field. Perslace recalculates computed columns for new imports and source syncs so dependent views and calculations use the current value.
Expected result
Section titled “Expected result”The computed column returns the expected typed value for representative transactions and is available in the intended filters, rules, metrics, targets, and reports.
Important notes
Section titled “Important notes”- A computed column does not change the original imported value.
- Changes can affect every metric, scheme rule, target, filter, and report that uses the column.
- Test empty values, zero, negative amounts, date boundaries, regional formats, and unexpected text where relevant.
- Record the formula, test cases, expected results, reviewer, and approval before using it in production calculations.
Troubleshooting
Section titled “Troubleshooting”The formula is rejected
Section titled “The formula is rejected”Check field names, braces, quotation marks, function arguments, and the selected output type. Use only supported functions and operators.
The preview is empty
Section titled “The preview is empty”Confirm that the referenced fields exist on the sample transactions and contain values. Use COALESCE when an approved fallback is required.
The result has the wrong type
Section titled “The result has the wrong type”Confirm that the output type matches the formula. Do not return text such as "High" from a column configured as Number.
Existing transactions show an unexpected value
Section titled “Existing transactions show an unexpected value”Compare the formula with the stored imported fields, then review the latest import or sync. Test the same record manually before changing the formula.
Related articles
Section titled “Related articles”- Importing transaction data
- Creating a Metric Definition
- Understanding commission calculations
- Reconciling dashboard, report, and imported totals
Last updated: August 2026