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. 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 →
  2. 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 →
  3. Support response and additional handling of POST requests

    Have the PI Connector for UFL running in REST Server mode respond to the first PUT/POST request with additional information, which then allows the RESTful endpoint to generate a second PUT/POST request with the data we want to parse and store in PI Data Archive.

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

    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 →
  5. The UFL Connector should have a run once mode

    Many rest APIs allow access to historical APIs. This is data that should be collected only once when, for example, a new piece of equipment is being added for data collection. This one time data collection is currently tricky in the UFL connector as it involves the following:
    1. Create and configure a data source
    2. Wait several minutes for the data to be collected
    3. Delete the data source

    And this process has to be repeated each time a new equipment is done.

    3 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 →
  6. Enable PI UFL Connector to read csv with empty data fields, eg. no value between commas

    Enable UFL Connector to interpret two consecutive commas in a csv file to mean that the data field is empty. The UFL connector should interpret this empty field as a zero.

    3 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 →
  7. Support Administration Pages on IE

    After latest patches Windows 2012R2, IE access to UFL Connector 1.3.0.106 admin pages is no longer functional.

    As some IT departments do not support different versions of browser on servers, or support opening up ports for admin access, this limits ability to administer the UFL.

    Please support the default server browser for the supported operating systems.

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

    20 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. Show the scan time broken up into days, hours, minutes, and seconds

    Currently, the scan time is shown and entered in seconds. While this is simple from a programmatic point of view, it requires the user to convert their desired scan time into seconds or convert the existing scan time into terms that they understand. Please break up the scan time into multiple fields: days, hours, minutes, and seconds. This would make entering and reading the scan time much faster and more intuitive.

    3 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. Uninstall only the installed files & folders

    It is standard for uninstallations to follow a procedure similar to this: Remove all files that were added during the installation. Then remove all folders that were added during the installation if they are currently empty.

    The PI Connector for UFL does not follow this procedure. My folder of INI files was in the PI Connector for UFL installation folder. Then I uninstalled the PI Connector for UFL and lost my INI file folder. Luckily, I was able to recover it.

    Please change the PI Connector for UFL install kit and any other install kits that behave this way to…

    3 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 →
  11. Enhance the Timestamp data type to support all the formats allowed on .NET

    Use case: ISO 8601 timestamps (2019-07-08T18:48:02+00:00), would be much easier to parse with full .NET datatime format support.
    It would also allow the connector to be consistent with the dynamic timestamp formatting that follows
    https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings

    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 →
  12. 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 →
  13. UFL Connector HTTP compression

    Large data sets need to be pulled from a REST server on the internet which supports HTTP compression. Since this feature is not supported by the UFL Connector, the data will need to be retrieved in an uncompressed format. For the current project, this means several Gigabytes daily.

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

    23 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 →
  15. 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.

    13 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 →
  16. 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.

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

    I’m not sure why this would be needed. In the UFL connector you need to specify the name of the tag that you write to. And if that tag already exists, it will write to it. If that tag does not exist, then the connector would create that tag with your desired tag name. Why would you want the connector not to create that tag?

  17. 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 →
  18. 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 ,…

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

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

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

    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?

← Previous 1 3
  • 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/PREVIEW
COMPLETED