Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Longview v23.2 Software Release Notes

This document describes enhancements and changes to Longview version 23.2.

Release Notes - Longview 23.2 (Build 56165)

This document contains information on these main topics:

Announcements in Longview 23.2

  • In this release we have continued to add further BEPS 2.0 Pillar Two functionality to meet the new Global Minimum Tax reporting requirements.
  • Longview version 23.2 is certified with insight software’s platform. Current capabilities include:
    • user management
    • single sign-on
    • license management
  • With the platform, everything starts in one place. Our vision is that business users will have one place to sign-in, launch their applications, and to access learning and support resources.
  • We have introduced the ability to Activate and Deactivate users in this release. Deactivated users will not be able to sign on to Longview, however the user’s information and settings remain in the database and when the user is Activated, the user can sign on to Longview again.
  • The Longview applications continue to undergo significant rebranding to create a more modern look and feel, and to align our solutions and user experience with the broader solution set of insightsoftware. In this release we have focused on the Longview Data View Input apps.
  • From this release Longview Java files are digitally signed.

The Longview applications continue to undergo significant rebranding to create a more modern look and feel, and to align our solutions and user experience with the broader solution set of insightsoftware.

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. 

A recap of the recent decisions, the following features have been de-supported over the past few releases:

  • Longview Desktop – Version 10.7 (Fall 2020)
  • Longview Input – Version 21.1 (Spring 2021)
  • Longview Component Manager – Version 22.1 (Spring 2022)
  • Legacy Longview for Excel component – Version 22.1 (Spring 2022)

No additional components are deprecated as part of the current release.

In addition, we communicated the updated support schedule to coincide with the new version numbering that has been adopted by the Longview Product as part of our acquisition by insightsoftware.

To recap that schedule, see the following table:

Release Version

Calendar Release

Oldest Support Version

Version No Longer Supported

10.7

Nov-20

3.5.7

 

21.1

May-21

3.5.7

 

21.2

Nov-21

3.5.7

 

22.1

May-22

7.3

All versions < 7.3

22.2

Nov-22

7.3

No new versions

23.2

May-23

10.6

Versions 7.3 – 10.5

23.4

Nov-23

10.7

10.6

24.2

Apr-24

21.1

10.7

24.4

Oct-24

21.2

21.1

25.2

Apr-25

22.1

21.2

25.4

Oct-25

22.2

22.1

26.1

Feb-26

23.1

22.2

26.2 Apr-2623.223.1
26.3Jul-26 23.3 23.2

For more information on any of the above updates, contact your Customer Success Manager, Account Executive, or Longview Support.

Enhancements Added in Longview 23.2

Longview 23.2 contains enhancements in the following areas:

Installation and Supported Platforms

EnhancementDescription

LV-6423

Longview Java files are now digitally signed.

Longview Application Administrator

EnhancementDescription

LV-7458

Users can be deactivated in the Longview system. Deactivated users will not be able to sign on to Longview, however the user’s information and settings remain in the database. When the user is Activated, the user can sign on to Longview again.

For more information, see the Longview Application Administrator Guide.

Longview Application Framework

EnhancementDescription

LV-7458

New Application Framework commands, DEACTIVATE USER and ACTIVATE USER, have been added so users can be deactivated and activated in the Longview system using a Longview procedure.

Deactivated users will not be able to sign on to Longview, however the user’s information and settings remain in the database. When the user is Activated, the user can sign on to Longview again.

Example:

DEACTIVATE USER MScott

ACTIVATE USER JSmith

For more information, see the Longview Developers Guide.

LV-7713

A new system variable, LVS_FILESCUSTOMROOTPATH, has been added. This variable stores the path of the Files Custom Root Folder.

Example:

Create Variable sFilesCustomRootPath as String

Set Variable sFilesCustomRootPath = “The files Custom Root Path is $LVS_FILESCUSTOMROOTPATH$”

Show Message “$sFilesCustomRootPath$”

