Skip to content

Casabase Cube 4.1.1

Release: 4.1.1
Release type: Patch
Released: September 7, 2026
Platform: Snowflake Native App

Casabase Cube 4.1.1 introduces asymmetric reports, a Cortex Code (CoCo) skill for AI-assisted cube development, in-app cube creation limits based on plan and licensing, and improved numerical precision for fact table measures.

Queries can now return specific coordinate combinations instead of the full cross product of selected members.

Pass an __ASYMMETRIC key in the POV to restrict output to an authored set of member combinations. For example, a report can return (Actual, Jan), (Budget, Feb), and (Variance, Q1) instead of every Scenario × Period combination.

Each cell is calculated using the same query logic. The asymmetric definition only restricts the output grid.

Example:

{
"SCENARIO": [{"children": "SCENARIO"}],
"PERIOD": [{"children": "Q1"}],
"__ASYMMETRIC": {
"dimensions": ["SCENARIO", "PERIOD"],
"combinations": [
["Actual", "Jan"],
["Budget", "Feb"],
["Variance", "Q1"]
]
}
}

Asymmetric reports are not supported with alias tables or when the authored combinations reference calculated members.

Casabase Cube can now generate a Cortex Code skill file tailored to the installed application.

The skill teaches CoCo about Casabase Cube procedures, POV syntax, and formula language, enabling AI-assisted cube development directly in Snowsight. CoCo can use this context to help write queries and manage dimensions.

The skill is available from the Help Center or can be generated using:

CALL CUBE.GENERATE_COCO_SKILL('<cube_name>');

Cube creation limits are now enforced within Casabase Cube.

To view the current plan, cube limit, and usage, run:

CALL CUBE.GET_PLAN_INFO();

The fact table measure column has been upgraded to:

NUMBER(38,10)

Existing measure columns using FLOAT are automatically retyped during the upgrade.

This change eliminates floating-point rounding artifacts in large aggregations while preserving existing data.

The migration runs automatically and re-applies the physical sort order after the measure column is retyped.

No manual action is required.

No manual steps are required for version 4.1.1. All required migrations run automatically.

The physical sort is re-applied after the measure column is retyped to NUMBER(38,10).

For very large fact tables, this process may extend the time required to complete the upgrade.

Queries continue to return correct results throughout the process.