Skip to main content

Known Issues

Before installing or upgrading AtScale, please review this section to be aware of all known issues.

Aggregates become inactive on catalogs that have been redeployed after being undeployed​

If you undeploy a catalog, and then redeploy it two or more days later (after the aggregate maintenance job has run at least twice), the catalog's aggregate definitions become inactive and cannot be recovered.

As a workaround, you can deploy the catalog with a different name.

ATSCALE-23504

Aggregate status remains out of date if the engine is restarted while they are being built​

If the AtScale engine is restarted while aggregates are in the process of being built, the state of those aggregates remains out of date until the aggregate maintenance job runs again. Aggregate maintenance jobs run automatically every 24 hours at 04:00 UTC.

ATSCALE-23144

For models 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 models that have more than 1600 attributes. This is due to a limitation of the PostgreSQL database used to answer these queries.

ATSCALE-22911

Identity Broker logout does not completely log out of Design Center​

Users who log in to the Identity Broker from Design Center, then log out of the Identity Broker, are not automatically logged out of Design Center. This is because the Identity Broker logout event interrupts the Design Center function.

ATSCALE-22180

Aggregates removed on redeploy​

In the new deploy mechanism, when the AtScale UI compiles SML into a project.xml, it is reinitialized, causing aggregates to be invalidated. This results in individual aggregates being rebuilt after each deployment.

ATSCALE-22187

Tableau: Double dashes in catalog names creates empty .tds files​

Double dashes (--) in the unique names of catalogs causes corruption of Tableau .tds file generation. This is because double dashes are reserved in many databases, and signal a comment in SQL. AtScale recommends avoiding this character pattern when creating and deploying catalogs.

ATSCALE-16605, ATSCALE-22167

Perspectives cannot contain multiple objects with the same display names​

Perspectives cannot contain references to multiple objects with the same display names/labels, as this results in errors at deploy time.

ATSCALE-22326