Skip to main content
Version: I2023.4.1

Resolved Issues

The following issues have been resolved in 2023.4.1.

Microsoft Excel: Text search for filters was not working when the Select Multiple Values checkbox was selected​

In Microsoft Excel, text search for filters was not working properly when the Select Multiple Values checkbox was selected. This issue has been resolved.

ATSCALE-18547

Microsoft Power BI: Results were missing when values were selected for Year and Month filters​

Microsoft Power BI visualizations did not display information for calculated measures created with the PeriodsToDate function. This occurred when the visualizations contained filters for Year and Month, with values selected for both filters. This issue has been resolved.

ATSCALE-16355

Microsoft Power BI: Results were missing when values were selected for Month filter​

Microsoft Power BI visualizations did not display information for calculated measures created with the PeriodsToDate function. This occurred when the visualizations contained filters for Year and Month, with multiple values selected for the Month filter. This issue has been resolved.

ATSCALE-16246

User queries were failing after two minutes with AskTimeoutException​

User queries processed by the non-leader node were failing after two minutes with an AskTimeoutException. This issue has been resolved.

ATSCALE-18735

DAX SWITCH queries involving a single dimension and a single measure were failing​

DAX queries that used the SWITCH function on only one measure and one dimension were failing. This issue has been resolved.

ATSCALE-17167

Duplicate Dimensions Appeared when Creating Semi-Additive Measures​

When adding or editing a semi-additive measure, the dimensions list in the Semi-Additive Measure field contained duplicate values, making it difficult to determine which one to use.

To resolve this issue, the following changes have been made:

  • The dimensions list now displays each dimension's full information, including its name, hierarchy name, level name, and role-playing relationships. This enables you to differentiate between different instances of the same dimension.
  • If you create a role-playing relationship for a dimension using the same template as an existing role-playing relationship on that dimension, AtScale now reuses the existing instance of the relationship, instead of creating a new one. This ensures that duplicate role-playing relationships with the same names do not appear in the dimensions list.

To fix this issue for your current models, you must upgrade their role-playing relationships to remove duplicates. After upgrading to AtScale 2023.4.1, do the following:

  1. Open each of your models in Design Center. If any contain duplicate role-playing relationships, a message appears on the Warnings tab.
  2. Click Fix It in the warning message to upgrade the role-playing relationships in the model. Alternatively, you can manually fix the model by deleting all relationships to the affected dimension and recreating them in Design Center (applies to AtScale I2023.4.1 or later).
  3. If the model defines semi-additive measures (Last Non-Empty or First Non-Empty), edit those measures to select the correct semi-additive dimension.

ATSCALE-9439

Group-Based Security Dimensions Produced Inflated Measure Values​

When individual AtScale users were in multiple user groups that had overlapping access to specific attributes in security dimensions, query results for those attributes were inflated. For example, if UserA was a member of both Group1 and Group2, and both groups had access to AttributeX, query results for AttributeX would be doubled for UserA. This issue has been resolved.

ATSCALE-18309

Microsoft Power BI: Incorrect Grand Totals Were Displayed for Period-to-Date Calculations​

When using Microsoft Power BI in either SuperDAX MD or Tabular mode, Grand Total values for Period-to-Date calculations were incorrect when used with NOT IN dimension filters. This issue has been resolved. In these cases, Power BI now displays empty cells for Grand Total values.

ATSCALE-18027

Level Detection was Not Discriminating Between Grand Totals and Top-Level Hierarchies for SuperDAX MD and DAX Tabular Dialects​

For the SuperDAX MD and DAX Tabular dialects, level detection was not discriminating between Grand Totals and top-level hierarchies, producing incorrect query results. This issue has been resolved.

ATSCALE-18131

Microsoft Power BI: Filtering from One Visualization to Another Failed when DateTime Fields were Involved​

When using Microsoft Power BI in either SuperDAX MD or DAX Tabular mode, filtering from one visualization to another failed when DateTime fields with a Time component were involved. This issue has been resolved.

ATSCALE-15556

Microsoft Excel: Drill Through Did Not Support Numeric Columns​

In Microsoft Excel, Drill Through results did not recognize numeric columns as such. This issue has been resolved.

ATSCALE-14917