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.

How can we improve PI DataLink?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Manual Data Entry Function May Be Useful with Macros Becoming Antiquated

    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.

    46 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Functions  ·  Flag idea as inappropriate…  ·  Admin →
  2. Setting to allow the omission of error strings in Calculated or Filtered Results

    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.

    34 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Functions  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support for UOM conversions

    Being able to specify a UOM that is not the default UOM and having the value returned converted in all functions

    Note: This was previously Enhancement 25182OSI8

    19 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Functions  ·  Flag idea as inappropriate…  ·  Admin →
  4. Compressed Data and Tables

    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.

    13 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Functions  ·  Flag idea as inappropriate…  ·  Admin →
  5. 12 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Functions  ·  Flag idea as inappropriate…  ·  Admin →
  6. Continue to support/modify the PI Trend Add-In for Excel DataLink that was in 2014 on into 2016 and beyond.

    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.

    11 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Functions  ·  Flag idea as inappropriate…  ·  Admin →

    The PI Trend functionality is still available in all versions of PI DataLink. However, starting in 2013 when PI DataLink was rewritten to use the AF SDK instead of the PI SDK, the PI Trend feature is in the Legacy add-in rather than the main add-in. Now, the Legacy add-in is no longer enabled by default in order to softly discourage its use, but it can be re-enabled using instructions in the setup.ini.

    While the Legacy add-in remains available, I want to mention why we have not updated the popular PI Trend functionality in several years. The PI Trend function is an ActiveX control. ActiveX is an older technology that is quite useful for embedding a program in another program (another example of its usage in the PI System is PI ActiveView). However, due to the same design that allows great portability, ActiveX is also inherently insecure and carries…

  7. Support child attributes in the Asset Filter Search

    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

    9 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Functions  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add calculation options to Calculated Data to match PSE

    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.

    9 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Functions  ·  Flag idea as inappropriate…  ·  Admin →
  9. Support named ranges to avoid issue KB01369

    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.

    7 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    RESEARCHING / EVALUATING  ·  3 comments  ·  Functions  ·  Flag idea as inappropriate…  ·  Admin →
  10. Return Annotations in Current and Archive Value Functions

    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.

    7 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Functions  ·  Flag idea as inappropriate…  ·  Admin →
  11. Support AF UOM Groups

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

    5 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Functions  ·  Flag idea as inappropriate…  ·  Admin →
  12. Improve Error Dialog When Element Attribute Path Length is too long

    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

    4 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Functions  ·  Flag idea as inappropriate…  ·  Admin →
  13. Recalculate without resize in the right click menu

    Recalculate without resize in the right click menu

    Note: This was previously Enhancement 19185OSI8

    4 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Functions  ·  Flag idea as inappropriate…  ·  Admin →

    The previous status was incorrect—this issue is not planned and was not implemented in PI DataLink 2017. If you remain interested in this idea, please help us by clarifying the idea and your use case. E.g. why do you specifically want an option to recalculate without resizing in the right-click menu in addition to “Select DataLink Function”, “Recalculate (Resize) Function”, and “[Function Name]”? How would this be more beneficial than, say, using the Update button in the ribbon?

  14. Add support for all the AFData methods as well as the generic getvalues method

    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.

    3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Functions  ·  Flag idea as inappropriate…  ·  Admin →
  15. "Show value attributes" option for Current Value and Archive Value functions

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

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Functions  ·  Flag idea as inappropriate…  ·  Admin →
  16. For compressed data, have the option to return the tagname (for example, similar to how the count is returned at the top).

    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

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Functions  ·  Flag idea as inappropriate…  ·  Admin →
  17. Show Data Time Zone

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

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Functions  ·  Flag idea as inappropriate…  ·  Admin →
  18. Eliminate the "calculation basis" argument for Calculated Data

    Consider eliminating the "calculation basis" argument (time-weighted versus event-weighted) for Calculated Data.

    Reasons:

    • Average already has 2 calculation modes, 1 for each calculation basis.
    • Minimum, maximum, and range produce the same value whether they are time-weighted or event-weighted.
    • Time-weighted count is useless and so is not needed.
    • Time-weighted total (i.e. integration over time) and event-weighted total are not even in the same dimension, since integration over time multiplies the unit by time, but an event-weighted total does not. These should be separated into 2 calculation modes. Consider calling the time-weighted total something like "totalize" or "integral"…

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Functions  ·  Flag idea as inappropriate…  ·  Admin →
  19. Display a parameter tooltip when typing functions manually

    Please add a tooltip or equivalent to show the arguments of the PI DataLink functions when you are entering the functions manually, similar to the tooltips that appear when you use native Excel functions.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Functions  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add AFTimestampCalculation options to Calculated Data

    PI DataLink currently uses Auto to return the timestamp.  As a power user, I would like to be able to choose between Auto, EarliestTime, and MostRecentTime for the timestamp returned for a value when a summary calculation is done.

    https://techsupport.osisoft.com/Documentation/PI-AF-SDK/html/T_OSIsoft_AF_Data_AFTimestampCalculation.htm

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Functions  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base

Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA
COMPLETED