A significant number of companies are moving from the Microsoft Office suite to "G Suite" (Google). This move takes customers from MS Excel to Google Sheets, and they would like to retain PI DataLink as a functional add-on.

Support PI DataLink on Microsoft Office 365's web portal, Office Online (accessible via a browser). Note that PI DataLink already supports desktop installations of Office 365.

Currently, PI System thick clients such as PI DataLink or PI ProcessBook are not tested against virtualized environments, as described in KB01590. However, there are various benefits of virtualizing parts of the PI System, as outlined in the article. As a sysadmin, I would like official support for virtualizing PI System clients using technologies such as App-V or Citrix Virtual Apps (formerly ZenApp) in order to realize these benefits across our company’s technology stack.

https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=KB01590

Please add a feature that automatically checks for updates when PI DataLink starts up. This way, the updates come to the user rather than the user having to check if there is an update.

Official support for Microsoft's application virtualization technology, App-V.

NOTE: While PI DataLink 2016 may happen to work with App-V, it is not officially supported by OSIsoft. This was previously Enhancement 25302OSI8.

To minimize the amount of data that is returned from the PI Servers, and to make the PI DataLink computers more like thin clients, consider making a service for the PI Servers (PI Data Archive + PI Asset Framework) that handles PI DataLink requests.

This service should perform all interpolation calculations (Sampled Data) and aggregation calculations (Calculated Data) and return only the raw function output to PI DataLink.

Many users utilize the legacy add-ins for DataLink through VBA code.  Starting with DataLink 2016, the add-ins are not installed by default and so upgrades and new installations can prevent existing spreadsheets from working if additional steps were not taking to install the legacy components.  These steps are unnecessarily complicated: extract the installation package, modify the setup.ini, then proceed with the installation.

Instead, the installation wizard could provide users with an option to install the legacy components while at the same time warning them of the security risks posed by ActiveX.