For more information, see the Longview Developers Guide.

Longview Platform

EnhancementDescription

LV-7458

Users can be deactivated in the Longview system. Deactivated users will not be able to sign on to Longview, however the user’s information and settings remain in the database. When the user is Activated, the user can sign on to Longview again.

For more information, see “Maintaining users and user groups” in the Longview Solutions Framework Admin Guide.

Longview Tax – Multi-Regional Provision

EnhancementDescription

LV-7434

In Longview Tax Multi-Regional Provision (IAS/IFRS), regional deferred tax calculations have been updated to be in line with ASC/US GAAP, including:

  • Updated deferred tax and rate change calculations;
  • Support for classification and netting.

Longview Tax – Pillar Two

EnhancementDescription

LV-7320

In Longview Pillar Two, calculations have been updated to calculate for jurisdictions excluded by de minimis or safe harbours, but force the top-up tax to be zero in these cases, in line with the pillar two model rules.

LV-7358

In Longview Pillar Two, automation has been added for GloBE temporary differences allowing you to automate adjustments to provision temporary differences for use in determining covered taxes.

LV-7631

In Longview Pillar Two, automation has been updated for GloBE income and GloBE covered taxes to skip calculation in cases where elections would block the target accounts from input.

Issues Resolved in Longview 23.2

Longview 23.2 contains issues resolved for the following components:

Installation and Supported Platforms

Issue

Description

LV-7974

The Longview Installer did not create the database log file when upgrading.

Longview Add-In for Office

IssueDescription

LV-1516

Longview Add-In for Office did not display the correct error message when an invalid symbol was entered in the LVLOCK function.

Longview Application Framework

IssueDescription

LV-1456

The memory allocation reported in the history file would change signs when hitting a memory limit during a model execution.

LV-7743

In some cases Longview Application Framework would crash when using the count() function on a large document that opened with a LOAD command.

LV-7767

A syntax error occurred when trying to resolve a user attribute with a user ID that started with a number and contained a hyphen.

Longview Data Servers

IssueDescription

LV-7308

When a user with no symbol access signed onto Longview the error that was displayed was not correct.

LV-7671

The Longview Servers were logging a misleading error message in the lv_dataserver.log file.

LV-7768

Journal Entry details for future periods were not generated for standard account type enteries.

LV-7854

The metadata audit trail message for removing all user authorizations was unclear.

Longview Designer

IssueDescription

LV-7819

The Filters table was not editable when the number of value fields in the import file is set to Single Value.

Longview Documentation

IssueDescription

LV-7815

The meaning of the symbol specification symbol### in the working with symbol specification section of the Longview Developers Guide did not explain the behavior when the symbol specified was a leaf symbol.

Longview Platform

IssueDescription

LV-6364

In Application Administrator, when the User Administrator Authorization was set, Symbol Access-Groups and Symbol Access - Users authorizations did not become disabled.

LV-6931

In some cases, when launching Longview Application Administrator or Longview Server Manager the initializing splash screen would take a long time to appear.

LV-7427

A blank file was opened when attempting to view import/export logs through Longview Server Manager.

Longview Smart Client

Issue

Component

Description

LV-1289

Data Tables

When a Data Table was shown in a sub window, the width and height parameters were ignored.

LV-7718

Report Viewer

In Report Viewer, column headers were not always aligned correctly after the report was refreshed.

LV-7776

Report Viewer

In some cases, Report Viewer would crash with the message “Exception has been thrown by the target of an invocation.”.

LV-7818

Form

In some cases, the symbol selector popup in a Longview Form would close unexpectedly when trying to select a symbol.

LV-7912

Data Grid

An "Out of memory" error was returned when loading a data view document that contained the LIDInputOnly function with no comment specified.

Longview Close

Issue

Description

LV-7658

Long module names were cut off in the Longview Modules and Settings menu.

Longview Solutions Framework

Issue

Description

