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. 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 →
  2. 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 →
  3. 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…

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

    3 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. Incoming TimeStamps Utc

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

    These small spelling issues come across as sloppy.

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

    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 →
  7. UFL Connector - sort input files by parameters other than name

    Allow the UFL Connector to sort input files by parameters other than the name.  This will be useful in cases where file naming conventions will lead to large amounts of OOO data.

    2 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 →
  8. Make a version of SkipFile() that stops processing the current file immediately

    The current SkipFile() function tells the PI Connector for UFL to skip the remaining lines in the file, but the PI Connector for UFL will continue to execute the rest of the code in the "per message" section that the current line triggered.

    Please consider making a version of SkipFile() that stops processing the current file immediately. This helps avoid unnecessary Else blocks in If statements. This functionality would be similar to returning from a function or breaking out of a loop in other programming languages.

    To implement this, consider adding a new function or adding a function argument SkipFile().

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

    0 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  10. Make Data Persistence Settings Configurable

    Currently, .zip folders containing processed files can reach up to 256MB in size. Browsing the contents these folders can be difficult due to the number of files within.

    Being able to specify either a file count of folder size parameter would help simplify this process by breaking the zipped folders into more digestible, user configurable sizes.

    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 →
  11. Add a type casting function or operator

    The INI files would be shorter and more readable if the PI Connector for UFL had a type casting function or operator.

    For example, if you are incrementing a Counter variable (type Int32) for each data line, and your tag names are Tag1, Tag2, etc., you currently cannot simply save data to "Tag" & Counter. You must assign Counter to CounterString (type String), and then save data to "Tag" & CounterString.

    This could be simplified to "Tag" & CAST(Counter, "String") or "Tag" & (String)Counter. A type casting function or operator would avoid the intermediate variable while still making it clear…

    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 →
  12. Use a consistent language-region separator for Locale

    Currently, the language-region separator in the Locale choices can be any of "-" (hyphen-minus), "–" (en dash), or ":" (colon). For consistency, please use only 1 separator.

    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 →
  13. Use the most recently used Locale as the default

    The default Locale is currently "English - United States" for all new data sources. Please consider using "English - United States" as the default Locale only for the 1st data source, and using the most recently used Locale as the default for all subsequent data sources. This saves the user from repetitive Locale configuration.

    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 →
  14. "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 →
  15. 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 →
2 Next →
  • 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