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. Develop an interactive INI editor for the UFL Connector

    The editor should allow you to see in real time how it interacts with the data. Being able to test the INI file prior to loading some file would make it much more manageable to read a variety of data format and insure that it has the expected behavior before starting the connector and having to use a trial and error approach. A good example of this is what Microsoft does with PowerQuery in PowerBI. This would allow troubleshooting UFL issues much more easily and allow more people to use the connector without having to spend a serious amount of…

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

    We’ll send you updates on this idea

    EVALUATING  ·  4 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  2. Support HTTP Token Authentication to a REST Endpoint

    The REST endpoint from which I want to pull data requires token authentication. I would like the UFL Connector to be able to obtain the token given the username and password I enter on the Admin page.

    32 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 →
  3. UFL Timezone Conversion

    Supported timestamps are currently limited to Local or UTC timezones.

    Data sources may not be configurable to provide timestamps in supported formats.

    There currently exists no robust or simple way of converting between timezones using the UFL syntax or configuration.  Including custom daylight savings time logic in ini files for this is not a maintainable solution. DST rules change over time and vary from region to region.

    With the current limitations I am currently having to maintain more than 20 ini files with custom DST logic for our global operations.

    Including functionality to accommodate for the timezone formatting limitations of…

    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 →
  4. Remove or disable the PI Connector UFL function which puts "Excluded" into attributes

    If the user has two different UFL flows working on same elements and attributes, one flow puts "Excluded" into the attributes created within the second one and vice versa.

    Giving the possibility to the user to disable this function would be a smart solution.

    (To give an example: if one UFL flow creates elements and its attributes and another flow creates only EventFrams referenced to those created elements, there are 2 ways:
    1) having EventFrames referenced to elements (using "StoreElement" funcion tin the INI file) and all attributes created with the first flow in "Excluded"
    2) having EventFrames not referenced…

    18 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 →
  5. Enable setting tag attributes in UFL Connector

    UFL Connector should have ways to set tag attributes. There should be way to set the default compression and exception settings and also other tag attributes like point and data security.

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

    We’ll send you updates on this idea

    3 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  6. Enable or Disable single DataSource

    When a datasource is actually offline and we don't want the UFL connector to keep trying uploading or connecting to it and pollute the message log .

    The best option would be having the stop/start enable/disable and restart options for each datasource.

    15 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 →
  7. Create child Event Frames

    UFL connector can create child element using StoreElement function.
    it should be useful to extend functionality to event frames on function StoreEventFrame

    15 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 →
  8. Windows Authentication to the Rest Endpoint should be supported with PI UFL Connector. Currently only Basic is supported

    I tried connecting to a REST endpoint using PI UFL Connector. However, it seems the Connector only supports Basic Authentication. The REST point only supports Windows Integrated Security. We can use Web Browser to read data from the REST endpoint. We get the following error in the connector log: HTTP status code: Unauthorized

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

    We’ll send you updates on this idea

    3 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
    TELL US MORE  ·  Chris Coen responded

    Thank you for reaching out. We can extend the connector to support the NTLM authentication, which falls under Windows Authentication. Would it meet your needs?

  9. Create/Write to Child Attributes

    I would like to be able to write to Child attributes with the UFL connector using the StoreInElement function. Currently, it seems that the Connector cannot write to or create an attribute with a path like:

    ..\Element|ParentAttribute|ChildAttribute

    It ends up creating another Attribute at the level of the ParentAttribute with %18i inserted in the name where the second pipe would go. (i.e. the attribute is named ParentAttribute%18iChildAttribute)

    12 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 →
  10. Add the ability to write to a point using an attribute other than tag name

    Provide the capabilities of mapping a UFL data point to a PI tag using a PI Point attribute other than the tag name.  For example, we’ll have a data file from another database that uses a different ID than our PI point name. Could we write to PI using that ID as the point instrumenttag or exdesc?

    8 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 →
  11. Add a Boolean data type

    Boolean variables are useful for reusing Boolean (sub)expressions, concise debugging of the value of a Boolean expression, and extraction and storage of Boolean values before writing to Int32 PI status tags (e.g. on/off status, open/closed status).

    8 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 →
  12. Be able to modify the PI Point prefix from the PI Connector for UFL administration page

    It does not make sense that edits to some of the PI Connector for UFL's JSON files can be done through the administration page, but not all. The administration page should be a 1-stop configuration shop.

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

    We’ll send you updates on this idea

    3 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow specifying UOM for new AF attributes created by UFL or OMF

    I'd like the ability to specify UOM for new attributes that I create. Adding categories as well would be even better!

    7 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 →
  14. PI UFL Connector Event Frame Generator enhancement and bugfixes

    Currently it is not possible to create an event frame from the PI UFL Connector linked to an existing element, despite the documentation does not specifically mention this restriction, you can only link the new event frame to an element created within the current capture ( #902422 )

    This is really a bad limitation and a really bad practice.

    Example :
    For an equipment I'm getting csv files at the end of its batch run, and it would be extremely helpful to create for every file loaded by the UFL a specific event frame directly linked to the equipment ,…

    6 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 →
  15. Scan only when the data folder changes

    Specifying the scan time seems unnecessary. Instead, the PI Connector for UFL should only scan the data folder if a change to the data folder's contents is detected. Surely some sort of event listener can be set up to achieve this?

    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 →
  16. UFL Connector NoReplace fuction ( Store Mode)

    What we would like is a third option with UPDATE and INSERT, which prevents a new value for the same timestamp from being processed. Such as a NO REPLACE mode.

    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 →
  17. Add ‘No Replace’ mode to UFL Connector

    Currently the only PI Data Archive ‘Store Mode’ options are ‘Insert’ and ‘Update’. I’m currently working on a project where a large quantity of data needs to be downloaded daily from the internet using the REST client node. To reduce chances of data loss (e.g. due to download failure), the Connector will be configured to retrieve the same data set several times throughout the day. The best option at the moment is the “Update” mode. This however will place unnecessary load on the PI Data Server as large quantity of archive records are re-written with the same data throughout the…

    5 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 →
  18. Configurable OSIsoft\PI Connectors\UFL.ConnectorHost\ location defined during installation

    Currently, the folder is created by default in %ProgramData%, which means that the output folder, storing the processed file, is created in %ProgramData%\OSIsoft\PI Connectors\UFL.ConnectorHost\Output{DSName}.
    Since %ProgramData% is generally on the OS drive (C:), processing a large number of files can cause serious damage to the machine.

    The path can be configured in Global configuration - parameter "Output Path" using the provided PS script that comes with the connector, but this parameter should be configurable during the installation.

    5 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 →
  19. Can we have a version of the UFL Connector that is compatible with the Data Collection Manager and the Relay?

    Can we have a version of the UFL Connector that is compatible with the Data Collection Manager and the Relay?

    Use case would be to allow the DCM to be the one-stop shop for all connectors and would make things easier to configure and manage the UFL connector if it were there

    4 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 →
  20. Payload configuration

    I want to be able to define a POST or PUT payload in the connector.
    Also the option to import the payload through a file. Add a testing capability so you can see the respons from the POST or PUT command.

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