Casabase Cube 4.2.0
Release: 4.2.0
Release type: Minor
Released: October 30, 2026
Platform: Snowflake Native App
Casabase Cube 4.2.0 introduces a new query engine delivering approximately 2.5× faster queries overall, stricter validation of calculated members and POV selections, and automatic cube preparation.
New Query Engine
Section titled “New Query Engine”Faster Queries
Section titled “Faster Queries”QUERY_CUBE, QUERY_CUBE_PIVOT_JSON, and QUERY_CUBE_BUILD now use a new query engine, delivering approximately 2.5× faster queries overall. The largest gains occur on cubes with many calculated members.
Procedure names, arguments, and result columns are unchanged.
Behavior Changes
Section titled “Behavior Changes”Unsupported Calculated Members Return Errors
Section titled “Unsupported Calculated Members Return Errors”When a calculated member cannot be evaluated exactly, the query now returns an error identifying the member and the reason, along with a HOW TO FIX line. Previously, the query might return a generic error message.
Queries on stored members and supported calculated members are unaffected.
Missing Substitution Variables Stop Queries
Section titled “Missing Substitution Variables Stop Queries”A formula referencing a substitution variable without an active value in CONFIG.CUBE_VARS now causes the query to fail. This includes references such as &CurrYr and [CUBE_VAR=CurrYr].
This is particularly relevant to cubes imported from Essbase or PBCS outlines when their substitution variables have not been configured. Define and activate the missing variable using:
CALL CUBE.MANAGE_CUBE_VAR('<CUBE>', 'UPSERT', 'CurrYr', 'FY25', TRUE, NULL);Invalid POV Entries Return Errors
Section titled “Invalid POV Entries Return Errors”Point of View (POV) errors that previously returned zero rows now produce descriptive errors. These include unknown dimensions, members, or operators; empty member lists; and operator objects containing multiple keys.
Errors identify the invalid entry and suggest a correction, such as checking capitalization, using the underlying member name instead of an alias, or selecting a member from the correct dimension.
Agent Saved Query Execution
Section titled “Agent Saved Query Execution”When an Agent runs a saved query that fails, the result now reports status: 'ERROR' with the error message instead of status: 'OK' with an error row.