Performance
SUM and LOOKUP in one reference
Don't combine SUM and LOOKUP in one bracket: Anaplan then maps cell by cell, one of the slowest patterns in the engine, so split it into two line items.
What MaxCheck detects
A bracket that combines SUM and LOOKUP, e.g. X[SUM: A, LOOKUP: B].
Why it hurts
Anaplan evaluates the combined mapping cell by cell, which is one of the slowest patterns in the engine.
Example
Taken from the rule's own test cases: formulas it must flag, and formulas it must not.
ErrorFlags this(sum then lookup)
Sales.Value[SUM: Map.Region, LOOKUP: Map.Month]
Fine (sum and lookup in separate brackets)
A[SUM: Map.Region] + B[LOOKUP: Map.Month]
How to fix
Split it: SUM into an intermediate line item first, then LOOKUP from that line item (or the other way round).
- Severity
- ErrorCounts toward the area score.
- Area
- Performance
- Runs in
- Basic and full check
- Rule ID
- P_SUMLOOKUP
- Version
- Rule 1.0.0, rule set 1.4.0
- Planual
- 2.02-08 Avoid combining SUM and LOOKUPon Anaplan's Formulas page
Does your model do this?
Upload the line-items blueprint. This rule runs in the basic check, in your browser, with no email.