LV-7202

Data GET and PUT REST APIs using a template would fail with a 404 not found error when file custom root path (FILES_CUSTOM_ROOT_PATH configuration parameter) was used, if the template file was not also located under the data server working directory,

LV-7610

In process maps, setting the same value for 'name' and 'description' of a process step would cause the description to be removed.

LV-7639

An event built using the Longview Designer event template would fail with an error if the system did not have a dimension for currencies.

LV-7769

In Longview Close, the roll period would not set the system attribute SGPCurrentYear correctly in a system that was not using journal entries.

LV-7955

During an upgrade, customizations to rules could be unintentionally overwritten with default rules.

Longview Tax – Multi-Regional Provision

Issue

Description

LV-6255

In Longview Tax Multi-Regional Provision (ASC/US GAAP and IAS/IFRS), tax credit year of expiry data is now correctly deployed during installation.

LV-6948

In some cases, 'Provision' could be added multiple times to the ASTaxRolloverScenarioTypes system attribute during an install or upgrade.

LV-6958

In Longview Tax Provision (ASC/US GAAP and IAS/IFRS) the following obsolete hierarchies have been removed for new installs:

  • CYRS (ENTITIES dimension)
  • BCDAYS (TIMEPER dimension)
  • MSGD (TIMEPER dimension)

LV-7739

In Longview Tax Multi-Regional Provision (IAS/IFRS), tax rates entered in 'XRC1201 - Tax Rates - Multi-Regional' were not pushed to the entity level when using the 'Regional' option for 'Regional Rates Input Level'.

LV-7771

In Longview Tax Multi-Regional Provision (IAS/IFRS), several elements were missing their exchange rate for foreign currency translation. This has been corrected for install only.

LV-7774

In Longview Tax Multi-Regional Provision (IAS/IFRS), the multi-regional deferred tax national gross transfer calculation was not transferring "Temporary Difference Classification Override" (TDCLASSOVERRIDE), "Short-term Recognisable in next 12 Months - Input" (GrsSTR_IAS_Input), and "Long-term Recognisable after 12 Months - Input" (GrsLTR_IAS_Input) to the regions, which could result in classification differences for temporary differences at the regional level.

LV-7797

In Longview Tax Multi-Regional Provision (IAS/IFRS), the multi-regional temporary difference classification calculation would fail with error when triggered by an entity with group nexus, if the regional group is a multi-currency group.

LV-7858

In Longview Tax Multi-Regional Provision (ASC/US GAAP and IAS/IFRS), several symbols were created with non-ascii characters in their descriptions which would cause issues connecting to Longview when regional settings is set to use a two-byte language for non-unicode programs.

LV-7946

In Longview Tax Multi-Regional Provision (ASC/US GAAP), the discrete items editor would assign protected accounts to the writable hierarchy, which could cause the Interim Apply Rates Calculation to fail with a lock conflict if any interim ETR input apps were open (NF0803, SSF0803 and SGF0803).

Longview Tax – Pillar Two

Issue

Description

LV-7120

If an error occurred during the installation of Pillar Two, re-running the installation process would not deploy Pillar Two correctly.

LV-7617

In Manage Constituent Entities you could get an inconsistent error message related to duplicate entity names depending on the steps taken to add a duplicate entity name.

LV-7618

In some cases it was possible to set a blank 'Main entity' for a constituent entity that was configured as a permanent establishment.

Longview Tax – Tax Provision

Issue

Description

LV-1623

In some cases, the Run Calculations button was disabled when valid settings had been selected in the Run Calculations editor.

LV-6255

In Longview Tax Provision (ASC/US GAAP and IAS/IFRS), tax credit year of expiry data is now correctly deployed during installation.

LV-6948

In some cases, 'Provision' could be added multiple times to the ASTaxRolloverScenarioTypes system attribute during an install or upgrade.

LV-6958

