Known Issues
Before installing or upgrading AtScale, please review this section to be aware of all known issues.
I2024.2.6
Iris JDBC does not support CTEs
The Iris JDBC driver does not support Common Table Expressions (CTEs), so the recent feature that enables the query planner to use CTEs is not supported for Iris. If you are using AtScale on Iris, you need to set the following engine setting:
QUERY.PLANNING.ALLOWCTES=False
By default, this setting is set to True
.
Some GBQ aggregate creation queries falsely display as Failed
Some Google BigQuery aggregate creation queries will display as Failed when they actually succeeded. This issue does not affect the display of the aggregate instance status, which is correctly displayed as Active.
ATSCALE-23272
For cubes with more than 1600 attributes, AtScale fails to answer all PostgreSQL metadata queries from BI tools
When connected to BI tools via the PostgreSQL interface, AtScale fails to answer all metadata queries on cubes that have more than 1600 attributes. This is due to a limitation of the PostgreSQL database used to answer these queries.
ATSCALE-22911
Limited data platform support
This release features support for the following data platforms:
- Databricks
- Snowflake
- Google BigQuery
- MSSQL
- Postgres
- Iris
Other supported data platforms will be reintroduced in a later release, including:
- Hadoop platforms: CDP, Hortonworks and MapR
- Synapse
- Redshift
- DB2
Cubes without a measure or dimension fail to publish
In I2024.2.4, cubes that do not contain a single measure and/or a single dimension cause projects to fail to publish. While the product allowed this in the past, a measureless and dimensionless cube is an illegitimate cube. It provides no function and utilizes server memory on publish. AtScale recommends cleaning up/modifying these cubes in projects intended for publish.
ATSCALE-22808
Simba Hive driver only supports ASCII character set
Non-ASCII character sets are not interpreted properly by the Simba Hive driver. For customers requiring broader character support, AtScale recommends using the PostgreSQL interface.
ATSCALE-13603
Aggregation Functions For Calculated Measures
The aggregation functions for calculated measures functionality is currently only supported on Snowflake and Google BigQuery. A future dot release is planned to extend support to other platforms.
ATSCALE-20465
Microsoft Power BI: Is-Not Filters Result in Incorrect Grand Totals for PeriodsToDate Calculated Measures in Some Situations
Microsoft Power BI visualizations display incorrect Grand Total values when Is-Not filters are applied to calculated measures that use the PeriodsToDate function. As a workaround, you can use the DatesPeriodsToDate function on calculated measures, for which Power BI displays correct Grand Total values.
ATSCALE-20118
Editing calculated measures fails after duplicating cubes
After duplicating a cube within a project, you cannot edit the calculated measures within the new cube. Because of this issue, the Duplicate feature is disabled at the cube level.
As a workaround, you can use the Duplicate feature at the project level.
ATSCALE-18622
Adding calculated measures with the same names to multiple cubes within a project fails
You cannot add calculated measures with the same names to multiple cubes within a single project.
If you try to add or save a calculated measure with the same Name or Query Name as a calculated measure in another cube within the same project, AtScale displays an error message on the Errors tab. If you need to use the same name for multiple calculated measures, you should save the cubes they belong to within separate projects.
ATSCALE-18641
I2024.2.4
For cubes with more than 1600 attributes, AtScale fails to answer all PostgreSQL metadata queries from BI tools
When connected to BI tools via the PostgreSQL interface, AtScale fails to answer all metadata queries on cubes that have more than 1600 attributes. This is due to a limitation of the PostgreSQL database used to answer these queries.
ATSCALE-22911
Limited data platform support
I2024.2.4 features support for the following data platforms:
- Databricks
- Snowflake
- Google BigQuery
- MSSQL
- Postgres
- Iris
Other supported data platforms will be reintroduced in a later release, including:
- Hadoop platforms: CDP, Hortonworks and MapR
- Synapse
- Redshift
- DB2
Cubes without a measure or dimension fail to publish
In I2024.2.4, cubes that do not contain a single measure and/or a single dimension cause projects to fail to publish. While the product allowed this in the past, a measureless and dimensionless cube is an illegitimate cube. It provides no function and utilizes server memory on publish. AtScale recommends cleaning up/modifying these cubes in projects intended for publish.
ATSCALE-22808
Calculation groups show the same Subtotal and Grand Total on partial selection of months on a time hierarchy
In reports that include calculation groups, on partial selection of months in a time hierarchy, the Subtotal at the year level and the Grand Total display the same values. This issue occurs if the year level has Custom Empty Member defined.
ATSCALE-21402
Simba Hive driver only supports ASCII character set
Non-ASCII character sets are not interpreted properly by the Simba Hive driver. For customers requiring broader character support, AtScale recommends using the PostgreSQL interface.
ATSCALE-13603
Aggregation Functions For Calculated Measures
The aggregation functions for calculated measures functionality is currently only supported on Snowflake and Google BigQuery. A future dot release is planned to extend support to other platforms.
ATSCALE-20465
Microsoft Power BI: Is-Not Filters Result in Incorrect Grand Totals for PeriodsToDate Calculated Measures in Some Situations
Microsoft Power BI visualizations display incorrect Grand Total values when Is-Not filters are applied to calculated measures that use the PeriodsToDate function. As a workaround, you can use the DatesPeriodsToDate function on calculated measures, for which Power BI displays correct Grand Total values.
ATSCALE-20118
Editing calculated measures fails after duplicating cubes
After duplicating a cube within a project, you cannot edit the calculated measures within the new cube. Because of this issue, the Duplicate feature is disabled at the cube level.
As a workaround, you can use the Duplicate feature at the project level.
ATSCALE-18622
Adding calculated measures with the same names to multiple cubes within a project fails
You cannot add calculated measures with the same names to multiple cubes within a single project.
If you try to add or save a calculated measure with the same Name or Query Name as a calculated measure in another cube within the same project, AtScale displays an error message on the Errors tab. If you need to use the same name for multiple calculated measures, you should save the cubes they belong to within separate projects.
ATSCALE-18641
I2024.2.3
For cubes with more than 1600 attributes, AtScale fails to answer all PostgreSQL metadata queries from BI tools
When connected to BI tools via the PostgreSQL interface, AtScale fails to answer all metadata queries on cubes that have more than 1600 attributes. This is due to a limitation of the PostgreSQL database used to answer these queries.
ATSCALE-22911
Calculation groups show the same Subtotal and Grand Total on partial selection of months on a time hierarchy
In reports that include calculation groups, on partial selection of months in a time hierarchy, the Subtotal at the year level and the Grand Total display the same values. This issue occurs if the year level has Custom Empty Member defined.
ATSCALE-21402
Simba Hive driver only supports ASCII character set
Non-ASCII character sets are not interpreted properly by the Simba Hive driver. For customers requiring broader character support, AtScale recommends using the PostgreSQL interface.
ATSCALE-13603
Multi-Cube Projects Accessed via the Inbound PostgreSQL Interface not Completely Updated on Publish
For AtScale installations that use the PostgreSQL interface, publishing projects with multiple cubes can create race conditions that result in only a subset of those cubes being created in the metadata database.
Due to this issue, customers who make inbound SQL connections using the PostgreSQL interface AND who deploy projects with multiple cubes should not upgrade to this release.
ATSCALE-22003
Aggregation Functions For Calculated Measures
The aggregation functions for calculated measures functionality is currently only supported on Snowflake and Google BigQuery. A future dot release is planned to extend support to other platforms.
ATSCALE-20465
Microsoft Power BI: Is-Not Filters Result in Incorrect Grand Totals for PeriodsToDate Calculated Measures in Some Situations
Microsoft Power BI visualizations display incorrect Grand Total values when Is-Not filters are applied to calculated measures that use the PeriodsToDate function. As a workaround, you can use the DatesPeriodsToDate function on calculated measures, for which Power BI displays correct Grand Total values.
ATSCALE-20118
Editing calculated measures fails after duplicating cubes
After duplicating a cube within a project, you cannot edit the calculated measures within the new cube. Because of this issue, the Duplicate feature is disabled at the cube level.
As a workaround, you can use the Duplicate feature at the project level.
ATSCALE-18622
Adding calculated measures with the same names to multiple cubes within a project fails
You cannot add calculated measures with the same names to multiple cubes within a single project.
If you try to add or save a calculated measure with the same Name or Query Name as a calculated measure in another cube within the same project, AtScale displays an error message on the Errors tab. If you need to use the same name for multiple calculated measures, you should save the cubes they belong to within separate projects.
ATSCALE-18641
I2024.2.2
For cubes with more than 1600 attributes, AtScale fails to answer all PostgreSQL metadata queries from BI tools
When connected to BI tools via the PostgreSQL interface, AtScale fails to answer all metadata queries on cubes that have more than 1600 attributes. This is due to a limitation of the PostgreSQL database used to answer these queries.
ATSCALE-22911
Calculation groups show the same Subtotal and Grand Total on partial selection of months on a time hierarchy
In reports that include calculation groups, on partial selection of months in a time hierarchy, the Subtotal at the year level and the Grand Total display the same values. This issue occurs if the year level has Custom Empty Member defined.
ATSCALE-21402
Simba Hive driver only supports ASCII character set
Non-ASCII character sets are not interpreted properly by the Simba Hive driver. For customers requiring broader character support, AtScale recommends using the PostgreSQL interface.
ATSCALE-13603
Multi-Cube Projects Accessed via the Inbound PostgreSQL Interface not Completely Updated on Publish
For AtScale installations that use the PostgreSQL interface, publishing projects with multiple cubes can create race conditions that result in only a subset of those cubes being created in the metadata database.
Due to this issue, customers who make inbound SQL connections using the PostgreSQL interface AND who deploy projects with multiple cubes should not upgrade to this release.
ATSCALE-22003
Aggregation Functions For Calculated Measures
The aggregation functions for calculated measures functionality is currently only supported on Snowflake and Google BigQuery. A future dot release is planned to extend support to other platforms.
ATSCALE-20465
Microsoft Power BI: Is-Not Filters Result in Incorrect Grand Totals for PeriodsToDate Calculated Measures in Some Situations
Microsoft Power BI visualizations display incorrect Grand Total values when Is-Not filters are applied to calculated measures that use the PeriodsToDate function. As a workaround, you can use the DatesPeriodsToDate function on calculated measures, for which Power BI displays correct Grand Total values.
ATSCALE-20118
Editing calculated measures fails after duplicating cubes
After duplicating a cube within a project, you cannot edit the calculated measures within the new cube. Because of this issue, the Duplicate feature is disabled at the cube level.
As a workaround, you can use the Duplicate feature at the project level.
ATSCALE-18622
Adding calculated measures with the same names to multiple cubes within a project fails
You cannot add calculated measures with the same names to multiple cubes within a single project.
If you try to add or save a calculated measure with the same Name or Query Name as a calculated measure in another cube within the same project, AtScale displays an error message on the Errors tab. If you need to use the same name for multiple calculated measures, you should save the cubes they belong to within separate projects.
ATSCALE-18641
I2024.2.1
Calculation groups show the same Subtotal and Grand Total on partial selection of months on a time hierarchy
In reports that include calculation groups, on partial selection of months in a time hierarchy, the Subtotal at the year level and the Grand Total display the same values. This issue occurs if the year level has Custom Empty Member defined.
ATSCALE-21402
Simba Hive driver only supports ASCII character set
Non-ASCII character sets are not interpreted properly by the Simba Hive driver. For customers requiring broader character support, AtScale recommends using the PostgreSQL interface.
ATSCALE-13603
Multi-Cube Projects Accessed via the Inbound PostgreSQL Interface not Completely Updated on Publish
For AtScale installations that use the PostgreSQL interface, publishing projects with multiple cubes can create race conditions that result in only a subset of those cubes being created in the metadata database.
Due to this issue, customers who make inbound SQL connections using the PostgreSQL interface AND who deploy projects with multiple cubes should not upgrade to this release.
ATSCALE-22003
Aggregation Functions For Calculated Measures
The aggregation functions for calculated measures functionality is currently only supported on Snowflake and Google BigQuery. A future dot release is planned to extend support to other platforms.
ATSCALE-20465
Microsoft Power BI: Is-Not Filters Result in Incorrect Grand Totals for PeriodsToDate Calculated Measures in Some Situations
Microsoft Power BI visualizations display incorrect Grand Total values when Is-Not filters are applied to calculated measures that use the PeriodsToDate function. As a workaround, you can use the DatesPeriodsToDate function on calculated measures, for which Power BI displays correct Grand Total values.
ATSCALE-20118
Editing calculated measures fails after duplicating cubes
After duplicating a cube within a project, you cannot edit the calculated measures within the new cube. Because of this issue, the Duplicate feature is disabled at the cube level.
As a workaround, you can use the Duplicate feature at the project level.
ATSCALE-18622
Adding calculated measures with the same names to multiple cubes within a project fails
You cannot add calculated measures with the same names to multiple cubes within a single project.
If you try to add or save a calculated measure with the same Name or Query Name as a calculated measure in another cube within the same project, AtScale displays an error message on the Errors tab. If you need to use the same name for multiple calculated measures, you should save the cubes they belong to within separate projects.
ATSCALE-18641