Troubleshooting guide

Empty output

Values are missing where you expect data. If you use FILTER, confirm the dimension names, level values, and the intended level all match exactly; and check whether one input is missing values where the other is defined.

Wrong shape

The result is too aggregated or too granular. Too aggregated: check whether + or - collapsed the inputs to their common dimensions, and make it explicit with ROLLUP or ROLLUP_TO. Too granular: check whether *, /, or EXPAND added detail.

Wrong numbers

The shape is right but the values are off. Check constants such as + 1 (use ADDEACH for element-wise adjustments), whether assumptions or scenarios changed the result upstream (consider BASELINE or NONSIM), and whether operator order matters.

Define the expected result

Note one specific intersection you expect to be correct and the expected output shape, including dimensions and levels. This gives you something to check against.

Fix syntax and validation errors first

Resolve any validation or syntax error the editor flags before you touch the formula logic, then re-check in Data Preview.

Simplify by bisection

Start from a single node reference such as 'Sales', then add the parts back one at a time. Move large sub-expressions into helper nodes so you can inspect them.

Spot-check the result

Confirm at least two representative intersections, checking both the shape and the values, so you don’t fix one case while breaking another.

Clean up

Once the result is correct, split complex logic into helper nodes where it helps and add short # comments to clarify intent.