Skip to main content

New Features and Improvements

AtScale contains the following new features and improvements.

SML now versioned​

AtScale's Semantic Modeling Language (SML) is now versioned: New properties and other changes to SML are rolled out as new versions of the language.

Additionally, when a new version of SML is released, Design Center now notifies you of any changes that need to be made to your models to upgrade. These appear as warnings and other messages in the Model Validator. You can upgrade your files by clicking the Fix Error button for each message.

For information on the latest version of SML, refer to the AtScale SML Object Documentation on GitHub.

ATSCALE-26546

Configure BI tools from the Settings page​

The pages for managing connections to Microsoft Power BI, Tableau Server, and Looker have moved from the Control Center to the Settings page in Design Center. For more information, see Using Power BI Service with Token-Based Authentication, Configuring Connections to Tableau Server, and Creating a Looker Connection.

ATSCALE-23237, ATSCALE-23236, ATSCALE-25700

Deploy to Looker from the Deploy panel​

You can now deploy catalogs to Looker from the Deploy panel. The panel contains a new Looker toggle in the Deploying To section, where you can select the specific Looker server definition and Git branch to deploy to. For more information, see Deploying a Catalog.

ATSCALE-21280

New realm roles for managing Tableau Server definitions​

The Identity Broker contains two new realm roles: tableau_admin and tableau_manage. Users with these roles can add, edit, and delete Tableau Server definitions. For more information, see Identity Broker Default Roles.

ATSCALE-25715

New access controls for Tableau Server definitions​

You can now control which users and groups can deploy to each of your Tableau Server definitions. To support this functionality, the Add Tableau Server Definition panel contains a new Access Controls field, where you can specify the users/groups that have access to that definition.

For more information, see Configuring Connections to Tableau Server.

ATSCALE-25715

Changes to realm role permissions​

The following permission changes have been made to the Identity Broker's default realm roles:

  • Users with the application_admin role now have read-only access to the Identity Broker. Previously, this role did not grant any access to the Identity Broker.
  • Users with the aggregates_manage role can now access the User Settings tab of the Settings page, allowing them to enable/disable the different aggregate modes available on the tab (e.g., Training Mode).

For more information, see Identity Broker Default Roles.

ATSCALE-26811, ATSCALE-26892

Support page now in Design Center​

The Support page has been moved from the Control Center to Design Center. For more information, see Contacting AtScale Support.

ATSCALE-23238

New DAX functions​

AtScale now supports the following DAX functions:

  • HASONEVALUE
  • AVERAGEX
  • EXCEPT
  • ISINSCOPE
  • SELECTEDVALUE

Additionally, the ALLSELECTED and ALL functions can now be used in expressions with the CALCULATE function. For more information, see Supported DAX Language Elements.

ATSCALE-17860, ATSCALE-11088

Support for inbound query CROSSJOIN operations that return empty cells​

AtScale can now be configured to calculate crossjoins of dimensions with empty values. This functionality is controlled by the following global settings:

  • query.emptyValueCrossJoin.enabled: When enabled (true), AtScale can calculate crossjoins of dimensions that contain empty values. This setting is disabled by default.

    Important

    Enabling this setting may result in slowed query performance.

  • query.emptyValueCrossJoin.requireConstraints: When enabled (true), crossjoins of dimensions that contain empty values (controlled by query.emptyValueCrossJoin.enabled) are only calculated if the query contains constraints. This setting is enabled by default.

    Important

    Disabling this setting when query.emptyValueCrossJoin.enabled is enabled is not recommended, as it may result in unconstrained crossjoins.

For more information, see Query Settings.

ATSCALE-26305

New First Child and Last Child options for semi-additive metrics​

You can now configure semi-additive metrics to return either the first child or last child of a dimension. This enables you to create semi-additive metrics that return NULL values when used across a time dimension.

To support this functionality, the Semi-additive metric field in the Metric properties panel contains two new options: First Child and Last Child.

note

When using either First Child or Last Child, be aware of the semi-additive trigger hierarchy's Exclude values with no fact data setting. When this option is disabled, the first child and last child always return the first or last child dimension member via an outer join with the semi-additive hierarchy's relationship key. When Exclude values with no fact data is enabled (the default), the system performs an inner join, resulting in the first child or last child result that has a fact table row. Keep the fact table record requirement in mind when using first child/last child with the associated hierarchy's Exclude values with no fact data setting.

For more information, see Semi-Additive Metrics and Add Semi-Additive Metrics.

ATSCALE-24760

New Visible toggle for calculation groups and calculated members​

You can now control whether calculation groups and calculated members appear in BI tools from the Calculation Group properties and Calculation Member properties panels. Previously, this could only be done via SML.

To support this functionality, both panels contain a new Visible toggle. For more information, see Add Calculation Groups and Calculated Members.

ATSCALE-24801

Support for queries with multiple calculation groups​

AtScale now supports queries containing multiple calculation groups, enabling you to evaluate metrics using calculations from more than one group. This gives BI tool users the flexibility to combine multiple calculations at runtime, without requiring model designers to create every necessary calculation combination in advance. Overall, this functionality can help reduce the number of calculations in your models.

To support this, the Calculation Group properties panel now contains an optional Precedence field, where you can set the rank of the calculation group. At runtime, groups are evaluated in descending order of their precedence. The default value of Precedence is controlled by the new query.calculationGroups.defaultPrecedence global setting.

For more information, see Add Calculation Groups and Calculated Members, Introduction to Calculation Groups, and Query Settings.

ATSCALE-25330

Constraint translation enhancement​

AtScale's constraint translation functionality has been enhanced to identify the earliest member required to satisfy a query, and apply it to the query as a constraint. This improves performance for queries containing dimensional modifications such as ParallelPeriod, PrevMember, Lag, etc.

Note

Constraint translation is a Public Preview feature.

For more information, see Using Constraint Translation for Fact Table Query Acceleration.

ATSCALE-24337

New query scopes for semi-additive metrics​

You can now configure AtScale to scope queries on semi-additive metrics by metric, model, or dataset. This behavior is controlled by the new query.planning.semiAdditive.multiMeasureHandling global and model settings.

Note

The new query.planning.semiAdditive.multiMeasureHandling settings replace the Boolean query.planning.semiAdditive.forceIndividualMeasureCheck settings. Existing configurations are automatically migrated as follows:

  • query.planning.semiAdditive.forceIndividualMeasureCheck: true is migrated to query.planning.semiAdditive.multiMeasureHandling: measure.
  • query.planning.semiAdditive.forceIndividualMeasureCheck: false is migrated to query.planning.semiAdditive.multiMeasureHandling: model.

For more information, see Query Settings (global-level) and Query Settings (model-level).

ATSCALE-25753