In Longview Tax Multi-Regional Provision (ASC/US GAAP and IAS/IFRS) the following obsolete hierarchies have been removed for new installs:

  • CYRS (ENTITIES dimension)
  • BCDAYS (TIMEPER dimension)
  • MSGD (TIMEPER dimension)

LV-7489

In Longview Tax Provision (IAS/IFRS), the deferred tax recognised event would fail with error in cases where it was triggered by multiple entities with no overlapping accounts.

LV-7658

Long module names were cut off in the Longview Modules and Settings menu.

Longview Tax – Planning

Issue

Description

LV-6930

In Longview Tax Planning, the Import and Export folder within the Administration category was displayed twice.

Longview Workflow

Issue

Description

LV-7687

In some cases, when creating or modifying hierarchical steps the process was able to be saved and activated with no symbol selected in the approval dimension.

Hardware and Software Requirements

This chapter contains information on these main topics:

Note: Third party components and versions, such as operating systems, browsers, etc., no longer in mainstream 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

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.

(x64 architecture)

Server RDBMS (64-bit)

Windows Server 2022

SQL Server 2019

Oracle 19c    

Windows Server 2019

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 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 2022

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

Windows Server 2019

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

 

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.16 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 2022

SQL Native Client 11.0

Windows Server 2019

SQL Native Client 11.0

Note: You must install the SQL Native Client 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 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

 

Windows 10

Microsoft Edge

Google Chrome1

.NET 4.8

 

Note: 1 Chrome browsers require a Chrome extension to launch ClickOnce components. For example, the Windows Remix ClickOnce Helper to launch Longview ClickOnce components.

Caution: 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 2021 – 32-bit and 64-bit

Excel 2019 – 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 17 (LTS)

Oracle JDK 20

or

OpenJDK 20

Oracle JDK 17 (LTS)

Oracle JDK 20

or

OpenJDK 20

Web browser

English

French

Server operating system

English

English

RDBMS

English

English

Web server

English

English

 

 

Published:

Longview v23.2 Software Release Notes

This document describes enhancements and changes to Longview version 23.2.

Release Notes - Longview 23.2 (Build 56165)

This document contains information on these main topics:

Announcements in Longview 23.2

  • In this release we have continued to add further BEPS 2.0 Pillar Two functionality to meet the new Global Minimum Tax reporting requirements.
  • Longview version 23.2 is certified with insight software’s platform. Current capabilities include:
    • user management
    • single sign-on
    • license management
  • With the platform, everything starts in one place. Our vision is that business users will have one place to sign-in, launch their applications, and to access learning and support resources.
  • We have introduced the ability to Activate and Deactivate users in this release. Deactivated users will not be able to sign on to Longview, however the user’s information and settings remain in the database and when the user is Activated, the user can sign on to Longview again.
  • The Longview applications continue to undergo significant rebranding to create a more modern look and feel, and to align our solutions and user experience with the broader solution set of insightsoftware. In this release we have focused on the Longview Data View Input apps.
  • From this release Longview Java files are digitally signed.

The Longview applications continue to undergo significant rebranding to create a more modern look and feel, and to align our solutions and user experience with the broader solution set of insightsoftware.

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. 

A recap of the recent decisions, the following features have been de-supported over the past few releases:

  • Longview Desktop – Version 10.7 (Fall 2020)
  • Longview Input – Version 21.1 (Spring 2021)
  • Longview Component Manager – Version 22.1 (Spring 2022)
  • Legacy Longview for Excel component – Version 22.1 (Spring 2022)

No additional components are deprecated as part of the current release.

In addition, we communicated the updated support schedule to coincide with the new version numbering that has been adopted by the Longview Product as part of our acquisition by insightsoftware.

To recap that schedule, see the following table:

Release Version

Calendar Release

Oldest Support Version

Version No Longer Supported

10.7

Nov-20

3.5.7

 

21.1

May-21

3.5.7

 

21.2

Nov-21

3.5.7

 

