Skip to main content

Resolved Issues

The following issues have been resolved.

C2026.8.0​

Engine statistics required recollection after upgrade​

In C2026.6 and C2026.7, engine statistics needed to be recollected for all values after upgrading. This resulted in additional statistics queries and delays in displaying model validation errors. This issue has been resolved.

ATSCALE-50705

Partition-based incremental aggregates could only be enabled at the global level​

The aggregate.incrementalUpdate.partition.enabled setting, which enables/disables partition-based incremental aggregates, was not supported at the model level. This issue has been resolved.

ATSCALE-50738

Git repo linking failed when extraCaCerts/existingExtraCaCertsSecret was combined with an HTTPS forward proxy​

Git repositories could not be linked in Design Center when AtScale was configured with both an HTTPS forward proxy and extraCaCerts/existingExtraCaCertsSecret. This issue has been resolved.

DEVOPS-10163

Resolved issues with AtScale licenses that do not contain the data_catalog_api feature​

Previously, customers whose licenses don't contain the data_catalog_api feature encountered issues such as misleading errors after successful catalog deployments, Resource Permissions page load failures, and failed queries when using the AtScale add-on for Google Sheets. These issues have been resolved.

ATSCALE-50539

Some CTE outbound queries referencing base tables used the wrong query role mapping​

Some outbound SQL statements using Common Table Expressions (CTEs) used the Small Interactive Queries query role, even though the CTEs referenced base tables and therefore should have used the Large Interactive Queries query role. This issue has been resolved.

ATSCALE-45757

extraEnvVars was duplicated in the AtScale engine subchart​

extraEnvVars was listed twice in the AtScale engine subchart. This issue has been resolved.

DEVOPS-10404

Tableau: Calculated fields could not be used in reports with calculation groups​

In Tableau, adding a calculated field to a report that contained AtScale calculation groups resulted in an error. This issue has been resolved.

ATSCALE-51197

Dimensional dataset columns could not be dragged to the ends of long hierarchy lists in the Dimension properties panel​

When clicking and dragging a dimensional dataset column to a hierarchy to add it as a level, the column could not be dropped near the bottom of the hierarchy list if the list was very long. This issue has been resolved.

ATSCALE-50393

Microsoft Excel and Power BI could not connect to AtScale when soap.xpress.enabled was set to true​

Microsoft Excel and Power BI could not connect to AtScale when soap.xpress.enabled was set to true. This issue has been resolved.

ATSCALE-50237

Excel: Filter search did not match values after an invalid value was entered​

In Excel, filter search did not yield results for valid values after one invalid value was entered. This occurred when soap.xpress.enabled was set to true. This issue has been resolved.

ATSCALE-50234

Queries failed with an error of "Aggregate functions cannot be nested" when using aggregate tables​

Queries failed with an error of Aggregate functions cannot be nested when using aggregate tables. This issue has been resolved.

ATSCALE-50024

AtScale displayed a misleading error message when the engine pod was unavailable​

When the engine pod was unavailable (i.e., it had crashed or was restarting), Design Center incorrectly displayed an error message indicating that the AtScale license needed to be updated. This issue has been resolved.

ATSCALE-49156

Constraint translation issues​

Multiple issues related to constraint translation have been resolved:

  • Constraint translation on a level was not applied when another level on the same hierarchy had a partition rank defined, but no connection to the fact dataset. This issue has been resolved: A model is now considered invalid and will fail to deploy if it contains a level that has a partition rank defined but no connection to a fact dataset. Additionally, an invalid candidate level no longer disables constraint translation for the entire hierarchy.
  • Constraint translation was applied to join-only connections to fact datasets. This sometimes resulted in it being applied twice (over two levels), when it was only configured on one level. This issue has been resolved: Constraint translation is no longer applied to join-only connections.
  • Constraint translation on a level was not applied when that level was also used in the relationship to the fact dataset it was being translated to. This issue has been resolved: Constraint translation is applied even when the constraint translation level doubles as the join level.

ATSCALE-49138

The wrong key was used in joins when a model contained two dimensions based on a single dataset​

When a model contained two dimensions based on the same dataset, the wrong key was used in joins, resulting in wrong data. This issue has been resolved.

ATSCALE-49085

Design Center displayed deployment failure errors after successfully deploying large catalogs​

Design Center sometimes displayed a deployment failure error after successfully deploying very large catalogs. This issue has been resolved.

ATSCALE-48373

AtScale did not recover after interruptions to data warehouse connectivity​

If AtScale's connection to the data warehouse was interrupted and then restored, queries continued to fail in AtScale until the engine was restarted. This issue has been resolved: AtScale now recovers from data warehouse connection interruptions without requiring an engine restart.

ATSCALE-47611