PI DataLink
Welcome to the
PI DataLink
feedback page!
We created this forum to hear your ideas, feature suggestions and feedback on PI DataLink and PI DataLink Server. Please suggest your most important features and design change ideas on this site, and vote for your favorite ideas.
Please note that your ideas and comments posted here are visible to all other users.
- For bugs, please open a case with OSIsoft Tech Support through myOSIsoft Customer Portal (https://my.osisoft.com) instead of sharing them on this site.
- For documentation feedback and bugs, please report to documentation@osisoft.com instead of sharing them on this site.
-
PI DataLink for Microsoft Office 365 online
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.
95 votes -
Provide DataLink functionality in a Google Sheets add-on
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.
84 votes -
Official testing/support for application virtualization
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
15 votes -
Split the PI DataLink install kit into 2: PI DataLink (Legacy) and PI DataLink (not legacy)
According to the discussion in the question linked below, PI DataLink (not legacy) uses the PI SDK for loading annotations, even though PI DataLink (not legacy) could use the PI AF SDK for this instead. If PI DataLink (not legacy) was fully migrated to PI AF SDK, then this would leave PI DataLink (Legacy) as the only thing in the PI DataLink install kit that uses PI SDK.
At this point, another improvement can be made: separating PI DataLink (Legacy) and PI DataLink (not legacy) into their own install kits. This way, the main (not legacy) PI DataLink install kit…
2 votes
- Don't see your idea?