The Longview Add-In for Office now supports schedule data locking and submission through new functions. The LVSLOCK function enables users to lock entire schedules for data protection, with the ability to specify base dimension symbols to define the lock scope. The LVSSUBMIT function allows direct submission of schedule values, similar to LVSUBMIT but specifically designed for schedule data. Both functions integrate with existing submission workflows.

For more information, see Longview Add-In for Office – Longview Function Syntax help.

The Longview Add-In for Office now provides API support for attribute queries, enabling developers to programmatically retrieve System, User, and Symbol attribute data. The API supports querying both attribute definitions and values, delivering the same functionality and output format as the Attribute Query UI for automated data extraction workflows.

For more information, see Working with Longview Add-In for Office APIs help.

The Longview Office Add-in now supports full comment management capabilities, enabling users to retrieve and submit comments directly from Excel.

This enhancement introduces the new LVCOMMENT function to retrieve comments and LVSUBMITCOMMENT function to submit comments for base data cells. The LVCELL function has been enhanced to include comment retrieval, and Data Query now offers a comments option when formulas are selected, automatically placing retrieved comments in Excel notes. Additionally, Data Extract can now include comments alongside data values.

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

The Longview Add-In for Office now provides automatic lock generation for data submission. Users can submit data with automatic locking that identifies all LVSUBMIT, LVSSUBMIT and LVSUBMITCOMMENT functions in a worksheet or workbook, creates the necessary locks, submits the data, and releases the locks - eliminating the need for manual LVLOCK functions.

The API also supports this functionality with new RunSubmitAutoLockWorksheet and RunSubmitAutoLockWorkbook methods for programmatic submissions.

For more information, see Longview Add-In for Office – Working with Data Using Longview Functions help.

The Longview Add-In for Office now provides enhanced error messages for data submission. A summary message displays submission results showing how many submissions succeeded, failed, or were unchanged. When LVSUBMIT or LVSSUBMIT operations fail due to lock issues, users receive detailed error messages directly in the affected cells, replacing the generic 'Lock Conflict' message with specific information about the problem.

The Longview Add-In for Office now defaults data extract leveling to 'Leaf' instead of 'All 99', aligning with the most commonly used setting.

Data Extract now includes a 'Use Thousand Separator' option in the Format Options tab. When enabled, this feature displays numeric values with thousand separators based on system regional settings, improving readability of large numbers in extracted data.

Longview now provides all product documentation through online resources instead of locally installed documentation files. All help links and context-sensitive help within the Longview Client now direct users to the online Zendesk documentation portal, ensuring access to the most current information. This modernization eliminates documentation from product installers, reduces installation size, and allows documentation updates without requiring product releases.

The Events Status tool now displays Error, History, and Log file columns, allowing users to directly access event diagnostic information without navigating to the Events Tool. Users can click the links in these columns to view the corresponding log files for each event, streamlining troubleshooting and event monitoring workflows.

Tax preparers can now specify a separate Country of Incorporation for constituent entities in Country-by-Country Reporting. The HMRC XML export includes a new IncorpCountryCode field that allows entities to have different values for residence country, tax jurisdiction, and incorporation country, enabling full CBCR compliance without manual XML file modifications.

Longview now provides automation capabilities for Substance-Based Income Exclusion accounts in Pillar Two.

Tax administrators can configure automation settings including calculation methods (Average, Change In Balance, or Year-To-Date Balance), percentages, and source accounts. Automated accounts are removed from manual entry workflows to streamline data processing and reduce user input requirements.

A comprehensive Analyze feature is now available across Pillar Two and Transfer Pricing automation workflows, providing calculation proof similar to Book-Tax Differences.

Tax analysts can review automation source details directly from input applications including P2200 (GloBE Income), P2205 (SBIE), P2300 (GloBE Covered Taxes), P2310 (Temporary Differences), and Transfer Pricing Adjustments, enabling thorough verification of automated calculations and data accuracy.

Enhanced year-end rollover processing to support QDMTT Additional Top-Up Tax workflows. The rollover now properly manages prior fiscal year adjustments and reporting year values, streamlining multi-year QDMTT compliance management.

The system now automatically populates year values for Additional Top-Up Tax adjustments during upgrade and rollover processes. Year values are automatically calculated and updated during period-end and year-end rollovers, eliminating the need for manual entry across jurisdictions and ensuring accurate tracking of prior fiscal year adjustments.

Longview now supports Additional Top-Up Tax calculations for Qualified Domestic Minimum Top-up Tax (QDMTT).

This feature enables tax preparers to track and calculate adjustments to covered taxes and GloBE income for prior fiscal years, ensuring compliance with QDMTT requirements under Pillar Two. The functionality includes automated year population, rollover support, and input applications for managing historical adjustments up to five years prior.

