Longview now provides an alternative deployment option to ClickOnce using the Enterprise Deployment package. This allows customers to install and upgrade Longview Components using an .msi installer.

For more information, see the Longview Enterprise Deployment Guide.

Longview now supports SQL Server 2022.

Users can now choose to clear previous results when rerunning a Data Extract query.

A new option has been added to the Data Extract query to separate string and numeric data into separate columns.

This option was also added to the API.

For more information, see the Longview Add-In for Office Guide.

In some cases, when installing Longview on the platform, the installer would encounter a “VCRUNTIME140.dll was not found” error.

When installing Longview on the platform, not all files were properly cleaned up after the install completed.

When installing Longview on the platform, the installer did not check to ensure the user installing was already in the local group specified, which would result in the install not running the solutions code.

The Back button on the Ready to Install step of the Longview Installer did not work.

When connecting to Tidemark in Longview Add-In for Office, the user’s member access was not automatically updated after being modified in Tidemark Data Security Profile.

The “Levels” label in the SymbolSelector and SymbolSpecSelector function builder were not displaying correctly in French.

Using Longview Application Framework to delete a rule that did not exist would cause the server process to crash.

In some cases, a template lvsrvr.cfg file was created when running the start.bat.

Temporary files created during the server import process were not deleted after a successful import.

Event rules with delays were being calculated from the moment the event was triggered, not when the event was previously run.

In some cases, users that belonged to multiple platform organizations were unable to connect to Longview for Longview systems on the platform.

The Longview server process would crash if a “recalc audit reset” was issued while the servers were not started.

In some cases, the database reconnect for SQL Server would crash lvagent.exe.

In non-partitioned systems, the restatement would fail if no journal entries existed when USE_DATA_CACHE was set to FALSE.

When the recalc folder was in a different location other than the default, Longview Server Manager would error when launching.

In some cases, Longview Server Manager would display error messages with an exception report.

The Longview Sever Manager was creating a local copy of the lvsrvr.cfg file.

When a sort order was entered that was greater than the valid maximum value, the row would no longer be displayed in the data table.

In some cases, the Ellipse button did not appear on the toolbar to be able to get to the additional buttons that were not displayed on the toolbar.

When the wrapping for the row header was enabled in a data grid, the minimum row height was less than the default height.

In some cases, a data grid would not render correctly when a parent symbol was disabled.

When starting the servers using an Oracle database an "Unable to determine table structure for SLNS_JE_DETAIL" warning would be reported. This warning had no impact on functionality.

When selecting a specific user that was using windows authentication in the User Access or Effective User Access reports no results were displayed.

In a system with no currency dimension specified via system attribute SGPCurerncyDimension, a data view input app would fail with a "VARIABLEEXISTS: Requires additional parameters" error when executed.

In Longview Tax Multi-Regional Provision (IAS/IFRS), cases in which the opening balance of a temporary difference was zero, and/or the closing balance of a temporary difference was zero, would treat all activity in the account as unrecognised. In this case the activity of the temporary difference is now fully recognised.

In Longview Tax Multi-Regional Provision (ASC/US GAAP), inputs XSC0501S - Deferred Tax Beginning Balance and XSC0501G - Deferred Tax Beginning Balance did not take into account the regional scheduling setting.

In Longview Tax Multi-Regional Provision (ASC/US GAAP), the initial expansion level for input apps XSC0501S - Deferred Tax Beginning Balance, and XSC0501G - Deferred Tax Beginning Balance has been updated to compensate for the hierarchy updates supporting deferred tax netting for regions.

In Longview Tax Multi-Regional Provision (ASC/US GAAP), the query rules for Regional Interim Current ETR - Manual Adjustment (RegIPETRCURA) have been updated to correctly function across all symbols in the DETAILS dimension.

In Longview Tax Multi-Regional Provision (ASC/US GAAP), the interim current and deferred was incorrectly filtering accounts under Regional Additional Provision Items - Not Currently Deductible (MSP_RegAddPrvNCD_ASC) at National Level and Regional Additional Provision Items - Not Deductible at National Level (MSP_RegAddPrvND_ASC) from the lock, causing the results of the calculations for these accounts to not be submitted to the database.

