Skip to main content

New Features and Improvements

AtScale contains the following new features and improvements.

Data warehouse security​

You can now configure which users/groups have access to each of your data warehouses. These permissions apply throughout AtScale: If a user doesn’t have access to a data warehouse, they can’t view it on the Data Warehouses page, view its data in the Data Sources panel, or access the catalogs and models based on its data within AtScale.

To support this functionality, the Add/Edit Data Warehouse panels contain a new Access Controls field, where you can specify the users and groups that have access to the data warehouse.

note

If you upgrade to C2024.10.0, all existing data warehouses are accessible by all users. If you wish to change this, you can do so from the Data Warehouses page.

For more information, see About Data Warehouse Security.

ATSCALE-22163

Global and model settings​

In this release, AtScale introduces a new system for managing engine settings. Additionally, AtScale now supports model-level settings, enabling you to apply specific configurations to individual models. Both sets of settings are managed via Git.

Engine settings, which are now called global settings, are managed in a dedicated Git repository. This repository contains a file called global_settings.yml, which defines all of the global configuration settings applied to your system.

Model settings are managed at the catalog repository level, in a file called model_settings.yml. This file is stored in the root level of the repository and defines the configuration settings applied to the individual models in the catalog.

note

The original Settings page is currently still available. However, AtScale recommends that you begin manually transitioning your existing engine settings to a global settings file after upgrading to C2024.10.0. For more information, see Upgrade Requirements.

These changes enhance CI/CD automation with AtScale, as they enable you to have the same global and model settings configured across different environments. Because they're stored in Git, they don’t need to be set separately for each environment.

For more information on configuring global settings, see Configuring Global Settings. For more information on configuring model settings, see Configuring Model Settings.

ATSCALE-21925

New Query Mapping option​

The Query Mapping configuration for data warehouse connections contains a new option called Aggregate Build Queries. Previously, aggregate build queries were part of the System Queries option.

This change enables you to assign aggregate build queries to a separate data warehouse connection that has more compute power. All other system queries (i.e., aggregate maintenance builds and stat queries) still fall under the System Queries option.

For more information, see Configuring Query Mapping.

ATSCALE-21920

Distinct Sum aggregation for non-additive metrics​

You can now create non-additive metrics that use Distinct Sum aggregation, which provides the sum of distinct values for integers.

To support this functionality, the Aggregation Type field in the Edit Metric panel contains a new option called Distinct Sum. Additionally, the calculation_method property in SML metric files now supports the sum distinct value.

For more information on working with distinct sum metrics, see Non-Additive Metrics. For more information on creating non-additive metrics, see Add Additive or Non-Additive Metrics. For more information on defining non-additive metrics in SML, refer to the SML Object Documentation on GitHub.

ATSCALE-21703

Semi-additive metrics in Design Center​

You can now create semi-additive metrics via the Edit Metric panel in Design Center. Previously, semi-additive metrics could only be defined via SML.

To support this functionality, the Edit Metric panel now contains a Semi-Additive field, where you can define the non-additive behavior of the semi-additive metric (First Non-Empty or Last Non-Empty), as well as the specific dimensional attributes this behavior applies to.

For more information on creating semi-additive metrics in Design Center, see Add Semi-Additive Metrics.

ATSCALE-19052

Updated SML properties for calculation groups​

The following changes have been made to the calculation_groups property in SML dimension files:

  • The name property has been changed to unique_name.
  • The description property is now optional.
  • calculation_groups now supports the label property. This property is required.

Additionally, the following changes have been made to the calculation_groups > calculated_members property:

  • The name property has been changed to unique_name.
  • The description property is now optional.
note

After upgrading to C2024.10.0, you need to update any existing calculation groups in your dimension files to reflect these changes. For more information, see Upgrade Requirements.

For more information on defining calculation groups in SML, refer to the SML Object Documentation on GitHub.

ATSCALE-22943

Support for Hex metadata calls​

AtScale now supports metadata calls from Hex, enabling queries to be executed from the Hex data browser.

ATSCALE-19124

Drag-and-drop creation of degenerate dimensions​

AtScale now provides a more streamlined method for creating degenerate dimensions: Simply click and drag a column from your model’s fact dataset directly onto the Canvas. The degenerate dimension is automatically created and linked to the fact dataset.

For more information, see Add a Degenerate Dimension.

ATSCALE-21643