Release Notes - 2026.04.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 1st April 2026.

User Experience Improvements

• We have enhanced the Insight Library to make it a more streamlined and integrated part of your daily productivity. Previously a central storage repository, the library now allows you to move from individual insights to a finished Storyboard with fewer clicks, regardless of where you are in the app.  

  Key improvements include:
   

  • Global Navigation: You can now open the Insight Library from anywhere using the new icon in the main navigation bar. This eliminates the need to jump between pages to find a saved query.
  • Multi-Select Support: You are no longer limited to selecting one item at a time. Use checkboxes to select multiple insights, or entire categories, to add to your Storyboard at once.
  • Simplified Storyboard Creation: To speed up productivity, you can now select a group of insights and choose Generate New Storyboard. The system will automatically create, name, and lay out your Storyboard tiles instantly (ref ).
     

• The KPI Chart with Insights is now Generally Available, moving from closed beta to a standard feature within Storyboards. This visualization highlights a single, high-impact metric alongside change tracking and trend lines, bridging the gap between high-level vision and strategic execution. It enables leaders to move swiftly from observing a number to understanding its organizational impact.
  
  Beyond the visuals, the KPI Chart integrates AI-driven Auto or Custom Insights directly into the tile. Users can leverage generative AI by defining specific personas, such as a Senior People Analytics Consultant or HRBP, to focus analysis on financial risk, root causes, or retention tactics. This consultative approach ensures every stakeholder receives a tailored, scannable, and high-value perspective directly within their dashboard.
   

Data Ingestion Innovations

• Added support for configuring the same query parameter as both destructive and incremental (ref 27165).
• Fixed an issue where batched loading errors were not visible on the API Runs page (ref 27135)
• Added features to enable and disable API endpoints, making it easier to set up Greenhouse V3 in the Generic API Connector (ref 25244).
• Added response element pivot configuration to the Universal Connector data source configuration (ref 26434).

Minor Improvements & Bugs Squashed

• Improved the loading performance of the Data Access Roles (DAR) rules popup for large dimensions. Previously, the popup would load the entire dimension tree — including all levels and paths — and return it to the client at once. This could result in slow load times and unresponsive browser behavior for dimensions with large amounts of data. The popup now loads data progressively as the user navigates the dimension, significantly reducing load times and improving browser responsiveness (ref 26623).

• We've fixed an issue where the 'Data limit reached' warning (previously 'Query too large') was appearing twice on saved charts. This occurred specifically when refreshing a List Table with 'Expand/Collapse Rows' enabled. The warning will now correctly appear only once, providing a cleaner and more efficient loading experience (ref 27481).
   
• We fixed an issue in Processing scripts where the Override clause was not setting the Data Type correctly on Fact and Dimension tables (ref 27080).
   
• Fixed a vague error message shown when an invalid decimal was entered in the "Period" field of a Number Range variable (ref 27297).
   
• Fixed an issue where no error message was displayed when validation errors were hidden inside collapsed sections during an Update operation (ref 27286).
   
• Fixed an incorrect validation message under Key Path, which displayed "At least 1 key required" instead of correctly indicating that a Value was required (ref 27285).
   
• Fixed an issue in the Generic API Connector where the "Clear Row" (X) button was clearing the following row's field instead of the intended row (ref 27270).
   
• Made the consolidation poller idempotent when a multipart upload completion fails (ref 26956).