Longview now supports Oracle Java JDK 21 (LTS) and OpenJDK 21.

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 Data Servers now allow the user to enter a name for an export, allowing multiple exports to be created. 

Example:

export TO Full_Export_Backup

When importing an export, you can now specify the export name that you want to import.

Example:

import systemdata FROM Full_Export_Backup

import data FROM Full_Export_Backup

For more information, see Longview Server Manager Guide.

ODBC connection resiliency is now enabled and used by the Longview Data Servers, taking advantage of the ODBC reconnection logic for systems using Microsoft SQL Server.

The Client IP address will now be recorded in the lv_dataserver.log for any connections made in the Longview Dashboard that are configured to use the Longview Proxy.

Longview Pillar Two now includes support for calculating the substance-based income exclusion for top-up tax, including:

• An input app to capture gross values, and adjustments for permanent establishments and other flow-through entities for the purpose of calculating the substance-based income exclusion.
• An input app to capture substance-based income exclusion rates.
• An app to manage the gross substance-based income exclusion account structure.
• An event to calculate the substance-based income exclusion amount applied to calculation of excess profit.

Longview Pillar Two now includes the ability to export and import automation settings for Income, Covered Taxes, and Temporary Differences.

Longview Pillar Two now includes the allocation of top-up tax to constituent entities under section 5.2.4 of the model rules. The allocation is supported by a report to review the results.

If the install or upgrade is unsuccessful but is unable to rollback, the log file will now contain a message to inform the user that the installation or upgrade was completed unsuccessfully.

The Longview Installer was limiting the Oracle System Host to only 12 characters. It will now allow up to 32 characters.

When Microsoft Office was upgraded from 32-bit version to a 64-bit version the Longview Add-In for Office would no longer run.

Typing fast in the textboxes and symbol selectors of the Longview Function Wizard would cause inputs to be missed.

The LVATTRIBUTE function returned a numeric value as a string.

Longview Add-In for Office was unable to connect to an older version of the Longview Data Servers where the files custom root path was not used.

When using the advanced symbol selector in the Data Query dialog, pressing the enter key to select a symbol would close the Data Query dialog and run the query.

The Longview Application Framework function IsMaintenanceUser()was not returning the correct value for users that did have access to turn maintenance on.

In some cases, Longview Application Framework would crash with an EXCEPTION_ACCESS_VIOLATION error after running a SYNCHIER command.

Event log files that were larger than 1MB were truncated when opened in the Longview Client.

Event logic was waiting for submission batches to complete before invoking sequencing logic.

Schedule dimension definitions did not include the root of the subtree when the schedule dimension was a mirror dimension.

The duplicates.out and <user>_<session>_duplicate.tmp files were still being created in the Longview Data Servers working directory.
These files are now created in the <FILES_CUSTOM_ROOT_PATH>/logs/duplicatedata directory and are now created as .txt files. In addition, these files can now be viewed in Longview Server Manager.

When switching between tabs in a Longview Data Table the filtering was lost.

The performance of the symbol selector was poor when working with large hierarchies.

Keyboard focus was lost after pasting values in a Longview Data Grid.

Navigation in the Longview Symbol Selector did not work correctly when using the keyboard arrow keys.

Searching in a Longview Data Grid would cause the data grid to become unreadable, when the found symbol was in a down dimension where the dimension column was too narrow to display the symbol.

User and group security reports no longer filter puser from selection or results.

If any maintenance that affected the number of rows in a user or group security report occurred, while the report was open, the number of rows would not be updated in the title text on a refresh.

The addresssType attribute has been added back to the address element for OECD XML as it was erroneously removed as part of an update to HMRC XML.

In Table 2 - Main Business Activities, if the submitted organization name contained a comma, the values in the report columns for Table 2 - Constituent Entity Information would be shifted.  This also applied to other columns allowing text entry such as address.

Corrected the output of the OtherEntityInfo element for OECD XML.

Corrected the output of the OtherInfo element to correctly output the language attribute only when the language of the information does not match filing language. Also corrected the attribute from xml:lang to language per the HMRC schema document.

In Longview Tax Multi-Regional Provision (IAS/IFRS), reporting currency only adjustments were not automatically impacting the Tax Account Roll Forward and Effective Tax Rate reports.

In Longview Tax Multi-Regional Provision (ASC/US GAAP), changing the end of year rate for a region would not trigger the calculation of the deferred tax rate change.

In Longview Tax Multi-Regional Provision (ASC/USGAAP) and (IAS/IFRS), several interim automation rules were being triggered on the current tax period (CYTAXPER) instead of the interim tax period (IPTAXPER), causing the events to be triggered, but not calculated, on a non-interim period. This has been corrected on new installs only. The affected rules are: 5006902, 5006912, 5006922, 5006932, 5006942, 5006952, 5006962, and 5006972.

In Longview Tax Multi-Regional Provision (IAS/IFRS), some ASC specific scenarios were deployed and activated. These would show up as skipped in the scenario rollover log.

A misleading blank error file was created when installing Longview Tax, related to publishing report template Z1000 - New Report Template.

In Longview Tax Multi-Regional Provision (IAS/IFRS), input app SS1599 - Reporting Currency Only Adjustments was displaying the national adjustment accounts instead of the regional adjustment accounts.

In Longview Pillar Two, automation calculations could fail to upload results if the last automation defined was set to not automate and had no target symbols defined.

In Longview Pillar Two, when an automation entity and/or group override existed for an account that had multiple specific targets for details, segments, elements, the override was not applied correctly.

In Longview Pillar Two, automation settings containing multiple source symbols in a dimension other than accounts, where one of the source symbols matched the target symbol would erroneously only include the values of the matched target symbol in the calculation.

In Longview Pillar Two, the Pillar Two Temporary Difference Net calculation would fail with an error when the calculation was applied to a large number of account symbols.

In Longview Tax Provision (IAS/IFRS), reporting currency only adjustments were not automatically impacting the Tax Account Roll Forward and Effective Tax Rate reports.

Longview Tax Provision showed errors when opening an editor after running a rollover.

In Longview Tax Provision (ASC/USGAAP) and (IAS/IFRS), several interim automation rules were being triggered on the current tax period (CYTAXPER) instead of the interim tax period (IPTAXPER), causing the events to be triggered, but not calculated, on a non-interim period. This has been corrected on new installs only. The affected rules are: 5006902, 5006912, 5006922, 5006932, 5006942, 5006952, 5006962, and 5006972.

A misleading blank error file was created when installing Longview Tax, related to publishing report template Z1000 - New Report Template.

In Longview Transfer Pricing, automation calculations could fail to upload results if the last automation defined was set to not automate and had no target symbols defined.

In Longview Transfer Pricing when an automation entity and/or group override existed for an account that had multiple specific targets for details, segments, elements, the override was not applied correctly.

In Longview Transfer Pricing, automation settings containing multiple source symbols in a dimension other than accounts, where one of the source symbols matched the target symbol would erroneously only include the matched target symbol in the calculation.

SQL Server 2022

SQL Server 2019

Oracle 19c

Microsoft IIS 10.0

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

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 21 (LTS)

or

OpenJDK 21

French

English

English

All versions < 7.3

No new versions

Versions 7.3 – 10.5

10.6

10.7

21.1

21.2

22.1

22.2

23.1

23.2

23.3