Pillar Two automations now support "Change in Balance" calculation method in addition to the existing Year-to-Date method. This enhancement enables users to automate balance sheet account movements by calculating the difference between current year and prior year values, useful when profit and loss accounts are not available for automation sources.

The GloBE Income account hierarchy (P2GI) has been updated to align with the GloBE Information Return (GIR) structure. Accounts are now organized in GIR order with a streamlined list of adjustments following Adjusted FANIL, and account descriptions now include GIR codes and article references. This alignment improves reporting accuracy and simplifies GIR preparation workflows for tax analysts.

Longview now supports top-up tax allocation under Article 5.2.5 for jurisdictions with no GloBE income. The system correctly allocates additional top-up tax related to prior fiscal year adjustments when jurisdictional top-up tax does not exist and GloBE income is zero or negative, ensuring accurate Pillar Two compliance calculations for complex tax scenarios.

Transfer Pricing now supports scenario creation and maintenance. Tax administrators can activate scenarios for Transfer Pricing that are initialized using Transfer Pricing-specific initialization steps, enabling what-if analysis and planning workflows within the Transfer Pricing module.

In large hierarchies, searching in the advanced symbol selector would not navigate to the correct symbol.

When signing in to a Tidemark connection, the Longview Add-In for Office sign-in dialog spun indefinitely when user credentials were left empty.

When a different user connected and created a lock using a previously used LVLOCK function, the Longview Add-in for Office incorrectly reported the lock was not created.

The PROFILE command reported zero values for compression, decompression, and receive timing metrics when using the Longview HTTP proxy server.

The Longview Application Framework SYNCHIER command failed to parse the synchronization file for some cloud customers.

Root symbols within a dimension were not listed in alphabetical order in some components.

The Longview Single Sign-On (SSO) service encountered a startup error when the Identity Provider (IdP) metadata contained a Byte Order Mark (BOM) at the beginning.

Automation editors did not restore accounts to the writeable hierarchy when all automations were turned off or deleted. Accounts are now properly returned to the writeable hierarchy when automation settings are removed, ensuring users can resume manual data entry as expected.

Dormant entities marked as "included" with no TIN specified had their entity name set to X5 instead of the entity's actual name.

The Main Business Activity report failed on launch when an active country contained an apostrophe in its name, and the Constituent Entity report's symbol selection functionality did not work.

GloBE Temporary Difference automation files with automation disabled incorrectly triggered validation errors on target and source parameters during import. The import process now skips validation of target and source parameters when the "Automate" field is 0, allowing users to reimport previously exported automation configurations without encountering false errors.

Merge rules were missing for some Pillar Two calculation events,potentially affecting event sequencing and calculation dependencies.

Activating new compliance periods in the Compliance Period Maintenance application resulted in an error.

The QDMTT Substance-Based Income Exclusion transfer process transferred incorrect column values from QD205 to QD510. The transfer now correctly uses the QDMTT adjustment column instead of the P2SUMM column, ensuring accurate QDMTT calculations for Substance-Based Income Exclusion amounts.

The net book value of tangible assets collected at the constituent entity level was not properly translated to reporting currency in Undertaxed Profits Rule (UTPR) calculations when Pillar Two FX was enabled.

Pillar Two reports were missing the Compliance root in frozen dimensions, preventing analysts from selecting inactive compliance periods. All reports now include the Compliance root, enabling users with appropriate access to view and analyze data from compliance periods that are not currently active. Note: This fix applies to new installs only as reports are not overwritten on upgrade.

The Manage Adjusted Covered Taxes Accounts editor incorrectly allowed modification of protected accounts P2CT.ENTE.D and P2CT.ENTE.G. With the fix, users can no longer move these accounts, create child symbols under them, or assign symbols to them, ensuring the integrity of the covered taxes account structure required for proper Pillar Two calculations.

Exporting GIR data to CSV resulted in errors when Constituent Entities had election year data but no election setting.

Analyst users with access restricted to specific jurisdictions (without access to P2JTotal) could not open Pillar Two constituent entity input applications such as P2200 and P2300. These applications now work correctly for users with jurisdiction-level access only, supporting more granular security configurations for Pillar Two workflows.

Newly created jurisdictions and constituent entities were incorrectly excluded from Pillar Two automation calculations after being created in the Manage Constituent Entities editor without reviewing and saving elections. New entities are now properly included in GloBE Income, Covered Taxes, and other Pillar Two automation calculations immediately after creation.

French Windows

French Microsoft Office

Oracle JDK 21 (LTS)

Oracle JDK 25 (LTS)

OpenJDK 21 or

OpenJDK 25