We’re ending 2025 with the 7th release of InVision this year. The release primarily contains a number of small but important enhancements across the board. The 2025.7 release also includes important security patches and a number of new APIs enabling automation through Flow.
AppHeader Notifications component
The AppHeader Notifications component enables showing a notification icon in the Workbook application header when the logged in user has unread chat messages. The user can then click the icon to view and read the messages.
Read more here
Popout Forms control
The new Popout control enables showing or editing data relative to another control inside a Form. For example, clicking a button can display a Popout to its right containing details about a customer or product. The addition of the Popout control makes it easier to build more advanced Forms-based workflows which require showing or editing data in popouts / popups.
Read more here
Dimension properties can be specified as required (mandatory)
Solution developers can now specify dimension properties as required. This will force the user to specify a value before new dimensions members, or changes to existing dimension members, can be saved. This feature is useful when there is business logic associated with dimension properties, and there is no good default value to apply.
Parameterization of OpenSpreadsheetEditor
InVision has had a hidden gem for over 10 years – the OpenSpreadsheetEditor API – which enables editing data in any table by simply providing the table ID. Initially designed for a scenario where filtering was not required, there was no option to specify filter arguments. In 2025.7, we’ve extended the OpenSpreadsheetEditor API to support passing in filter arguments as a JavaScipt object. Note that this means that this API is only supported when using JavaScipt (and not Eaze) as the programming language for Workbook component instructions.
Read more here
Support for Display Order expression in table columns
The Display Order expression allows columns in tables and reports to be positioned dynamically based on parameterized expressions. This provides even more flexibility for configuration of standard products on InVision without requiring customer-specific customizations.
Read more here
Table Explorer improvements
The Table Explorer enables customers to quickly browse and edit all parameters for the products on the CFO platform (like Budgeting and Forecasting). InVision 2025.7 adds a few more features to make the Table Explorer even easier to work with.
Close editors from the table list
A small but useful improvement to the Table Explorer is the ability to close open editors directly from the table list, rather than from the table toolbar. This makes it easier to quickly browse data, such as financial parameters, in large solutions like budgeting and forecasting (due to much less mouse pointer travel).
Support for dynamic tag filters
A budgeting and forecasting solution with all features enabled can have several hundred configurable parameters. In practice, however, customers rarely enable all features from the outset. A new capability for solution developers allows tag filters to be set dynamically when a Table Explorer loads, so that only tables (and parameters) related to enabled features are listed. This makes it easier for customers and partners to learn, set up, and operate solutions such as Budgeting and Forecasting, Risk Management, and Consolidation.
.NET 10 upgrade
InVision has been updated to the latest version of .NET, released in late November. The update improves performance and reduces memory usage. Solution developers can now use C# 14 and the latest .NET 10 APIs when writing Web Functions.
New SDK libraries for Package development published to NuGet
New SDK libraries for package development have been published to NuGet. Package developers must upgrade their .NET package projects to use the new SDK for packages targeting 2025.7 or later.
Breaking changes – important!
This change applies to all on-premise customers and customers using their own Entra ID for authentication
For SaaS customers using their own Entra ID
SaaS customers using their own Entra ID for authentication must update their Entra ID app registration for InVision.
- Log on to the Azure portal
- Go to Microsoft Entra ID -> App registrations
- Find and open the App registration for the InVision web app
- In the left menu, go to Manage -> Manifest
- Locate the “api” section and change requestedAccessTokenVersion from null to 2 and save
For On-premise customers
Before upgrading InVision to 2025.7, upgrade the Installation Manager to the latest version first.
When upgrading on-premise installations to 2025.7 or later, and you are using Microsoft Entra ID for authentication, you must now specify a scope in the Installation Manager before starting the upgrade.
Follow these steps:
- Log on to the Azure portal
- Go to Microsoft Entra ID -> App registrations
- Find and open the App registration for the InVision web app
- In the left menu, go to Manage -> Manifest
- Locate the “api” section and change requestedAccessTokenVersion from null to 2 and save
- In the left menu, go to Manage -> Expose an API
- Find the scope, listed under Scopes. Copy and paste the name into the Installation Manager (and save) before running the upgrade.
- When you start the Designer to log on to the Solution, modify the connection and provide the Scope name there as well. You can also go to the /Designer page in the browser and copy the connection information from there.
That’s it for now!
Merry xmas and happy new year!