Skip to main content

Resolved Issues

The following issues have been resolved.

Deployed Data Models Did Not Display For Non-Admin Users​

AtScale users could not see their deployed models unless they were assigned the admin role in the Identity Broker. This issue has been resolved.

ATSCALE-20976

Relationship Lines Did Not Display Correctly In Design Center​

In Design Center, the lines showing the relationships between dimensions and fact datasets were not properly connected to the dataset. This issue has been resolved.

ATSCALE-19928

Incremental Aggregates Were Not Supported​

Incremental aggregates are now available. For more information on working with incremental aggregates, see Managing Aggregates.

ATSCALE-20946

Perspectives Were Not Supported​

Perspectives are now available. For information on working with perspectives, see Modeling Perspectives and the AtScale SML Object Documentation on GitHub.

ATSCALE-21000

Microsoft Excel: Reports Containing Calculation Groups And Calculated Metrics With Hidden Metrics Failed​

In Microsoft Excel, reports failed when they contained both a calculation group and calculated metric that contained a hidden metric. This issue has been resolved.

ATSCALE-20788

Microsoft Power BI Online Service: The Export Data Option Failed With Matrix Visual Reports​

In Microsoft Power BI Online Service, using the Export Data option from a matrix virtual report failed when both of the following conditions were true:

  • The AtScale model used in the report contained a row security object with a lookup rule of Use Filter Key.
  • The Power BI report was created with a connection that included daxdialect=tabular or daxdialect=superdaxmd.

This scenario also caused queries to fail in AtScale. This issue has been resolved.

ATSCALE-20271

Power BI: Reports Containing Metrics With UTCNOW() Failed​

In Power BI, reports containing metrics that used the UTCNOW() DAX function failed. This issue has been resolved.

ATSCALE-19848

Power BI: Incorrect Outbound Queries Generated When Filtering By NULL And Using SuperDAXMD​

When connected to Power BI using SuperDAXMD, filtering reports by NULL values incorrectly yielded no results. This was caused by incorrect outbound queries being generated in AtScale. This issue has been resolved.

ATSCALE-18260

Power BI: Applying Multiple Degenerate Dimension Level Slicers Reset Other Slicers​

In Power BI, applying multiple slicers based on degenerate dimension levels reset other slicers in the report to All. This occurred when all slicers involved were based on degenerate dimension levels. This issue has been resolved.

ATSCALE-18032