The lvsrvr.cfg file has undergone multiple updates in this version:

The following parameters have been removed and are now stored in the database. These items should now be set in the Longview Server Manager:

• DIAGNOSTIC_SERVICE_TRACKING

• DIAGNOSTIC_SERVICE_DETAIL

• DIAGNOSTIC_SERVICE_LOGGING

• DIAGNOSTIC_QUERY_STATISTICS

• DIAGNOSTIC_QUERY_LOGGING

• DIAGNOSTIC_RDBMS_LOGGING

• DIAGNOSTIC_EVENT_PROFILING

• ENABLE_WEB_TRACE

• USE_DATA_AUDIT_TRAIL

The following parameters have been removed as they are no longer configurable. These log files will always be saved in the corresponding log folder in the data server’s custom folder location:

• EVENTS_LOG_FILES_LOCATION

• EVENTS_ERROR_FILES_LOCATION

• EVENTS_HISTORY_FILES_LOCATION

• METADATA_AUDITTRAIL_LOGFILES_LOCATION

• WEB_TRACE_FILE_LOCATION

The following parameters have been removed as they are now obsolete:

• USE_HTML5_DASHBOARD

• USE_FILE_ATTACHMENT

For more information, see the Administrative Server Tasks online documentation.

The user command in the Longview Administrator console now supports Longview Single Sign-On using the Oauth2 flow using the following syntax:

user <clientID> <secret> SSO [scope]

For example:

user 4c796c6b-21u5-463b-8ddd-c5839e5c41e7 qPa-pz0D8mgi4zDZRR2E SSO

For more information, see the Administrative Server Tasks online documentation.

The maximum value for DATA_FETCH_SIZE has increased to 1,024,000 and the default value is now 96,000. Setting this parameter to a higher size improves the performance of querying data audit trail.

This feature is available exclusively for Longview customers who are ISW platform enabled. The ISW Platform now supports multi-environment licensing. Longview will utilize this feature so that each environment (e.g., Production and Testing) will match the corresponding environment in the platform. Licenses will no longer be shared at the product level but will be matched to the specific environment. Only the production environment will use the license count.

Longview Server Manager will now prompt users to change their passwords as required by the system's password policy.

The Longview Server Manager Logs page has been expanded to include additional log files. New tabs have been added for Event, REST API, Install, and Metadata audit log files. Additionally, the logs page now supports tree structures for logs that have folder structures within them, providing a more organized and intuitive way to navigate the log files.

Users can now clear the data audit trail based on a dimension symbol. This feature allows the removal of obsolete leaf and schedule data audit trail from the database for all intersections of data containing the specified symbol.

Additionally, the option to reset the data audit trail is now available in Longview Server Manager. For more information see Longview Server Manager online documentation.

Note: Users can also clear data audit trail based on a dimension using the Longview Administrator console. For more information see Administrator Server Tasks online documentation.

Users can now clear data and event area monitoring through Longview Server Manager. For systems using data area monitoring, when the data and event area monitoring becomes too large, users could experience performance issues while opening reports. Clearing the data and event monitoring may help with the performance. For more information see Longview Server Manager online documentation.

Note: Users can also clear data and event monitoring using the Longview Administrator console. For more information see Administrator Server Tasks online documentation.

Pillar Two temporary differences now include regional accounts, and national accounts now include regional impacts in the net per provision amounts.

In Pillar Two, a new input app for capturing direct ownership between entities has been added. The ownership percentages are used to derive the effective ownership between entities which is used to apply the income inclusion rule.

In Pillar Two, a new calculation has been added to derive the effective ownership of one entity in another. This is used as part of the application of the income inclusion rule.

In Pillar Two, a new app has been added to indicate whether the ownership interest of the UPE or an intermediate parent entity constitutes a controlling interest. This setting is used in instances where the income inclusion rule is applied to an intermediate parent.

When importing an export created with the AffectedOnly option, tables not included in the export were truncated.

The Longview LVMGRL USER command would not be executed if any previously executed commands in the LVMGRL session encountered errors.

For some systems hosted in the Longview Cloud, running a rollover in Longview Tax would cause a lvagent.exe to crash.

In some cases, systems hosted in the Longview Cloud experienced a server crash when updating the server configuration from the Longview Server Manager.

The title of the French default dashboard displayed incorrect characters for some systems hosted in the Longview Cloud.

The Longview Developers documentation did not include information about the EXTERNAL parameter for the LogFile and ErrorFile functions.

Schedule reports that did not include the schedule in the down or across dimension caused errors when exported to Excel in table format.

In the Longview Server Manager Logs tab, the delete button was available on the lv_dataserver.log file.

The Countries editor would report an error when the Submit button was clicked with an Oracle database.

The hierarchies for Statutory and Consolidated National Effective Tax Rate reports have been adjusted to match the Loss, Tax Credit, and Other Accounts editor for IAS.

The Multi-Regional Partnership Calculation for IAS now correctly includes a comment for data submissions.

The Multi-Regional Provision Regional Adjustments Automation (ASC and IAS) now includes partnership entities.

Regional accounts have been removed from the National Current Tax Account report (NA1602) for IAS.

Net national recognised acquisition elements were not being calculated in Multi-Regional provision for IAS.

Net regional recognised acquisition elements were not being calculated for regional Consolidated Income groups in Multi-Regional provision for IAS.

The national rate change calculation in a Multi-Regional provision system was not using the parent value of the perm/temp difference accounts when referencing the opening and end of year elements to determine the tax rates to apply.

The Multi-Regional provision rate differential event would fail when triggered by a large number of accounts in ASC.

The Multi-Regional provision group consolidation adjustment deferred tax event would fail when triggered by a large number of accounts in ASC and IAS.

Two corrections were made to the ASC 740 Disclosure workbook: In the Amount columns, the formula for "U.S. Federal Statutory Tax Rate" was corrected to "Total_Countries" for ENTITIES and "ASC740_TOTAL" for CONTROLS, and the formula for Effective Tax Rate was corrected to be a sum. In addition, a new version of the workbook was deployed as a template which includes some other enhancements to the workbook to ease the initial configuration. You can find the new workbook "ASC740 ETR Disclosure_Template.xlsx" in the disclosures folder of your custom file location.

In Manage ETR Disclosure Accounts app, a cycle of errors could be created when modifying symbols that have changes applied using Apply button, but the editor has not been refreshed.

ASC 740 Disclosure has been corrected to use Tax Effect (Consolidated) (NetNTaxEffectC_ASC) instead of Current Year (GrsCY_ASC) as its source.

The IAS Multi-Regional provision rate reconciliation calculation would fail if it was triggered by data submitted to a numerical symbol in the details dimension.

When using a manage hierarchy app, clicking the X to close the parent assign confirmation would result in an error. This action is now considered to be cancelling the parent assign.

SQL Server 2022

SQL Server 2019

Oracle 19c

.NET 4.8

Office 365 – 32-bit and 64-bit

Excel 2021 – 32-bit and 64-bit

French Windows

French Microsoft Office

Oracle JDK 17 (LTS)

Oracle JDK 21 (LTS)

OpenJDK17

or

OpenJDK 21

French

English

English

The last version of Longview that will be supported on Windows Server 2019 will be 26.1 (January 2026).

In line with Microsoft EOL of Windows 10, Longview will only support Windows 10 LTSC 2021 (21H2) as of October 14, 2025.

February, 2025

July, 2025

February, 2026

April, 2026

July, 2026

October, 2026

February, 2027

February, 2027

May, 2027

July, 2027

October, 2027

January, 2028