Skip to main content

New Features and Improvements

AtScale contains the following new features and improvements.

Support for Amazon Redshift data warehouses​

AtScale now supports Amazon Redshift data warehouses. For instructions on adding and configuring them, see Adding Amazon Redshift Data Warehouses.

ATSCALE-23260

Support for Microsoft Azure DevOps​

AtScale now supports Azure DevOps repositories. For instructions on connecting to Azure DevOps, see Managing Git Repositories in AtScale and Connecting to Git.

ATSCALE-24386

New MDX functions​

AtScale now supports the following MDX functions: Members, Except, Intersect, Union. These can be used together to create churn rate functions. For more information on each of these, see the MDX Reference.

ATSCALE-23338

Configure default members to only be applied when specified in a query​

You can now configure default hierarchical members to only be applied when they are explicitly included in queries. This enables you to selectively apply default constraints for meta dimensions (calculation groups or similar dimensions) that represent calculations or parameters, rather than data.

To support this functionality, the Hierarchy properties panel contains a new Apply only when in Query checkbox, which appears when you enable the Use default member literal expression option on the hierarchy. Additionally, SML dimension files now support the apply_only_when_in_query property.

For more information, see About Default Hierarchical Members, Add a Normal Dimension, and the SML Object Documentation on GitHub.

ATSCALE-23650

Calculation groups and calculated members in Design Center​

You can now create calculation groups and calculated members within Design Center. Previously, calculation groups could only be defined via SML.

To support this functionality, the Dimension properties panel contains a new Calculation Groups section, where you can view, create, and manage the dimension's calculation groups and calculated members.

For more information, see Add Calculation Groups and Calculated Members.

ATSCALE-19184

Reordering dimension hierarchies in Design Center​

You can now change the order of hierarchies within dimensions by dragging and dropping them within the Dimension properties panel. This introduces the concept of a default hierarchy within a dimension, which can be referenced in calculated members via the CurrentMember MDX function.

For more information, see Referencing Calculation Groups in Calculations.

ATSCALE-23840

Support for referencing calculation groups and calculated members in calculations​

Metrics inside of calculations can now be scoped by the member range defined in a calculation group. This is typically a quantity of time like Month-to-Date or Equivalent Period in the Last Year.

To make this capability as reusable as possible, you are no longer required to reference a specific hierarchy in your calculation group code. For ParallelPeriods, you no longer need to reference a specific hierarchy level by name (e.g. "Year Level"), and can instead use metadata types, such as TimeYears.

Additionally, you can also include references to calculated members within calculations. This enables the isolated evaluation and reuse of individual calculation group expressions. For example, the calculation group "TimeCalc" MTD calculated member can be individually referenced with different metrics to compute the Month-To-Date Sales/Customer calculation: ([DateCustom].[TimeCalcs].[MTD], [Measures].[SalesTotal]) / ([DateCustom].[TimeCalcs].[MTD], [Measures].[SaleCount])

For more information, see Referencing Calculation Groups in Calculations.

ATSCALE-22059, ATSCALE-23619

Distinct count aggregates at non-leaf levels​

If you have enabled system-generated distinct count aggregates by setting the aggregates.create.allowExactDistinctCountMeasures.enabled model-level setting to true, then AtScale now creates distinct count aggregates at the level specified in the query, rather than at the leaf level of the hierarchy. This ensures that distinct count aggregates are used by the query planner.

This functionality is enabled by default, and can be controlled via the new aggregates.create.withDistinctCounts.queryLevel.enabled model-level setting. For more information, see Aggregate Creation Settings.

ATSCALE-24195

Cancel running queries​

You can now cancel running queries from the Queries page. To do this, hover over a running query in the table and click the Cancel button that appears.

For more information on the Queries page, see Using the Queries Page.

ATSCALE-23110

SML: use_input_measure_format renamed to use_input_metric_format​

The use_input_measure_format SML property (under calculated_members in dimension files) has been renamed to use_input_metric_format. After upgrading to C2025.1.0, you should update your dimension files to reflect these changes.

For more information on dimension files, see the AtScale SML Object Documentation on GitHub.

ATSCALE-24226

New parameters available in the AtScale Helm subcharts​

The following parameters are now available in the atscale-entitlement, atscale-api, atscale-engine, and atscale-web subcharts: nodeSelector, topologySpreadConstraints, toleration, and affinity.

New database timeout parameter​

The database timeout parameter waitForDB is now available in the atscale-entitlement subchart. For example, waitForDB: 60 will cause atscale-entitlement pods to fail only if the PostgreSQL database is unavailable for over 60 seconds.