PI Connectors

Welcome to the PI Connectors feedback page!  

We created this forum to hear your ideas, feature suggestions and feedback on PI Connectors. 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 Connectors?

(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. Be able to point the PI Connector for UFL to INI files

    Please allow INI files to be pointed to by saving their full path, just like the PI Interface for UFL, rather than saving a copy of an uploaded INI file. This makes editing, testing, debugging, etc. much easier.

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

    We’ll send you updates on this idea

    2 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
    DECLINED  ·  Chris Coen responded

    The proposed solution in this request is not advisable for security reasons. The current process ensures that the change to the parsing file is accomplished with credentials that allow administration of the connector.

    The question I have is what is the underlying problem that fostered this solution? If it is something like it is hard to deploy updates to the parsing script (.ini file) and maybe this is especially challenging during development, then that idea would be worth capturing for sure.

  2. Connector (UFL) can read AF data structure

    Right now it is a limitation because of the current functionality / design.

    In the future it would be nice if:
    - the connector can read the existing AF structure
    - update the existing AF structure
    - create elements / EF / attributes under existing elements

    there was a case, while the customer wanted to create EF StoreEventFrame() under existing element, but it did not work.

    had to explain the limitation: we are not able to do it unless the element was not created by the UFL.

    also Event Frames StoreElement() needs to be used in conjunction with StoreEventFrame() and…

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

    We’ll send you updates on this idea

    1 comment  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  3. Remove conflict between TAU framework and PIBufSS

    We should be able to use buffering on one tag that is fed by the connector, in case there are moments when data has to be primed into it using AFSDK.

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

    We’ll send you updates on this idea

    0 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  • 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