22.1

May-22

7.3

All versions < 7.3

22.2

Nov-22

7.3

No new versions

23.2

May-23

10.6

Versions 7.3 – 10.5

23.4

Nov-23

10.7

10.6

24.2

Apr-24

21.1

10.7

24.4

Oct-24

21.2

21.1

25.2

Apr-25

22.1

21.2

25.4

Oct-25

22.2

22.1

26.1

Feb-26

23.1

22.2

26.2 Apr-2623.223.1
26.3Jul-26 23.3 23.2

For more information on any of the above updates, contact your Customer Success Manager, Account Executive, or Longview Support.

Enhancements Added in Longview 23.2

Longview 23.2 contains enhancements in the following areas:

Installation and Supported Platforms

EnhancementDescription

LV-6423

Longview Java files are now digitally signed.

Longview Application Administrator

EnhancementDescription

LV-7458

Users can be deactivated in the Longview system. Deactivated users will not be able to sign on to Longview, however the user’s information and settings remain in the database. When the user is Activated, the user can sign on to Longview again.

For more information, see the Longview Application Administrator Guide.

Longview Application Framework

EnhancementDescription

LV-7458

New Application Framework commands, DEACTIVATE USER and ACTIVATE USER, have been added so users can be deactivated and activated in the Longview system using a Longview procedure.

Deactivated users will not be able to sign on to Longview, however the user’s information and settings remain in the database. When the user is Activated, the user can sign on to Longview again.

Example:

DEACTIVATE USER MScott

ACTIVATE USER JSmith

For more information, see the Longview Developers Guide.

LV-7713

A new system variable, LVS_FILESCUSTOMROOTPATH, has been added. This variable stores the path of the Files Custom Root Folder.

Example:

Create Variable sFilesCustomRootPath as String

Set Variable sFilesCustomRootPath = “The files Custom Root Path is $LVS_FILESCUSTOMROOTPATH$”

Show Message “$sFilesCustomRootPath$”

For more information, see the Longview Developers Guide.

Longview Platform

EnhancementDescription

LV-7458

Users can be deactivated in the Longview system. Deactivated users will not be able to sign on to Longview, however the user’s information and settings remain in the database. When the user is Activated, the user can sign on to Longview again.

For more information, see “Maintaining users and user groups” in the Longview Solutions Framework Admin Guide.

Longview Tax – Multi-Regional Provision

EnhancementDescription

LV-7434

In Longview Tax Multi-Regional Provision (IAS/IFRS), regional deferred tax calculations have been updated to be in line with ASC/US GAAP, including:

  • Updated deferred tax and rate change calculations;
  • Support for classification and netting.

Longview Tax – Pillar Two

EnhancementDescription

LV-7320

In Longview Pillar Two, calculations have been updated to calculate for jurisdictions excluded by de minimis or safe harbours, but force the top-up tax to be zero in these cases, in line with the pillar two model rules.

LV-7358

In Longview Pillar Two, automation has been added for GloBE temporary differences allowing you to automate adjustments to provision temporary differences for use in determining covered taxes.

LV-7631

In Longview Pillar Two, automation has been updated for GloBE income and GloBE covered taxes to skip calculation in cases where elections would block the target accounts from input.

Issues Resolved in Longview 23.2

Longview 23.2 contains issues resolved for the following components:

Installation and Supported Platforms

Issue

Description

LV-7974

The Longview Installer did not create the database log file when upgrading.

Longview Add-In for Office

IssueDescription

LV-1516

Longview Add-In for Office did not display the correct error message when an invalid symbol was entered in the LVLOCK function.

Longview Application Framework

IssueDescription

LV-1456

The memory allocation reported in the history file would change signs when hitting a memory limit during a model execution.

LV-7743

In some cases Longview Application Framework would crash when using the count() function on a large document that opened with a LOAD command.

LV-7767

A syntax error occurred when trying to resolve a user attribute with a user ID that started with a number and contained a hyphen.

