Skip to main content

New Features and Improvements

AtScale contains the following new features and improvements.

C2026.3.0

Enhanced model metadata

AtScale has enhanced and extended its model metadata to allow users to make better use of the SQL interface and robustness of the AtScale semantic layer, as well as provide improved context to LLMs.

ATSCALE-43942

Create Git branches in Design Center

You can now create Git branches from within Design Center. In the Workspace panel, the Branch field now has its own menu, which enables you to create a branch from the one you're currently on. For more information, see Git Workflows.

Note

As part of this change, the options for linking, editing, and unlinking repositories have moved to the new context menu for the Repo field in the Workspace panel. For more information, see Managing Git Repositories in AtScale.

ATSCALE-23132

PGWire (SQL) streaming

The AtScale PGWire interface (port 15432) now streams results back to the SQL client.

Note

To revert back to the previous behavior (i.e., buffering the result set in engine memory until all results are returned), open a ticket with AtScale Support. You will receive instructions on setting up an environment variable to disable the new behavior.

ATSCALE-21094

New tab for data validation errors in the Model Validator

The Model Validator contains a new Data Validation tab, which displays all errors related to data validation; for example, if your model contains multiple levels pointing to a single, unique key column. Note that compiler errors still appear on the Errors tab of the panel.

This change helps simplify the process of troubleshooting models, as errors related to structural issues are now separate from those related to data issues.

For more information, see About Design Center.

ATSCALE-43949

New JDBC connection string format

AtScale uses a new format for JDBC connection strings: jdbc:postgresql://<host>:<port>/atscale_catalogs. This change ensures that JDBC connection strings are consistent for all BI tools that require them, and that they can be used to connect to the AtScale MCP Server.

Note

AtScale still supports the previous connection string format of jdbc:postgresql://<host>:<port>/<catalog_name>. If you currently use this format, there is no need to update your connections with the new one.

ATSCALE-43017

New DAX function

AtScale now supports the DISCTINCT (table) DAX function. For more information, see Supported DAX Language Elements.

ATSCALE-23153