Skip to main content
Version: I2023.2.1

Resolved Issues

The following issues have been resolved.

2023.2.1​

Error on excluding a month from year results​

When using Power BI connected in superdaxmd mode, a report with a table and slicer added for a year with all months selected completed successfully. De-selecting a month in the slicer resulted in 'Can't display the visual' error message.

ATSCALE-16241

Internal error prevented loading the schema​

When attempting to execute any query from Power BI Desktop against multiple models, the "Internal Error prevented loading the schema" error message was displayed. The issue occurred when the daxdialect setting was set to legacy or superdaxmd.

ATSCALE-16228

Incorrect report results​

When using Power BI connected in superdaxmd mode, a report with a table and slicer added and several entries selected completed successfully, but the results were not correct.

ATSCALE-16245

Upgrade to 2023.2.0 failed​

There was a failure during the upgrade of an AtScale system from 2022.1.0 to 2023.2.0.

ATSCALE-16339

2023.2.0​

Calculated measures removed from copied cube​

After copying a cube and deleting or editing calculated measures in the copy, the changes were also applied to the original cube.

ATSCALE-13742

Incorrect Grand Total for PeriodsToDate measure​

In AtScale, there is a calculated measure created with the PeriodsToDate function. When using this measure in a Power BI visualization, the Grand Total value shown was incorrect.

ATSCALE-14756

Power BI visualization cannot be displayed when connected in superdaxmd mode​

When using Google BigQuery as data warehouse, running a visualization in Power BI connected in superdaxmd mode leads to the following error message: Can't display the visual

ATSCALE-15027

Report failed when using DAX Tabular dialect and Databricks​

Running a report in Power BI failed when all of the following conditions were met: using Databricks as data warehouse, the project contains a time dimension where key and value columns are of integer type, and AtScale is configured to use the DAX Tabular dialect.

ATSCALE-14678

Error during publishing​

When publishing a big model, the final step of the publishing wizard displayed a message that the publishing failed. This was only a visualization issue, the publishing actually completed successfully.

ATSCALE-10274

Dimension canvas closes while adding calculated column​

With the main cube canvas and a dimension canvas opened, if the user started adding a calculated column for the dimension and selected a dataset column, the dimension canvas was closed. This was only a visualization issue, it did not affect the creation of a calculated column.

ATSCALE-14757

Hierarchy shown when all levels in the hierarchy are hidden​

When a hierarchy level was hidden and it had secondary attributes that were visible, the hidden hierarchy name was visible in BI tools.

ATSCALE-15404

Broken query with a single member from a set in Tableau​

Creating a set in Tableau, including it in a report, and editing the set until only one element was left lead to an error message containing a text like "Error from server: error code: '0' error message: 'null".

ATSCALE-15401

Incorrect permissions when using Project Update​

The value of the "Default Project/Cube Security" global setting was not taken into account when creating the Design-Time and Run-Time permissions for a new Cube or Perspective created using the Project Update feature.

ATSCALE-15048

Incorrect reports when using custom empty members​

When there were custom empty members defined for a dimension level, the results shown in BI tools were incorrect.

ATSCALE-14482

Incorrect TDS file​

If the name of a cube element contained several space characters, opening the resulting TDS file led to issues with Tableau.

ATSCALE-14630

Cube settings not working against perspectives​

A cube-level setting configured in the Design Center had no effect when querying against a perspective.

ATSCALE-9642

Cannot use Power BI when relationship starts with a number or a special character​

In case the name used for a relationship started with a number or a special character, visualizations in Power BI displayed 'Cannot load model' error message.

ATSCALE-15508

Failed statistics queries​

Some statistics queries were displayed as Failed correctly in the Query screen, and there was 'No SQL found' error message shown for them.

ATSCALE-15584

Visualization not displayed when connecting in legacy mode​

When there was a calculated measure in a cube, connecting with Power BI in legacy mode to this cube and trying to use the calculated measure in a visualization led to "Can't display the visual" error.

ATSCALE-14558