Longview Data Servers

IssueDescription

LV-7308

When a user with no symbol access signed onto Longview the error that was displayed was not correct.

LV-7671

The Longview Servers were logging a misleading error message in the lv_dataserver.log file.

LV-7768

Journal Entry details for future periods were not generated for standard account type enteries.

LV-7854

The metadata audit trail message for removing all user authorizations was unclear.

Longview Designer

IssueDescription

LV-7819

The Filters table was not editable when the number of value fields in the import file is set to Single Value.

Longview Documentation

IssueDescription

LV-7815

The meaning of the symbol specification symbol### in the working with symbol specification section of the Longview Developers Guide did not explain the behavior when the symbol specified was a leaf symbol.

Longview Platform

IssueDescription

LV-6364

In Application Administrator, when the User Administrator Authorization was set, Symbol Access-Groups and Symbol Access - Users authorizations did not become disabled.

LV-6931

In some cases, when launching Longview Application Administrator or Longview Server Manager the initializing splash screen would take a long time to appear.

LV-7427

A blank file was opened when attempting to view import/export logs through Longview Server Manager.

Longview Smart Client

Issue

Component

Description

LV-1289

Data Tables

When a Data Table was shown in a sub window, the width and height parameters were ignored.

LV-7718

Report Viewer

In Report Viewer, column headers were not always aligned correctly after the report was refreshed.

LV-7776

Report Viewer

In some cases, Report Viewer would crash with the message “Exception has been thrown by the target of an invocation.”.

LV-7818

Form

In some cases, the symbol selector popup in a Longview Form would close unexpectedly when trying to select a symbol.

LV-7912

Data Grid

An "Out of memory" error was returned when loading a data view document that contained the LIDInputOnly function with no comment specified.

Longview Close

Issue

Description

LV-7658

Long module names were cut off in the Longview Modules and Settings menu.

Longview Solutions Framework

Issue

Description

LV-7202

Data GET and PUT REST APIs using a template would fail with a 404 not found error when file custom root path (FILES_CUSTOM_ROOT_PATH configuration parameter) was used, if the template file was not also located under the data server working directory,

LV-7610

In process maps, setting the same value for 'name' and 'description' of a process step would cause the description to be removed.

LV-7639

An event built using the Longview Designer event template would fail with an error if the system did not have a dimension for currencies.

LV-7769

In Longview Close, the roll period would not set the system attribute SGPCurrentYear correctly in a system that was not using journal entries.

LV-7955

During an upgrade, customizations to rules could be unintentionally overwritten with default rules.

Longview Tax – Multi-Regional Provision

Issue

Description

LV-6255

In Longview Tax Multi-Regional Provision (ASC/US GAAP and IAS/IFRS), tax credit year of expiry data is now correctly deployed during installation.

LV-6948

In some cases, 'Provision' could be added multiple times to the ASTaxRolloverScenarioTypes system attribute during an install or upgrade.

LV-6958

In Longview Tax Provision (ASC/US GAAP and IAS/IFRS) the following obsolete hierarchies have been removed for new installs:

  • CYRS (ENTITIES dimension)
  • BCDAYS (TIMEPER dimension)
  • MSGD (TIMEPER dimension)

LV-7739

In Longview Tax Multi-Regional Provision (IAS/IFRS), tax rates entered in 'XRC1201 - Tax Rates - Multi-Regional' were not pushed to the entity level when using the 'Regional' option for 'Regional Rates Input Level'.

LV-7771

In Longview Tax Multi-Regional Provision (IAS/IFRS), several elements were missing their exchange rate for foreign currency translation. This has been corrected for install only.

LV-7774

In Longview Tax Multi-Regional Provision (IAS/IFRS), the multi-regional deferred tax national gross transfer calculation was not transferring "Temporary Difference Classification Override" (TDCLASSOVERRIDE), "Short-term Recognisable in next 12 Months - Input" (GrsSTR_IAS_Input), and "Long-term Recognisable after 12 Months - Input" (GrsLTR_IAS_Input) to the regions, which could result in classification differences for temporary differences at the regional level.

