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

Batchview actualmente no se puede usar en Excel X64, con lo que se pierde la posibilidad de analizar los batchs con datalink

If multiple tags are selected for 1 compressed data function, it is difficult to determine which data is associated with the tags.

On behalf of Elizabeth Metzler
elizabeth.metzler@enbridge.com

When returning data have an indicator of the data's timezone. Other than in setting as that only indicator future pulls.

As a PI DataLink user, I would like for attributes for the Event Frames I am viewing with the Explore or Compare Events functions to update automatically, rather than having to use the Clear Cache button in the Settings window to retrieve new values.

SUPPRESS THE COLUMN NAMES.
I am working "one rwo at a time" where an attribute within an event must match something in another column, but can't do it when PIEFDat always returns two rows for each query. grrr. The older Batch system version could do all this stuff.

ProcessBook stores tags by their pointid. If you change the name of a tag, It will still show up in ProcessBook. We would like to have the option to store tags in Xcel by the tag number instead of the name.

As an example, we are getting ready to change allot of PI tag names, it would be nice to convert the spreadsheet to save current tags by pointid, then save the file. Change our PI tag names, then reopen the file and reconvert it tag names. When we change PI Tag names, we want the spreadsheets to still function.

Whenever Daylight Saving Time starts on Brazil the issue below is prone to happen:

Whenever Start/End time has a date corresponding to DST start, which will either cause date misinterpretation (using formats XX-XX-XX or XX/XX/XX) or throw an error (given DateTime represents an invalid time).

Customers want to avoid having to install a localhost to client machines and having to make changes to every spreadsheet.

When we use Datalink to select the child attributes, you have to select them one at a time. Being able to select several at once would be nice.

When AF Elements contain hierarchical attributes, there is currently no mechanism to use the Asset Filter Search to bring in the child attributes... only the parent attributes are returned.. 

This is already documented in this KI
https://techsupport.osisoft.com/Troubleshooting/Known-Issues/40739

PI DataLink (specifically, the right sidebar that pops up when entering a current or archive value) is very hard to read in Dark Theme (office 365 only). If this could be resolved, that'd be great

Element Template field doesn't accept multi-cell referencing - only the 1st referenced cell will take effect. Known Issue 91547 is exist.

The issue is that not all attributes displayed in the attribute to display section on the Asset Filter Search in MS Excel when range of the element template is chosen.

Excel VBA code can invoke the resize/recalculate function on Datalink array formulae.  However this requires selection of the array and this pulls the appropriate Task Pane into view (unless the Datalink setting is in force that turns this off).  It would be good if the VBA code could hide this Task Pane, but trying to do this currently causes an exception.  See PI Square thread: https://pisquare.osisoft.com/message/116861-re-is-there-a-way-to-force-a-pi-datalink-array-formula-to-recalculateresize-using-vba-automation

For international companies, it would be good having the possibility to use the new AF UOM Groups in DataLink, so that each user could see data with the UOMs he is more comfortable with.
It would be even better if these would be selected automatically depending on the user region (though it should be possible overriding this setting).

Currently, the Root Path field of Datalink can be pointed to a single cell to retrieve the name of the Data Archive where the tag resides.

It is not possible to specify an array of cells, as only the first Data Archive will be considered.

There are workarounds for this, such as:
- using an Excel formula to concatenate the root path and the point name and call the obtained cell from the DataItem field
- using single-row queries instead of array queries

Still, it would be nice to have an array-query option also for the Root Path field.

The values of timestamp tags or AF attributes should be formatted as timestamp in Excel by default. Currently they are returned as integers, and then users have to manually convert them into timestamps.

Compressed Data should be able to (or have the option to) query multiple tags and return the results as a single table/array of information, instead of independent columns of data. Returning independent columns of data results in rows being mismatched across multiple columns because of missing events. A table should be able to be easily created that keeps the data from multiple tags contextualized with each other based on the time stamps.

Currently, you can only use "Recalculate (Resize) Function" on a single array formula at a time.

Instead, please consider implementing this rule: all PI DataLink array formulas that have ≥1 cell in the selected range get recalculated and resized.