PI to CONNECT 2​.5​.2790 release notes

120148

Future Data PI Points are now supported in the transfer, allowing forecast data to be consumed in CONNECT that would enable customers to centralize and perform analytics on future data in the cloud. Previously only real-time points were supported.

120149

Support for Data Archive Collectives has been added to the agent. Previously, the agent could only connect to a single node within a collective and would stop functioning if that node became unavailable. With this enhancement, the agent now automatically detects node unavailability and seamlessly fails over to another available node in the collective, ensuring uninterrupted data flow without requiring user intervention. Asset Framework attributes can now reference points from any node within the collective or use the collective name itself. Additionally, the agent’s configuration utility now detects the collective and displays detailed collective information, including the collective name and its member nodes.

120147

Support for multiple Data Archives has been added for PI Tags usage reporting. Users can now add multiple data archives to the agent through the configuration utility. While only one data archive can be selected at a time for data transfer, the agent will send license information and PI Tag usage reports for every configured data archive. This enhancement enables a single agent to report usage information for multiple data archives, streamlining license management and usage tracking across your environment.

123799

A new Databases setting has been added to the PIAssetFrameworkServerNames section of the appsettings.json file, providing more granular control over the agent’s access to Asset Framework databases. By default, if this setting is left empty, the agent will index all databases on the AF server, making them all available for selection on the transfer page in CONNECT data services. However, specifying one or more databases in this setting will restrict the agent’s access to only those databases. This enhancement is especially beneficial for large AF servers, as limiting the agent to only the necessary databases can significantly reduce indexing time and improve overall performance.

120146

To provide more granular control over data transfer behavior and efficiency, the following user-configurable parameters have been added to the Agent section of the appsettings.json file:

• DataIngressRequestTimeoutInSeconds: Specifies the timeout for sending data from the agent to the cloud. The default value is 60 seconds, and it can be set between 60 and 180 seconds. In certain scenarios, increasing this timeout may help prevent timeouts and improve performance during long-running data transfers.

• MaxStreamingDataRefreshRateInSeconds: Allows users to control how often the agent sends streaming data to the cloud. The default value is 30 seconds, with a configurable range from 1 to 60 seconds. Adjusting this property does not guarantee the specified refresh rate and may impact transfer performance depending on data patterns.

119529

The agent now adds a new metadata item, __ParentCompleteId, when creating an asset in CONNECT data services. This field contains the full ID of the parent asset in CDS, making it easier for users to navigate and query their asset hierarchy through the API. The existing __ParentId item is still included and continues to represent the parent element’s ID in Asset Framework.

119535

Improved error messaging for large asset transfers. When a transfer fails due to an asset exceeding the allowed size limit, the error message now includes the payload size in bytes and the AF Element name.

71623

Proxy support has been added to the agent, allowing users to securely configure proxy settings using either the configuration utility or the silent installation. This enhancement ensures that proxy details are handled securely and simplifies the setup process for environments requiring proxy connectivity.

117987

Agent config utility shows default browser error if user does not have admin role on the tenant. When being prompted to login to CONNECT, if an email account that does not have tenant administrator privileges (Tenant Contributor or less) was being used, the user was being shown an error dialog stating: "Please log in to CONNECT via the default system browser. If the login fails, relaunch the configuration utility." We have now updated the error message to be more meaningful and direct: "Logged in user does not have Account Administrator role. Please log in with a user with the Account Administrator role."

118033

Tags using an extended classic point class were not being transferred to CONNECT data services as none of their tags were being picked up by a transfer. We now enable sending such tags. Note that we don't send any extended attributes, just attributes defined in the base/classic point class. We also do not support 'non-standard' point classes, that is point classes not based off the classic/base point class.

PI to CONNECT Agent Installation

2.5.2790