LV-7797

In Longview Tax Multi-Regional Provision (IAS/IFRS), the multi-regional temporary difference classification calculation would fail with error when triggered by an entity with group nexus, if the regional group is a multi-currency group.

LV-7858

In Longview Tax Multi-Regional Provision (ASC/US GAAP and IAS/IFRS), several symbols were created with non-ascii characters in their descriptions which would cause issues connecting to Longview when regional settings is set to use a two-byte language for non-unicode programs.

LV-7946

In Longview Tax Multi-Regional Provision (ASC/US GAAP), the discrete items editor would assign protected accounts to the writable hierarchy, which could cause the Interim Apply Rates Calculation to fail with a lock conflict if any interim ETR input apps were open (NF0803, SSF0803 and SGF0803).

Longview Tax – Pillar Two

Issue

Description

LV-7120

If an error occurred during the installation of Pillar Two, re-running the installation process would not deploy Pillar Two correctly.

LV-7617

In Manage Constituent Entities you could get an inconsistent error message related to duplicate entity names depending on the steps taken to add a duplicate entity name.

LV-7618

In some cases it was possible to set a blank 'Main entity' for a constituent entity that was configured as a permanent establishment.

Longview Tax – Tax Provision

Issue

Description

LV-1623

In some cases, the Run Calculations button was disabled when valid settings had been selected in the Run Calculations editor.

LV-6255

In Longview Tax Provision (ASC/US GAAP and IAS/IFRS), tax credit year of expiry data is now correctly deployed during installation.

LV-6948

In some cases, 'Provision' could be added multiple times to the ASTaxRolloverScenarioTypes system attribute during an install or upgrade.

LV-6958

In Longview Tax Multi-Regional Provision (ASC/US GAAP and IAS/IFRS) the following obsolete hierarchies have been removed for new installs:

  • CYRS (ENTITIES dimension)
  • BCDAYS (TIMEPER dimension)
  • MSGD (TIMEPER dimension)

LV-7489

In Longview Tax Provision (IAS/IFRS), the deferred tax recognised event would fail with error in cases where it was triggered by multiple entities with no overlapping accounts.

LV-7658

Long module names were cut off in the Longview Modules and Settings menu.

Longview Tax – Planning

Issue

Description

LV-6930

In Longview Tax Planning, the Import and Export folder within the Administration category was displayed twice.

Longview Workflow

Issue

Description

LV-7687

In some cases, when creating or modifying hierarchical steps the process was able to be saved and activated with no symbol selected in the approval dimension.

Hardware and Software Requirements

This chapter contains information on these main topics:

Note: Third party components and versions, such as operating systems, browsers, etc., no longer in mainstream 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

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.

(x64 architecture)

Server RDBMS (64-bit)

Windows Server 2022

SQL Server 2019

Oracle 19c    

Windows Server 2019

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 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 2022

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

Windows Server 2019

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

 

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.16 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 2022

SQL Native Client 11.0

Windows Server 2019

SQL Native Client 11.0

Note: You must install the SQL Native Client 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 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

 

Windows 10

Microsoft Edge

Google Chrome1

.NET 4.8

 

Note: 1 Chrome browsers require a Chrome extension to launch ClickOnce components. For example, the Windows Remix ClickOnce Helper to launch Longview ClickOnce components.

Caution: 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 2021 – 32-bit and 64-bit

Excel 2019 – 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 17 (LTS)

Oracle JDK 20

or

OpenJDK 20

Oracle JDK 17 (LTS)

Oracle JDK 20

or

OpenJDK 20

Web browser

English

French

Server operating system

English

English

RDBMS

English

English

Web server

English

English

 

 

For an optimal Community experience, Please view on Desktop