Skip to main content

Resolved Issues

The following issues have been resolved.

Changing passwords to atscale-kc-admin broke the Deploy model function​

Changing the password for the atscale-kc-admin user in the Identity Broker caused model deployments to fail. This issue can be resolved by following the steps to update the atscale-api and atscale-engine clients described in the Upgrade Requirements.

ATSCALE-22500

Microsoft PowerBI: Sort keys did not work on secondary attributes​

In PowerBI, sort keys did not work on secondary attributes when there was only one in the hierarchy, resulting in values not being properly sorted. This issue has been resolved.

ATSCALE-17117

Microsoft Excel: Keep Only Selected Items filter was slow​

In Excel, applying the Keep Only Selected Items filter to high cardinality secondary attributes and level aliases resulted in slow performance. This issue has been resolved: the filter’s performance for secondary attributes and level aliases is now optimized.

ATSCALE-21434

Power BI, Excel: Single-level hierarchies displayed without hierarchy name​

In Power BI and Excel, single-level hierarchies with no secondary attributes displayed without the hierarchy name. This issue has been resolved: hierarchies now always display with their dimension, hierarchy, and level names, whether or not they include secondary attributes.

ATSCALE-22501

Identity Broker admin password could not be updated​

In all containerized releases up to and including C2024.8.0, the password for atscale-kc-admin could not be updated alone. This issue has been resolved.

ATSCALE-22301

Aggregate stat jobs failed due to default database​

When AtScale initiated aggregate stat jobs, it defaulted to the aggregate database. This meant that AtScale looked for tables in the aggregate database where the base data may or may not have existed. If it didn’t exist, the stat queries failed and prevented aggregates from building. This issue has been resolved.

ATSCALE-22424

Power BI, Excel: Reports and queries failed when SOAP.SAFE.XML.PARSING was enabled​

The AtScale Engine setting SOAP.SAFE.XML.PARSING can be enabled to prevent XXE attacks. Previously, when this setting was enabled, Power BI and Excel reports and queries would fail against AtScale. This issue has been resolved: when the setting is enabled, Power BI and Excel queries and reports should no longer fail.

note

SOAP.SAFE.XML.PARSING is disabled by default. To enable it, set the following custom engine setting. For information on adding custom engine settings, see Changing Engine Settings.

  • Setting Name: SOAP.SAFE.XML.PARSING
  • Setting Value: true

You do not need to restart the engine after changing this setting.

ATSCALE-16773, ATSCALE-20815