Skip to main content

Resolved Issues

The following issues have been resolved.

C2026.10.0​

Models containing more than 6400 objects deployed successfully, but PGWire connections to them failed​

AtScale's PGWire interface cannot connect to deployed models that contain more than 6400 semantic objects. Previously, models with more than 6400 objects could be deployed successfully, but attempts to connect to them over the PGWire interface would fail with an error. This issue has been resolved: AtScale now blocks deployments of models with more than 6400 objects and displays an error clearly stating why.

ATSCALE-49588

Source Control panel did not display a loading indicator when updating incoming commits​

When updating incoming commits, the Source Control panel did not provide any indication that the system was fetching data. This led to confusion, as it appeared as though no changes were available. This issue has been resolved: After clicking Update in the Incoming Commits section of the Source Control panel, the panel now displays an Updating... message and a loading indicator.

ATSCALE-41897

Objects at the top of the Canvas became noninteractive​

The top of the Canvas contained an area where objects became noninteractive. This issue has been resolved.

ATSCALE-50672

Table-based datasets could not be created from Snowflake views​

Table-based datasets could not be created from Snowflake views. A view could be selected when creating or editing the dataset, but did not return any columns. This issue has been resolved.

DEVOPS-10711

Queries generated by deployed models caused high CPU usage and performance issues on the Build tab​

Queries generated by deployed models caused high CPU usage and performance issues on the Build tab. This issue has been resolved.

ATSCALE-53517

Extra datasets were included in query plans, resulting in wrong data​

When a dimension level's key was bound to a second dimensional dataset, the second dataset was joined into query plans for the original dimension, even when the query didn't reference any of its attributes. As a result, queries did not return any data for the original dimension. This issue has been resolved.

ATSCALE-52822

PGWire: Projected NULL literals not referenced in queries' GROUP BY clauses caused the queries to fail​

When using the PGWire endpoint, projected NULL literals that weren't referenced in queries' GROUP BY clauses reached SQL rendering with unresolved aggregation types, causing the queries to fail. Additionally, each failure leaked a pooled data warehouse connection, which led to an outage requiring engine restarts. This issue has been resolved.

ATSCALE-52736

Triggering multiple scheduled aggregate rebuilds at the same time caused the builds to hang indefinitely​

When multiple scheduled full aggregate rebuilds were triggered concurrently or within a short timeframe, the batch remained in progress indefinitely, requiring manual cancellation to recover. This issue has been resolved.

ATSCALE-52567

Microsoft Power BI: Using DAX TREATAS over an empty filter table failed​

In Power BI, using the DAX TREATAS function over an empty filter table failed with an error. This issue has been resolved.

ATSCALE-52393

Amazon Redshift rejected DateTimeType conversion for out-of-range timestamps, silently blocking statistics collection​

AtScale converts DateTimeType values to strings for Redshift HLL cardinality. When a row contained a timestamp outside the representable epoch range, Redshift rejected the conversion, causing the whole cardinality statistic for the column to be lost. This, in turn, had a negative impact on aggregates. This issue has been resolved.

ATSCALE-52309

The MCP Server's connection pool failed at startup​

The MCP Server's connection pool failed repeatedly at startup. This issue has been resolved.

ATSCALE-52109

Outbound queries for aggregate builds performed redundant table scans​

Outbound queries for aggregate builds performed redundant full scans of fact tables, causing increased build times and resource consumption. This issue has been resolved.

ATSCALE-51982

Design Center displayed the same job ID for different Google BigQuery jobs​

Design Center displayed the same Google BigQuery job ID for all outbound queries generated by a single inbound query, even though the queries were executed by different jobs in the data warehouse. This issue has been resolved.

ATSCALE-51928

Design Center displayed misleading warning messages for package and .env files​

Design Center displayed warning messages for package and .env files, indicating that they were unknown object types, even though both files are fully supported. This issue has been resolved.

ATSCALE-50826

Power BI: Including AtScale models in many-to-one composite models resulted in textual attributes being duplicated​

When an AtScale model was used in a many-to-one composite model in Power BI, textual attributes were duplicated in reports. This issue has been resolved.

ATSCALE-50160

Power BI: Including AtScale models in one-to-one composite models resulted in textual attributes failing to load​

When an AtScale model was used in a Power BI composite model with a one-to-one relationship to a non-AtScale dataset, textual attributes failed to load.

ATSCALE-49622

Deploying to Looker failed with an error when the AtScale license did not contain the Looker feature​

Deploying to Looker failed with an error for customers whose AtScale licenses did not contain the Looker feature. This issue has been resolved: AtScale no longer requires a special license to connect to Looker.

ATSCALE-48213

Design Center displayed vague error for data type mismatches between MDX queries and the data warehouse​

When an MDX query contained references to a model attribute whose data type did not match the physical type in the data warehouse, Design Center displayed a generic error message. This issue has been resolved: Design Center now displays a more descriptive error in these cases.

ATSCALE-49753

Microsoft Excel: When a default member was combined with one or more additional default members, querying with an unrelated metric returned non-drillable hierarchy members​

In Excel, when a default member was combined with one or more additional default members, querying with an unrelated metric returned hierarchy members that could not be drilled into. This issue has been resolved.

ATSCALE-54417

Queries that combined a hierarchy with a calculation group could not use system-defined dimensional aggregates when the hierarchy contained secondary attributes​

Queries that combined a hierarchy with a calculation group could not use system-defined dimensional aggregates (including Preferred Aggregate Storage) when a level in the hierarchy had secondary attributes. Those queries ran against the base tables. This issue has been resolved: The engine now creates and uses dimensional aggregates for these queries automatically, so a user-defined aggregate is no longer needed as a workaround.

ATSCALE-52222

Users linked to more than one IdP were denied authentication​

Users linked to more than one identity provider (for example, OIDC plus a leftover SAML link after a migration) were denied authentication. This issue has been resolved, and these users can now sign in.

Note

Queries over connections that impersonate the client will still fail if the user has more than one OIDC link. If this occurs, remove the extra links in the Identity Broker.

ATSCALE-52303

Git branch selector was disabled after deleting and then readding a repository​

If a Git repository was deleted and then readded, the Branch selector in the Workspace panel was disabled, and models in the repository could not be deployed. This issue has been resolved.

Note

If you encountered this issue prior to C2026.10.0 and your repository remains broken after upgrading, you must reset your Git data in Design Center.

ATSCALE-52056

Count/average metrics over a fact column that is also a degenerate dimension key returned wrong unfiltered totals​

A count non-null/average metric over a fact table column that was also a degenerate dimension key returned the distinct member count of the column when queried with no filter and no GROUP BY clause. This issue has been resolved.

ATSCALE-52562

Applying global settings regenerated the Power BI service token, which broke the gateway and published reports​

In token-based Power BI Service setups, applying global settings replaced the shared Power BI service token whenever global_settings.yml contained xmla.auth.token.enabled: true. This occurred even if no setting changed. The old token stopped working immediately, so the Power BI Gateway data source and every published report that used it failed until the gateway was reconfigured and each report owner ran Update Token. Once a token was replaced, any connection attempt using the previous token failed with a Token not found error. This issue has been resolved.

ATSCALE-55856