Skip to main content
Version: Next

Resolved Issues

The following issues have been resolved.

I2025.5.0​

Existing partitions were not considered when grace period overrides were defined​

When an incremental aggregate build ran with a grace period override, the build did not include the cube's aggregate partitions. This issue has been resolved.

ATSCALE-28539

Default hierarchical members were not applied on calculated columns based on multiple fact tables​

Default hierarchical members were not applied on calculated columns based on multiple fact tables, causing unexpected results to appear in reports. This issue has been resolved.

ATSCALE-28305

Submitting the same inbound query multiple times resulted in aggregates that were almost duplicates​

Submitting a single inbound query multiple times produced aggregates that were almost duplicates, differing only in the order of their keys. This issue has been resolved.

ATSCALE-28203

Microsoft Excel: Bottom value filter handled NULL values incorrectly​

In Excel, the Top 10 Filter's Bottom option did not correctly handle NULL values: Rather than ignoring the NULLs and displaying the last 10 non-NULL values, it instead displayed fewer than 10 values, with the NULLs hidden. This issue has been resolved.

ATSCALE-28179

Aggregates based on dimensions with many-to-many relationships to the fact table resulted in wrong data​

The AtScale engine incorrectly used aggregates based on dimensions with many-to-many relationships to the fact table to process queries on other dimensions, resulting in wrong data. This issue has been resolved.

ATSCALE-28163

Aggregates were not properly canceled during batch builds, causing the batch to fail​

When a batch aggregate build was running, if a query for one of the aggregates in the build was manually canceled, the batch continued and incorrectly marked all aggregates as active, including the one associated with the canceled query. This ultimately caused the batch to fail. This issue has been resolved.

ATSCALE-27916

Excel: Results from dimension-only queries were sometimes not sorted correctly​

In Excel, results from dimension-only queries were sometimes sorted according to the hierarchy's Value Column, rather than its Sort Column. This occurred when the number of results exceeded the QUERY.LANGUAGE.MDX.DIMQUERY.RESULT.LIMIT setting configured in the engine. This issue has been resolved.

ATSCALE-27855

Tableau: Reports created from calculated measures made of concatenated secondary attributes and measures based on multiple fact tables resulted in Query Planning Errors​

In Tableau, creating a report using a calculated measure made of concatenated secondary attributes and a measure based on multiple fact tables resulted in a Query Planning Error. This issue has been resolved.

ATSCALE-27685

Query planning failed after mapping a project to a new data warehouse mid-publish​

If a project was mapped to a new data warehouse while it was publishing, queries on the published project failed during the planning stage. This issue has been resolved.

ATSCALE-27521

Query planning failed with an error of "Could not find ColumnData"​

Query planning failed with an error of "Could not find ColumnData". This issue has been resolved.

ATSCALE-27161

Excel: Slicers could not be created in pivot tables that contained grouped fields​

In Excel, slicers could not be created in pivot tables that contained grouped fields. This issue has been resolved.

ATSCALE-27049

The Update Project API endpoint deleted the published project​

Updating a project using the Update Project API endpoint resulted in the published project being deleted.

This issue has been resolved. To update the project XML, the following endpoint should be used:

PUT - api/1.0/org/{orgId}/project/{projectId}/xml

ATSCALE-26194

Canceling multiple aggregate creation queries consecutively failed​

Aggregate creation queries failed to be canceled when multiple were canceled consecutively. This issue has been resolved.

ATSCALE-26103

Updating project permissions via API failed, despite appearing to succeed​

Updating project permissions using the Update Project Permissions API endpoint appeared to succeed, but the permissions remained unchanged. This issue has been resolved.

ATSCALE-24840

Excel: Using Value Filters on more than one secondary attribute resulted in an error​

In Excel, setting Value Filters on more than one secondary attribute resulted in an error. This issue has been resolved.

ATSCALE-27117

Query engine logged a high volume of errors when a data warehouse with existing aggregates was changed to a read-only source​

When a data warehouse with existing aggregates was edited to be a Read-only source, the AtScale query engine logged a high volume of errors. This issue has been resolved.

ATSCALE-20729

The inbound and planning stages took a long time for some queries​

The inbound and planning stages took a long time to complete for some queries. This issue has been resolved.

ATSCALE-28508

Queries that used the ParallelPeriod function on leaf levels produced incorrect results​

Queries that used the ParallelPeriod function on leaf levels produced incorrect results. This issue has been resolved.

ATSCALE-28186

Queries containing Custom Comparisons failed with an error during planning​

Queries that included custom comparisons failed during query planning with an error of "Error during query planning: assertion failed: No candidate paths found for an attribute". This issue has been resolved.

ATSCALE-27947

Microsoft Power BI: Paged tables and matrices displayed repeated data instead of loading the next page​

When paging through a Power BI table or matrix that used two high-cardinality dimensions and was sorted in descending order by a measure, Power BI issued the same query for the second page. This resulted in the data from the first page being repeated on the second, rather than the second page being properly loaded. This issue has been resolved.

ATSCALE-28586