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.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Feature to turn off auto creation of PI Tags in PI Connector for UFL

    Ability to turn off auto creation of PI tags - When data is sent via REST to a PI Connector for UFL service ,currently it looks for a PI Tag in the PI Server and if the PI Tag does not exist it creates a new PI Tag. It would be good if we could turn off the feature if not required as in our case we have a naming convention for PI Tags and we create the tag names in advance so would not like to allow for the auto creation of PI Tags.

    30 votes
    Sign in Sign in with: OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your input. We are continuing to support PI Connector for UFL with stability and security releases. However, for feature enhancements, we are starting to develop the PI Adapter for Structured Data Files and encourage you to go to the PI Adapters forum to share your use cases.

  2. Allow the connector to use a proxy for web requests

    Provide a way to configure the connector to use a proxy and authenticate with the proxy if required.

    24 votes
    Sign in Sign in with: OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Thank you for your input. While we are not planning on implementing this functionality in the PI Connector for UFL, we are testing PI Adapters against common proxy types to ensure that the Adapter will support them. We are starting to develop PI Adapter for Structured Data Files which may meet your needs.

  3. Make the UFL Connector logic development/testing/debugging process less tedious

    Deploying a UFL Connector solution requires a LOT of edits of the INI file as part of the development/testing/debugging process. After each INI file change and file save, the required procedure is as follows:
    1. Click on the Data Source List link.
    2. Click on ‘See Configuration’.
    3. Click on the ‘Change’ button.
    4. Click on the ‘Browse…’ button.
    5. Double-click on the INI file.
    6. Scroll the page down until the ‘Save’ button is visible (I’m using a 1920 x 1080 monitor).
    7. Press the ‘Save’ button.
    8. Click on the ‘Overview’ link.
    9. Press the ‘Start connector’ button.

    21 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 →

    Thank you for your input. We are continuing to support PI Connector for UFL with stability and security releases. However, for feature enhancements, we are starting to develop PI Adapter for Structured Data Files and encourage you to go to the PI Adapters forum to share your use cases.

  4. 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 →
    DECLINED  ·  Abbas Saboowala responded

    This functionality is currently not supported by the connector’s querying logic and design.

  5. UFL Connector - Add elements and attributes to existing AF hierarchies

    Simply, it would be nice if the UFL Connector could add to existing elements and attributes already in place instead of creating a new hierarchy.

    Also, would like the ability to create sub-elements from the UFL connector that span multiple elements and are not restricted to a single instance of the UFL connector.

    Very similar to the "Connector (UFL) can read AF data structure" idea, just more succinct.

    6 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 →

    Thank you for your input. We are continuing to support PI Connector for UFL with stability and security releases. However, for feature enhancements, we are focusing our efforts on developing PI Adapter for Structured Data Files.

    While our current PI Adapters do not support writing to AF, we will consider including that functionality at a later time. If you have additional enhancement requests, please head to the PI Adapters forum and share with us there.

  6. Incoming TimeStamps Utc

    Please rename "Incoming TimeStamps" to "Incoming Timestamps".
    Please change "Utc" to "UTC".

    These small spelling issues come across as sloppy.

    5 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 →
  7. 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.

  8. 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 →
  9. Allow connectors to write to a buffered PI Point

    The customer stores shelving and alarming event data in the same PI point, as they are two parts of a full picture. They receive alarm data through the interface for OPCAE, however shelving events are not exposed through this data path, and they have to export the shelving events on a scheduled basis as CSV files, then consume them using the interface/connector for UFL. Sending the data to two separate points and then combining with analysis would add to the complexity of an already complex process, so it's not desirable to use this method.

    1 vote
    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 →
  10. "13,10 OR 10" New Line default

    Currently, there is no default entry for New Line. The user can use any characters as line delimiters, but the Windows and Unix new lines would, by far, be the most common. Please make the default New Line "13,10 OR 10" to save most users the trouble of configuring the New Line.

    1 vote
    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 →

    Thank you for your input. We are continuing to support PI Connector for UFL with stability and security releases. However, for feature enhancements, we are starting to develop the PI Adapter for Structured Data Files and encourage you to go to the PI Adapters forum to share your use cases.

  11. Make CONCAT take an arbitrary number of arguments

    Currently, CONCAT only takes 2 arguments, so you need to nest multiple CONCAT (or just use the & operator) if you want to concatenate multiple strings. This can be avoided if CONCAT could take any number of strings as arguments.

    In general, users expect associative functions to take an arbitrary number of arguments.

    1 vote
    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 →

    Thank you for your input. We are continuing to support PI Connector for UFL with stability and security releases. However, for feature enhancements, we are starting to develop the PI Adapter for Structured Data Files and encourage you to go to the PI Adapters forum to share your use cases.

  • 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
TELL US MORE
EVALUATING
PLANNED
IN DEVELOPMENT
COMPLETED
DECLINED