Longview v25.4 Software Release Notes
This document describes enhancements and changes to Longview version 25.4
Announcements
-
Comprehensive Pillar Two Enhancements: Longview 25.4 delivers significant BEPS 2.0 Pillar Two advancements, including:
- Excess negative tax elections under Article 4.1.5
- Additional top-up tax calculations for previous fiscal year adjustments at the GLoBE level
- Multi-currency threshold support for transitional safe harbours
- Updated GloBE temporary differences aligned to GIR
- Comprehensive CSV data extraction capabilities
- Platform Integration and User Experience: ISW Resource Center integration provides direct access to help resources within Longview Dashboard and Longview Client. Lineos (formerly AI Assistance) features updated branding throughout the platform.
- Productivity Tools: Longview Add-In for Office users can clear previous query results for cleaner datasets. System tool applications now include Export to Excel functionality. The Mappings Editor now includes override functionality allowing users to replace or append mappings during import operations.
- Enhanced Data Management and Security: Enhanced server error handling with timestamp-based logging improves troubleshooting efficiency. The Actian Connector has been modernized with secure framework updates eliminating known vulnerabilities.
insightsoftware continues to focus our efforts on providing the greatest value in our product investment. As part of this effort, we began an initiative in 2020 to deprecate certain features that were legacy in nature and could be replaced with newer components that offered greater functionality and improved user experience.
The following components are deprecated as part of the current release:
- Longview Legacy Non-HTML5 Dashboard: Deprecated as of version 25.2 now that cards on the HTML5 Longview dashboard can be manually or automatically refreshed.
- Third-party authentication: Deprecated as of version 25.3 as Longview now supports the Longview SSO service, which provides a more industry-standard approach to Single Sign-On authentication.
Enhancements Added in Longview 25.4
Longview v25.4 contains enhancements in the following areas:
- Longview Add-In for Office
- Longview Application Framework
- Longview Data Servers
- Longview Designer
- Longview Installation and Supported Platforms
- Longview Platform
- Longview Server Manager
- Longview Smart Client
- Longview Tax -- Pillar Two
Longview Add-In for Office
| Enhancement | Description |
|---|---|
| LV-13287 | Users can now choose to clear previous results when rerunning Data Query, Attribute Query, and Symbol Query in Longview Add-In for Office. |
Longview Application Framework
| Enhancement | Description |
|---|---|
| LV-12864 | The QuotedString function has been added to DataArea import and export to properly handle string values containing delimiters or special characters when exporting to CSV files. |
| LV-13132 |
A new command, RESOURCE RESET, has been added to the Longview Application Framework to clear all resources in memory. The resource bundle will be loaded again the next time it is accessed. For more information, see the Longview Developers Guide. |
| LV-13288 |
A new function, ISEXCLUSIVEON(), has been added to Longview Application Framework. This function returns 1 when exclusive mode is on and 0 when it is off. Example: Create Variable nExclusiveMode as Num Set Variable nExclusiveMode = ISEXCLUSIVEON() If $nExclusiveMode$ == 1 Show Message "System is in exclusive mode" End If For more information, see the Longview Developers Guide. |
Longview Data Servers
| Enhancement | Description |
|---|---|
| LV-13066 | Enhanced server error handling and logging capabilities have been added to improve troubleshooting efficiency. A server error log file (server_errors_<timestamp>.log) will now be created capturing the error that triggered the "servers have encountered errors" database status flag, and user-facing error messages have been improved to provide clearer guidance on reviewing error logs. |
Longview Designer
| Enhancement | Description |
|---|---|
| LV-13003 | Import and Export now support quoted strings when exporting from a data area. Data Area Export, Free Form App and Configuration Library templates have been updated to include this as an option. |
Longview Installation and Supported Platforms
| Enhancement | Description |
|---|---|
| LV-12959 | Longview data servers now start automatically after a server reboot in cloud-hosted environments. The data servers can still be manually stopped and started through LVMGRL, and the automatic startup functionality is preserved during system upgrades. |
| LV-13038 |
The Longview Installer now supports Windows Authenticated DBO for SQL Server databases. For more information, see the Longview Installation Guide. |
| LV-13144 | Windows Server 2025 is now supported for Longview Application Servers and Web Servers. |
| LV-13290 |
Longview now supports Oracle Java JDK 25 (LTS) and OpenJDK 25. Some Longview components require the Java JDK. The Java JDK must be configured before any of these components may be used. You must obtain a supported version of the Java JDK and place it in the appropriate folder of the Longview Data Servers. For more information, see the Longview Installation Guide. |
Longview Platform
| Enhancement | Description |
|---|---|
| LV-12153 | AI Assistance has been rebranded to Lineos throughout Longview, including updated icons and naming in the Dashboard, Longview Client, and Longview Server Manager. |
| LV-13053 | The Longview Actian Connector has been updated to replace Axis 1.4 with a modern, secure framework, eliminating known security vulnerabilities while maintaining all existing connector functionality. |
| LV-13091 | The Longview SSO Service now logs version and copyright information to the sso.log file during service startup, making it easier to identify the current SSO service version for troubleshooting and compatibility verification. |
| LV-13110 | The ISW platform Resource Center is now integrated into Longview Dashboard and Longview Client, providing Longview customers integrated with ISW platform seamless access to help resources, documentation, and support materials. |
| LV-13139 | Longview SSO Service now supports proxy server configurations through a new optional "proxy.url" parameter in config.json, enabling authentication in corporate environments that require all traffic to route through proxy servers. |
| LV-13229 | The Designer license in ISW platform-integrated systems now includes the Server Manager and Server Manager - Stop/Start Toggle Dynamic Calculations authorizations, enabling them to run restatements without requiring separate administrator license. |
Longview Server Manager
| Enhancement | Description |
|---|---|
| LV-13085 | Restatement error logs are now accessible in Longview Server Manager, providing administrators with easier access to troubleshooting information. |
Longview Smart Client
| Enhancement | Description |
|---|---|
| LV-13052 | The Mappings Editor now includes an Override option when importing mappings. Users can choose to override, which deletes all existing mappings and replaces them with imported mappings, or append, which adds imported mappings to existing ones. |
| LV-13286 | Export to Excel functionality is now available in the system tool applications: Data Locks, User Submissions, and Events. |
Longview Tax -- Pillar Two
| Enhancement | Description |
|---|---|
| LV-12160 | Pillar Two now supports excess negative tax election and calculation under Article 4.1.5. |
| LV-12637 | Pillar Two now supports allocation of top-up tax under UTPR. |
| LV-12645 | Pillar Two now supports additional top-up tax for previous fiscal year adjustments at the GloBE level. Support under QDMTT will be in a future release. |
| LV-12928 | The ability to extract Pillar Two data to a comma separated file format has been added. The extract process includes jurisdiction data, SBIE allocation details, transition year data, constituent entity data, income and tax allocation details, and ownership. |
| LV-12993 | The Transitional Safe Harbours across Jurisdictions app now uses either EUR or Reporting Currency Threshold when determining safe harbour for Revenue. |
| LV-12994 | The Transitional Safe Harbour adjustments app now uses the EUR or Reporting Currency Threshold when determining safe harbour for Revenue. |
| LV-12995 | Pillar Two thresholds are now available and can be translated when your reporting currency is not EUR. The revenue threshold is applied to the transitional safe harbour in EUR or in reporting currency if it is not EUR. |
| LV-13105 | Pillar Two temporary differences have been adjusted to align with the GIR, as follows:
|
Issues Resolved in 25.4
Longview 25.4 contains issues resolved for the following components:
- Longview Add-In for Office
- Longview Application Framework
- Longview Data Servers
- Longview Designer
- Longview Installation and Supported Platforms
- Longview Platform
- Longview Report Viewer
- Longview Server Manager
- Longview Tax
- Longview Tax -- Country by Country Reporting
- Longview Tax -- Pillar Two
Longview Add-In for Office
| Issue | Description |
|---|---|
| LV-6309 | The LVSymbolSelector function returned an access error when users did not have access to the parent symbol specified in the Sym_Spec parameter, instead of displaying only the symbols they had access to. |
| LV-13026 | Longview Add-In for Office would encounter unexpected errors when running a data query shown as cell references and "Exclude Zeros" set to Rows, Columns or Rows and Columns. |
Longview Application Framework
| Issue | Description |
|---|---|
| LV-13124 | Data Table export crashed when Auto header was used with a large number of columns. |
| LV-13257 | The Longview Application Framework RUN EXPORT command experienced significant performance delays when executing on large data areas. |
Longview Data Servers
| Issue | Description |
|---|---|
| LV-13182 | The password change dialog incorrectly listed the $ symbol as a valid special character when Password Complexity was enabled. |
Longview Designer
| Issue | Description |
|---|---|
| LV-12944 | Import and export specs in configuration libraries were missing fields required for named value fields. |
Longview Installation and Supported Platforms
| Issue | Description |
|---|---|
| LV-13082 | Longview Add-In for Office had unexpected upgrade behaviour when mixing Enterprise and ClickOnce deployments. |
Longview Platform
| Issue | Description |
|---|---|
| LV-12198 | When user synchronization was triggered by user sign-on in ISW platform-integrated systems, the metadata audit trail did not include the triggering user and IP address. |
| LV-12982 | Users that did not have Application Framework authorization would receive a 500 Internal Server Error for Longview REST API requests instead of the 403 Forbidden response. |
| LV-13006 | Users could not use Windows Authentication to connect to Longview Application Administrator and Longview Server Manager. |
| LV-13086 | When the dashboard was set to French, Longview administrative tools were opened using the operating system's language settings. |
| LV-13285 | Dashboard page failed to load when X-Content-Type-Options "nosniff" header was enabled. |
Longview Report Viewer
| Issue | Description |
|---|---|
| LV-12943 | When using Export to Excel in table format in Report Viewer, only the last column's data was fully exported for reports with nested across dimensions with multiple columns. |
Longview Server Manager
| Issue | Description |
|---|---|
| LV-12948 | Longview Server Manager failed to auto-connect when launched from the dashboard if the port or location of the web bridge had been changed. |
Longview Tax
| Issue | Description |
|---|---|
| LV-12820 | When using Chart of Accounts Structure in Tax Import and Export or using Manage Trial Balance, new accounts will now be consistently applied to the writable and translation hierarchies. |
| LV-12856 | In a Multi-Regional Provision system, the MRP Deferred Tax Deductible calculation classified all regions as non-deductible after a rollover. |
| LV-12951 | In systems originally implemented prior to 10.1, the attribute to transfer reporting currency only adjustments to the tax account roll forward in reporting currency was not set correctly. |
| LV-13000 | Corrected a case where MRP TARF mappings were being applied to a non-MRP ASC system, generating an import error file. Under normal circumstances, this would not cause any issue with an upgrade or installation completing successfully. In addition, in an MRP system, the mappings were being applied before the symbols were created, which could cause an issue on a new installation of an ASC MRP system. |
Longview Tax -- Country by Country Reporting
| Issue | Description |
|---|---|
| LV-12862 | When the relevant country was not supplied in CbCR Table 3, it would be erroneously filled with the language code when the table was refreshed or opened. |
| LV-12888 | When a constituent entity is included for CbCR and has no override set for the issuing country, the resident country code is now used in the extract. |
| LV-12903 | Parents have been removed from the CbCR Table 2 reports. |
| LV-13258 | When pass-through was used for the details or segments dimension, a validation error would occur when saving automation settings in the Country by Country Automation editor. |
Longview Tax -- Pillar Two
| Issue | Description |
|---|---|
| LV-12616 | The income inclusion rule calculation would fail with an error if the ultimate parent entity was not defined, it is now fixed to report the issue in the event log instead of failing. |
| LV-12804 | An issue would occur if Pillar Two 25.2 had been deployed on tax provision version 25.1 or older when tax provision was subsequently upgraded to 25.2 or later and the regional temporary difference symbol (REGTEMP) was a leaf symbol. |
| LV-12821 | The Total Regional Tax Attributes and Total Regional Valuation Allowance accounts were missing from the Temporary Difference structure during Pillar Two upgrade. |
| LV-12855 | When adding a jurisdiction in Pillar Two, the calculation symbol was incorrectly added to the translated entities hierarchy. |
| LV-12887 | If the ultimate parent entity was not set, the Manage Constituent Entity and Export Constituent Entity Elections would fail. |
| LV-12917 | The time period selection has been removed from Manage Constituent Entities as it is no longer required as all time sensitive settings have been removed. |
| LV-12933 | The QDMTT covered taxes input app would display an incorrect value when rolling up a change that affected the total deferred tax adjustment amount. |
| LV-12975 | Newly added constituent entities and jurisdictions would be excluded from calculations unless the elections for these new entities were set. Constituent entities and jurisdictions now default to be included in calculations. |
| LV-12984 | Clicking Submit after closing Manage Jurisdiction Elections or Manage Jurisdiction Election Years app with unsaved changes would result in an error. |
| LV-12996 | When foreign exchange is enabled in Pillar Two, top-up tax would not be allocated to constituent entities. |
| LV-12997 | In some specific cases involving multiple currency changes, an error would occur when applying changes to constituent entities. |
| LV-13059 | The compliance period rollover step for ETR and Top-up tax percentage has been updated to correctly copy these values for jurisdictions. |
| LV-13131 | An upgrade to Pillar Two would fail when Tax Provision was on a version earlier than 25.3. |
Hardware and Software Requirements
This chapter contains information on these main topics:
- Supported Server Platforms
- Supported Client Platforms
- Upcoming Unsupported Server and Client Platforms
Note: Third party components and versions, such as operating systems, browsers, etc., no longer in support by the third-party provider are not supported by Longview as well.
Supported Server Platforms
Supported platforms are defined as the Operating System and RDBMS "families", and minimum patch/point level on which the application is supported under the terms of the Customer's maintenance Services Agreement. Assistance with issue investigation and resolution is available through Support Services. Any platform related software issues identified will be addressed based on Longview's standard issue prioritization criteria.
Longview reserves the right to end support for supported platforms with subsequent releases of the application.
Should a customer choose to use current versions of Longview software on non-supported platforms, Longview will continue to provide the application support under the terms of the Maintenance Services Agreement with the following exceptions:
- Issues encountered which cannot be replicated on a currently supported platform will not be addressed.
- For issues that exist on both supported and non-supported platforms, fixes will be verified only on supported platforms and may or may not address the issue on the non-supported platform.
- No support is available for platforms (OS or RDBMS) that are no longer supported by their respective vendors.
This section contains information on supported platforms for the following items:
- Updating Windows Universal CRT
- Data Server OS and RDBMS
- Web Server
- Data Server Web Services
- Longview Grid Server
- HTTP Proxy Server
Updating Windows Universal CRT
Improved security and compatibility of Longview means that older server machines must install Windows Universal C Runtime (CRT) update 2999226. You can determine whether your server requires this update and download this update, if needed, from the following link: https://support.microsoft.com/en-us/kb/2999226
Data Server OS and RDBMS
The following combinations are supported for all servers in the application. For details on the term Supported, see Supported server platforms.
| Server operating system (x64 architecture) | Server RDBMS (64-bit) |
|---|---|
| Windows Server 2025 | SQL Server 2022 |
| Windows Server 2022 |
SQL Server 2022 SQL Server 2019 Oracle 19c |
| Windows Server 2019 |
SQL Server 2022 SQL Server 2019 Oracle 19c |
Note: If you are using a separate Database server, any platform and Operating System supporting the database versions can be used.
Web Server
The following combinations are supported for the Web Server. For details on the term Supported, see Supported server platforms.
Note: The Web Server supports only x64 Server hardware architecture.
| Server operating system (64-bit) | Web Server (64-bit) |
|---|---|
| Windows Server 2025 | Microsoft IIS 10.0 |
| Windows Server 2022 | Microsoft IIS 10.0 |
| Windows Server 2019 | Microsoft IIS 10.0 |
Data Server Web Services
The following combinations are supported for Data Server Web Services. For details on the term Supported, see Supported server platforms.
Note: Data Server Web Services supports only x64 Server hardware architecture.
| Server operating system (64-bit) | Java |
|---|---|
| Windows Server 2025 | Oracle JDK 21 (LTS), OpenJDK 21, Oracle JDK 25 (LTS) or OpenJDK 25 |
| Windows Server 2022 | Oracle JDK 21 (LTS), OpenJDK 21, Oracle JDK 25 (LTS) or OpenJDK 25 |
| Windows Server 2019 | Oracle JDK 21 (LTS), OpenJDK 21, Oracle JDK 25 (LTS) or OpenJDK 25 |
Note: Apache Tomcat is deployed as part of the Data Server Web Services install process. If you have already installed Apache Tomcat, you must have version 9.0.102 installed.
Longview Grid Server
The following combinations are supported for the Longview Grid Server when Grid Processing Type is selected in Longview Server Manager. For details on the term "Supported", see Supported server platforms.
Note: Longview Grid Server supports only x64 Server hardware architecture.
| Operating system (64-bit) | ODBC |
|---|---|
| Windows Server 2025 | ODBC Driver 18 for SQL Server |
| Windows Server 2022 | |
| Windows Server 2019 |
Note: You must install the ODBC Driver 18 for SQL Server on the grid node that corresponds to the RDBMS that the Longview application server is configured for.
HTTP Proxy Server
The following combinations are supported for the HTTP Proxy Server. For details on the term Supported, see Supported Server Platforms.
| Server hardware | Server operating system (64-bit) |
|---|---|
| x64 Architecture |
Windows Server 2025 Windows Server 2022 Windows Server 2019 |
Note: You must have .NET 4.8 installed to run HTTP Proxy Server.
Supported Client Platforms
This section contains information on Supported platforms for the following items:
Longview Client Components
The following platforms are supported for client computers. For details on the term Supported, see Supported Server Platforms.
| Client operating system(64-bit) | Web browser | .NET version |
|---|---|---|
| Windows 11 |
Microsoft Edge Google Chrome1 |
.NET 4.8 |
Note:
- Chrome browsers require a Chrome extension to automatically deploy and launch ClickOnce components. Alternatively, an organization can use Enterprise Deployment to deploy components via IT.
- Longview components require WebView2.dll which is part of Edge.
Important: Longview recommends a DPI display setting of 100%. Using a DPI mode other than 100% can cause display issues ranging from incorrect and inconsistent font sizes to interface elements not being visible on the screen.
Microsoft Excel
The following Microsoft Excel versions are supported.
Note: Both Microsoft Office and Microsoft Office 365 are supported; however, you must use the fully deployed version of Microsoft Excel to work with Longview Add-In for Office.
| Longview Add-In for Office |
|---|
| Office 365 -- 32-bit and 64-bit |
| Excel 2024 -- 32-bit and 64-bit |
| Excel 2021 -- 32-bit and 64-bit |
Supported Languages
Longview client components are language consistent. For example, for a French client system, this update supports the French version of the Longview client, with the default regional settings, running with the French version of the respective operating system, and the French version of Microsoft Office.
However, for the servers, this update supports English versions of the respective RDBMS, server operating system, or Web server, regardless of the client language.
The following table outlines the language requirements for your Longview system.
| English | French | |
|---|---|---|
| Windows requirements |
English Windows English Microsoft Office |
French Windows French Microsoft Office |
| Java |
Oracle JDK 21 (LTS) Oracle JDK 25 (LTS) OpenJDK 21 or OpenJDK 25 |
Oracle JDK 21 (LTS) Oracle JDK 25 (LTS) OpenJDK 21 or OpenJDK 25 |
| Web browser | English | French |
| Server operating system | English | English |
| RDBMS | English | English |
| Web server | English | English |
Upcoming Unsupported Server and Client Platforms
Server Platforms
| Platform | Note |
|---|---|
| Windows Server 2019 | The last version of Longview that will be supported on Windows Server 2019 will be 26.1 (January 2026). |
| Oracle | Longview will continue to support Oracle 19c until it's EOL of April 30, 2027, Oracle has still not announced the release date for Oracle 23ai for Windows. Longview is currently reviewing the future of ongoing support of Oracle. |
Client Platforms
| Platform | Note |
|---|---|
| Windows 10 | In line with Microsoft EOL of Windows 10, Longview no longer supports Windows 10 LTSC 2021 (21H2) as of October 14, 2025. |
| Microsoft Excel 2019 | In line with Microsoft EOL of Office 2019 extended support, Longview no longer supports Office 2019 as of Oct 14, 2025. |
Longview Support Schedule
- As of this release, only Longview version 22.2 and newer are supported.
- Longview 22.2 will no longer be supported as of February 2026.
- As of 24.1 our standard support life cycle will be 3 calendar years from the month of release.
See the table below for more details:
| Version | Release Date | End of Support |
|---|---|---|
| 22.2 | November, 2022 | February, 2026 |
| 23.1 | March, 2023 | April, 2026 |
| 23.2 | May, 2023 | July, 2026 |
| 23.3 | August, 2023 | October, 2026 |
| 23.4 | November, 2023 | February, 2027 |
| 24.1 | February, 2024 | February, 2027 |
| 24.2 | May, 2024 | May, 2027 |
| 24.3 | July, 2024 | July, 2027 |
| 24.4 | October, 2024 | October, 2027 |
| 25.1 | January, 2025 | January, 2028 |
| 25.2 | April, 2025 | April, 2028 |
| 25.3 | July, 2025 | July, 2028 |
| 25.4 | October, 2025 | October, 2028 |
For more information on any of the above updates, please contact your Customer Success Manager, Account Executive, or Longview Support.