Release Notes - 2025.10.01

Welcome to the latest One Model product release update. This article provides an overview of the  product innovations and improvements to be delivered on 1 October 2025.

One AI

• The recently released "mode selection" feature in One AI Assistant now displays prompt input hints for each mode. To see this in action, simply select a mode other than "AI Mode" and note how the "How can One AI Assistant help you?" message changes to provide guidance for the selected mode. (ref 4057)
• Systems Administrators deserve love too. To that end, we made it easier to configure Answers for One AI Assistant. We enhanced the Answers section of the One AI Configuration screen to group answers by topic and enable dragging and dropping between and within topics.  (ref 4003)
• Before mode selection was introduced in One AI Assistant, using the words "dashboard" or "Storyboard" was necessary to get a Storyboard result. With "Storyboards" selected as the mode however, using these words should be unnecessary. In this release we removed that constraint. (ref 4030)
• We enhanced our date range recognition in One AI Assistant to allow for simultaneous selections and filters like “show me headcount by month for 2023”. We also improved month name recognition for prompts including date ranges like "for Apr 2024 to Mar 2025". (ref 4033)

User Experience Improvements

• You can now freeze columns in List Tables to keep them visible while scrolling horizontally. This helps maintain context and navigate large datasets more easily. The new Freeze Columns setting is found under Design > General. For basic list tables, you can freeze any number of columns, and for pivoted list tables, you can freeze non-value columns. (ref 25399)

• The Waterfall Chart now applies a digital separator to the "comparison value" for consistent metric formatting. (ref 25365)

Data Platform Innovations

SQL Explorer

• We are proud to announce that SQL Explorer is now Generally Available! This functionality lets users run SQL Statements directly on any data within their environment for exploration or debugging purposes (ref 25555)

Entity Relationship Diagram (ERD)

• We are also proud to announce that our Entity Relationship Diagram (ERD) is also Generally Available! This functionality in the Admin Reports page allows users to view all of the Fact and Dimension tables within their instance, and how the relationships are defined between them, giving a high-level overview of the Data Model (ref 25555)

Data Integration Improvements

• We improved user experience at API runs page, making it significantly easier to find specific tables and view their row counts during a workday full extraction. To do this we removed the S3 path column from the task display, as it was not useful and cluttered the interface. This change eliminates the need for horizontal scrolling or dialog resizing. (ref 25236)
• The team restored the functionality of the wrench button and the delete button for the delimited file inputs on the API data sources, as these buttons had not been working recently. (ref 25697)
• We fixed an issue at the API runs page where selecting destructive from the type drop down does not exclude non-destructive API runs. (ref 25514)

Minor Improvements & Bugs Squashed

• We resolved a bug with topic identification not always working for One AI Assistant Answers. At times a specific answer would be selected over a list of questions when requesting “What questions can you answer about X?". (ref 4045)
• We fixed a small bug where the forecasting numbers in Storyboard charts didn’t have all of the correct number formatting applied. (ref 25497)
• Fixed an issue where string field sizes might not be getting calculated correctly if a Date field was used. (ref 24663)
• Fixed an issue where the ERD Admin Report would not build for companies who had never run Modular Processing. (Ref 25772)
• We have fixed how 'Notifications' and the 'Proxy as User' feature interact. The underlying logic has been resolved for Data notifications and they now correctly remain specific to the intended user, even when using the Proxy as User feature, preventing configuration conflicts. (Ref 24714). 
• Due to the issue with data notification logic described above, we had temporarily blocked the Proxy as User feature specifically for Storyboard Notifications as a safeguard against potential misconfigurations.  Now that the underlying logic is fully resolved, we have removed this temporary block. The Proxy as User feature can now be correctly used to configure Storyboard Notifications on behalf of another user. (Ref 24145)