Installing or upgrading Longview Tax would deploy files to the templates folder in the data server working directory, even if custom files path was being used.

In Longview Tax Multi-Regional Provision (ASC/US GAAP), improved performance of Combined Deferred Tax Calculation - NBR and Combined Deferred Tax Calculation - Regional NBR events when triggered across a large number of details, segments, and currencies.

In Longview Tax Multi-Regional Provision (ASC/US GAAP), values entered in temporary differences for RAR - Deferred Only Impact (GrsRARDfd_ASC) and Other Adjustments - Deferred Only (GrsDfd_ASC) were not correctly flowing to the multi- regional Forecast Tax Expense (802) report and subsequently being omitted from the multi-regional ETR and Discrete Items Interim (803) report.

In Longview Tax Multi-Regional Provision (IAS/IFRS), the Regional Deferred Tax Impact - Change in Tax Rates ACQ PRIOR and Regional Deferred Tax Impact - Change in Tax Rates ACQ CUR elements were not being calculated for recognised deferred tax.

In Longview Tax Multi-Regional Provision (IAS/IFRS), recognised amounts related to regional acquisitions were not being calculated.

In Longview Tax Multi-Regional Provision (ASC/US GAAP), Regional Current Tax Expense/(Benefit) Before Discrete Items (RegIPCB4D) and Regional Deferred Tax Expense/(Benefit) Before Discrete Items (RegIPDB4D) were being calculated using apportioned net income before tax, causing the results to be understated.

In Longview Tax Multi-Regional Provision (IAS/IFRS), several combined tax elements were not configured correctly for the calculation of CTA. This is corrected in new installs only.

In a new install of release 23.2 of Longview Tax Multi-Regional Provision (IAS/IFRS), rule merge and dependency files were not deployed correctly.

In an installation of Longview Tax if the number of periods was set to a value other than 12 the system settings were not updated correctly requiring it to be manually updated afterwards.

When importing constituent entities via manage constituent entities an error would be reported if a constituent entity was changed from a Permanent Establishment to another type.

When the following input apps were opened in a period that did not contain election settings for jurisdictions, a "Cannot resolve variable" error would occur:

• P2200 - GloBE Income
• P2300 - GloBE Adjusted Covered Taxes
• P2310 - GloBE Temporary Differences
• P2510 - Top-up Tax

A database related error would occur when updating constituent entity settings in a time period if settings already existed in another time period, either manually or via import.

When importing jurisdictions via manage constituent entities an error would be reported if a jurisdiction's currency was not enclosed in square brackets.

Entity selections for Pillar Two process maps were using tax provision hierarchies rather than the Pillar Two total jurisdictions hierarchy.

In Longview Tax Provision (IAS/IFRS), cases in which the opening balance of a temporary difference was zero, and/or the closing balance of a temporary difference was zero, would treat all activity in the account as unrecognised. In this case the activity of the temporary difference is now fully recognised.

In Longview Tax Provision (IAS/IFRS), the following reports would report a "Not in GZIP format Report template was not published" error when attempting to publish them to additional groups:

• NA1503 - Consolidated Effective Tax Rate
• YCA1311 - Loss and Credit Expiration Schedule References
• YCA1312 - Utilization Schedule References
• YCC1601 - Tax Account Rollforward (TARF) References
• YNA1306 - Temporary Differences Recognised References
• YNA1503 - Consolidated Effective Tax Rate References

Installing or upgrading Longview Tax would deploy files to the templates folder in the data server working directory, even if custom files path was being used.

SQL Server 2022

SQL Server 2019 Oracle 19c

Microsoft IIS 10.0

Oracle JDK 17 (LTS), Oracle JDK 20 or OpenJDK 20

ODBC Driver 18 for SQL Server

.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 20 or

OpenJDK 20

French

English

English

All versions < 7.3

Versions 7.3 – 10.5

10.6

10.7

21.1

21.2

22.1

22.2

23.1

23.2

23.3