Manual entry data function may be useful with macros becoming antiquated. Support for making annotations may be useful enhancement as well.

Note: This was previously Enhancement 19290OSI8.

Give the customers either an option or an application setting that allow them to omit error strings from function output. This would allow them to more easily chart results. Some examples of current strings that cause charting problems include, the "[-11101] All data events are filtered in summary calculation" message in PIAdvCalcFilDat/PIAdvCalcExpFilDat and the "Calc Failed" message from PIExpDat.

Note: This was previously Enhancement 26880OSI8.

Being able to specify a UOM that is not the default UOM and having the value returned converted in all functionsNote: This was previously Enhancement 25182OSI8

This add-in allowed for a trend to be created within an Excel Spreadsheet without first dumping the data to the sheet.  It was an easy trend to make and it updated with current live data when requested (F9).

There is a work around to get this legacy add-in function to work in 2016, but no one likes a custom that only the user can see and update.

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.

As an end user, I would like to choose calculation options other than time-weighted and event-weighted so that I can override the default processing of continuous or discrete. This functionality is currently available in PI System Explorer | Time Series Data | Summary | Weighting.

Current Value and Archive Value does not return Annotations. It should not return anything for interpolated. But it can return annotations for the other retrieval modes. For auto mode, it may need to detect whether the tag is a step tag and enable to show annotations accordingly.

Note: This was previously Enhancement 12949OSI8.

Excel places named ranges in formulas when a cell has a named range (instead of cell references). Excel formulas become more readable this way.
Datalink should support defined named ranges too.
Editing a Datalink array formula directly in Excel and replacing cell references with named ranges in works already.
But Datalink pop-up dialogs can only use cell references.
With named range support for parameters of Datalink formulas no workbook and worksheet named are added to the formula anymore avoiding the issue of KB01369.

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).

Recalculate without resize in the right click menu

Note: This was previously Enhancement 19185OSI8

e.g Current Value, When Selecting an attribute whose path length > 255 characters, throws an Excel Error "Unable to Set the FormulaArray Property of the Range Class". 255 characters is an excel limitation, Datalink should not allow such a selection and throw a more human readable error or refer to an ID in the formula cell

There are tags that should be kept as Step=On but there is certain cases in which someone should be able to easily bypass the typical interpolating rules (interpolation that follows the step parameter) and allow for a true interpolation between values

The cumbersome workaround is to utilize performance equation functions within the expression field . . . but that's pretty advanced usage

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

Please add total support of using DataLink to pull data with all the methods available to AFData.  In my commercial organization we release software to aid our customers in retrieval of PI data.  We can't release software in which the AFData can't be verified.  We rely on OSIsoft tools to verify the data results.

If you make a mistake or overwrite information while working with PI Datalink information there is no way to undo it without deleting or recalculating the information completely.

Include a "Show value attributes" option on the Current Value and Archive Value functions.

now users can query compressed data according the interval. how about to query according the numbers, which users can set

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