Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Historian

TABLE OF CONTENTS

Expectations and limitations

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedSep 23, 2026
  • 2 minute read

The following expectations and deprecated features should be considered for this release of AVEVA Historian Server:

Support for OData V1 will be deprecated starting with the next release. We recommend migrating to OData V2 to ensure continued support and access to the latest features and improvements.

Historian Client Web Modern uses internationalized decimal format

Historian Client Web Classic displays decimal numbers as expected. However, Historian Client Web Modern displays decimal numbers in internationalized decimal format. The specifications for this format are:

  • If the value is 0 or NaN, Historian Client Web returns them as 0 or NaN.

  • For very small or very large numbers, Historian Client Web returns the numbers in exponential format.

  • The number of decimal points to be displayed depends on the given range. If the range is large, the decimal points displayed are reduced. If the range is small, the number of decimal points displayed increases. For example:

    • In a range of 0 to 700,000, a value of 600,123 is calculated and displayed as 600,123 in internationalized decimal format.

    • In a range of 0 to 600,500, a decimal value 600,123.123 is calculated and displayed as 600,123.12 in internationalized decimal format.

Deprecation of legacy HCAP architecture

The Historian Client Access Point (HCAP) architecture has been modernized to use gRPC Remote Procedure Calls (gRPC), a high-performance framework that improves startup time, scalability, and maintainability. HCAP now runs natively as a 64-bit (x64) process, enabling more efficient memory management and support for higher workloads than the previous 32-bit (x86) architecture. gRPC communication uses TCP/IP port 32565.

Impact: As part of this architectural change, the HCAP executable location has changed. Customers using path-based application allowlisting or host-firewall rules should review and update their configurations after upgrading. In most environments, no other functional changes are expected, and users may benefit from improved performance and scalability.