Skip to main content

Resolved Issues

The following issues have been resolved.

C2026.6.1​

Only users with the superuser_user role could access the Settings > Power BI tab in Design Center and the Power BI page in the Connection Portal. This issue has been resolved.

ATSCALE-50163

DAX model-specific connection strings in the Connection Portal did not contain user XMLA tokens​

The DAX model-specific connection strings in the Connection Portal did not contain user XMLA tokens. This issue has been resolved.

ATSCALE-50563

The Power BI > DAX Connections tab of the Connection Portal displayed repository names instead of catalog names​

The Power BI > DAX Connections tab of the Connection Portal listed models under their repository names, rather than their catalog names. This issue has been resolved.

ATSCALE-50688

The Published Using field incorrectly displayed Personal Token for Power BI reports published with DAX model-specific connection strings​

The Published Using field on the Settings > Power BI tab incorrectly displayed Personal Token for reports published with DAX model-specific connection strings that had been updated with service tokens. This issue has been resolved.

ATSCALE-50768

C2026.6.0​

Preferred aggregate storage did not promote aggregates with distinct count estimate metrics​

Preferred aggregate storage did not promote aggregates with distinct count estimate metrics. This issue has been resolved.

Note

Preferred aggregate storage is a Private Preview feature.

ATSCALE-45509

Role-played dimensions and their hierarchies, levels, and attributes could not be hidden from BI tool users via perspectives. This issue has been resolved.

ATSCALE-48276

AtScale did not check for unsupported parameter combinations when validating the values file​

When validating the values file, AtScale did not prevent global.atscale.tls.existingSecret and global.atscale.tls.caCerts from being set at the same time. This combination of values is not supported, and causes the engine to fail to start.

This issue has been resolved: During validation, AtScale now checks whether these parameters are both set, and returns an error if they are.

DEVOPS-9459

Microsoft Excel: Adding multiple level aliases based on the same level to pivot tables resulted in errors​

In Excel, adding multiple level aliases based on the same level to a pivot table resulted in an error. This issue has been resolved.

ATSCALE-48984

Using parentheses in Custom Empty Member values caused query failures when in-memory aggregates were enabled​

Using parentheses in Custom Empty Member values caused query failures when in-memory aggregates were enabled. This issue has been resolved.

ATSCALE-47700

Aggregate batch builds remained in progress indefinitely​

Aggregate batch builds remained in progress indefinitely when an instance in the batch failed during incremental fragment planning. This issue has been resolved.

ATSCALE-47549

Multiple engine pods could run duplicate maintenance tasks simultaneously​

Multiple engine pods could run duplicate maintenance tasks simultaneously. This issue has been resolved.

ATSCALE-45848

Excel: Keep Only Selected filter failed when preferred aggregate storage was enabled​

Applying the Keep Only Selected filter to hierarchical data in pivot tables failed when Excel was connected to AtScale via the AtScale add-in, and preferred aggregate storage was enabled in AtScale. This issue has been resolved.

Note

Preferred aggregate storage is a Private Preview feature.

ATSCALE-45800

Queries failed when preferred aggregate storage was enabled​

When preferred aggregate storage was enabled, BI tool queries initially succeeded, but failed after refreshing the BI tool's connection to AtScale multiple times. This issue has been resolved.

Note

Preferred aggregate storage is a Private Preview feature.

ATSCALE-45734

Tableau: Using calculated fields in reports caused queries to fail in Snowflake when aggregates were enabled in AtScale​

When aggregates were enabled in AtScale, using calculated fields based on pre-aggregated metrics in Tableau reports caused queries to fail in Snowflake data warehouses. This issue has been resolved.

ATSCALE-45153

Power BI tab displayed incorrect report ownership​

On the Power BI tab of the Settings page, the Is Owned By Me? column incorrectly displayed Yes for reports that were not owned by the current user. This issue has been resolved.

ATSCALE-44858

Microsoft Power BI: TopN metric-based filters failed when slicers were selected​

In Power BI, Table view reports created with TopN metric-based filters failed when slicer values were selected. This occurred when the slicer included a secondary attribute whose dimension had a many-to-many relationship with another dimension. This issue has been resolved.

ATSCALE-24904

Model Validator displayed invalid warnings for level key columns when using Snowflake data warehouses​

When using a Snowflake data warehouse, the Model Validator displayed an invalid warning for level key columns: Child key value points to multiple parent key values. This occurred even when the key column pointed to a single parent value. This issue has been resolved.

ATSCALE-21975

Model could not be deployed after resolving circular embedded dimension dependencies​

Models could not be deployed after resolving dependencies for circular embedded dimensions. This issue has been resolved.

ATSCALE-47566

Excel: Statistics hash collisions caused model connections to fail​

Statistics hash collisions caused model connections in Excel to fail. This issue has been resolved.

ATSCALE-44947

Queries page did not display names of Power BI Service users​

When connected to Power BI Service with token-based authentication, the Queries page in Design Center listed XMLA Service Account as the User for all queries from Power BI, rather than the names of the actual users who initiated them. This issue has been resolved.

ATSCALE-47724

Excel: Editing pivot table filters resulted in errors​

In Excel, editing a pivot table filter resulted in an XML parsing error. This issue has been resolved.

ATSCALE-49925

Improved log messages for promoted aggregates​

When using the promoted aggregates feature, some queries do not use promoted aggregates, and some aggregates are not promoted. Improvements have been made to AtScale's log messages to further address these issues.

ATSCALE-45625

Improved log messages for composite models​

After upgrading to C2026.3.0, the Permissions tab for deployed composite models fails to load, and the models cannot be queried. Improvements have been made to AtScale's log messages to further address these issues.

ATSCALE-47722

AtScale license was not mapped to the system​

A licenseKey could not be set using globa.atscale-entitlement.entitlement.existingLicenseSecret due to the secret itself being mapped to the wrong environment variable. This issue has been resolved.

DEVOPS-9514

poc named profile for resourcesPreset did not provide sufficient resources for the engine pod​

The poc named profile for resourcesPreset did not provide sufficient CPU or RAM for the engine pod, causing it to crash. This issue has been resolved.

DEVOPS-9408

AtScale-generated Power BI service tokens did not support DAX model-specific connection strings​

Service tokens generated on the Power BI tab of the Settings page did not support DAX model-specific connection strings. When a new service token was generated, the model-specific format was replaced with the MDX+Token format, causing model connections to fail. This issue has been resolved.

ATSCALE-49945

Gemini Enterprise: Queries got stuck in a confirmation loop and were not executed​

When working with Gemini Enterprise, the run_query MCP Server tool got stuck in a confirmation loop and never executed the queries. This issue has been resolved.

ATSCALE-50235