Skip to main content
Version: Next

Resolved Issues

The following issues have been resolved.

Microsoft Power BI: Connecting to a project was slow​

Connecting to an AtScale project from Power BI was slow when the client session was with either the non-leader engine or the query engine, and the AtScale organization contained a large number of projects. This issue has been resolved.

ATSCALE-23447

"Getting planning prereqs" stage of query planning took a long time​

Under high concurrent load, queries started to slow down and display an increased amount of time (about 1-2 minutes) in the "Getting planning prereqs" query stage. This issue has been resolved.

ATSCALE-26209

Power BI: Matrix visuals sorted by measures crashed after scrolling​

In Power BI, matrix visuals that were sorted by measures crashed after scrolling down to the next page of the report. This issue has been resolved.

ATSCALE-26104

AtScale produced incorrect results for tuple-constrained moving window of distinct count expressions​

AtScale produced incorrect results for tuple-constrained moving window of distinct count measure expressions. This issue has been resolved.

ATSCALE-26039

Data Catalog API returned the same values for cube name and caption​

The Data Catalog API for MDSCHEMA_CUBES returned the same values for the cube name and caption. Additionally, it did not return a value for the cube description. This issue has been resolved.

ATSCALE-24496

Importing sample data into different organizations caused aggregate maintenance failures​

Importing AtScale's sample projects into different organizations caused aggregate maintenance to fail. This issue has been resolved.

ATSCALE-24205

Users could not modify runtime permissions in AtScale instances with large numbers of users​

In AtScale instances that contained a large number of users, users with lower-end hardware experienced browser crashing and an inability to edit cube runtime permissions.

This issue has been resolved. Additionally, AtScale now recommends a minimum of 8GB of RAM to use Design Center.

ATSCALE-23131

Projects were sometimes unpublished after the engine was restarted​

Projects were occasionally unpublished after the AtScale engine was restarted. This issue has been resolved.

As part of the fix for this issue, modifications to the following settings now require an engine restart to take effect:

  • query.language.mdx.caseInsensitiveStringComparison
  • query.language.mdx.currentMember.allowLegacySyntax

ATSCALE-21521

Queries failed with a "Boxed Exception" error​

Queries failed with a "Boxed Exception" error. This issue has been resolved.

ATSCALE-26261

Queries failed with an error of "A portion of this TopN query is not currently supported"​

Queries failed with an error of "A portion of this TopN query is not currently supported". This issue has been resolved.

ATSCALE-26875

Queries failed with an error of "Error during query planning: This query would contain joins or aggregations that are not allowed"​

Queries failed with an error of "Error during query planning: This query would contain joins or aggregations that are not allowed". This issue has been resolved.

ATSCALE-26934

Google BigQuery: Aggregate maintenance did not delete aggregate instances from the schema​

Aggregate maintenance did not delete aggregate instances from Google BigQuery, even though they appeared to have been removed in Design Center. This occurred when BigQuery used different projects for query execution prioritization and the aggregate schema. This issue has been resolved.

ATSCALE-27370

Microsoft Excel: First/last child values did not appear when using filters​

In Excel, first/last child measure values disappeared from reports when a filter was applied. This issue has been resolved.

ATSCALE-27728