Expectations and limitations

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

Limitations of runtime language switching

Please note the following limitations of runtime language switching:

• Runtime language switching is not supported for embedded Query controls.

• For the Query tool, runtime language switching is only applicable to the Description field.

• For SQL connections, runtime language switching is only available for SQL-supported languages.

• If multiple connections are configured and one of the connections is Cloud (OData), when on an active cloud connection, the user will be prompted to log in each time the language is switched.

Enable macros when using Historian Client Report add-in for Microsoft Word

When using the Historian Client Report add-in for Microsoft Word, macros must be enabled when running a query from the Historian tab or a runtime error occurs.

ActiveX controls deprecated by Microsoft

Microsoft has permanently disabled ActiveX controls by default in Microsoft 365 and Office 2024 due to ongoing security and compatibility risks. This means that embedded ActiveX controls in Word, Excel, PowerPoint, and Visio no longer work and are blocked without notification, often appearing as static, unclickable content. If you have legacy documents with older, embedded templates, you may run into unclickable content due to this.

If you have any legacy content affected, Microsoft recommends the following alternatives for migrating your disabled content:

• Office JavaScript (Office.js) Add-ins: The primary modern replacement using web technologies. Note that these only run within Office hosts and cannot be embedded in standard .NET or Win32 apps.

• Office Scripts: The recommended choice for automation scenarios, specifically in Excel.

• VBA and Form Controls: A viable alternative for desktop environments, though they will not work on Office for the Web.

Importing .NET controls

The following .NET controls require an additional step to be imported correctly:

• aaHistClientActiveDataGridControl

• aaHistClientQueryControl

• aaHistClientTimeRangePicker

• aaHistClientTrendControl

• aaHistClientSingleValueEntryControl

• aaHistClientTagPicker

Steps to import these controls:

1. Import the aaPKG files from: C:\Program Files (x86)\ArchestrA\Framework\Bin

2. Import the desired controls from: C:\Program Files (x86)\ArchestrA\Framework\Bin\AVEVA_Software_LLC_xxxxxx.dll

This process applies to both InTouch HMI and System Platform IDE applications.