I am trying to pull control limits for many different types of measurements from a single table. Some control limits do not have a high limit and others do not have a low limit but I do not want a blank to be recognized as zero because that is misleading. The only solution I am aware of currently is to assign the values in the table as strings but read them as singles at the attribute. Values that are not a number are then read as "No Data".

Although, this creates another issue in that these strings that are read as singles cannot be assigned a source unit of measure and therefore the table lookup cannot convert the units automatically.

Possible solutions could include:
- allowing you to assign a source unit of measure to a value that is converted from a string
- allow null values in tables for data types like single
- a variant data type for tables

To push data to another system (here to our MES), we would like to execute by a notification an http request e.g. as composed by JSON (POST) or URI-Builder (GET), but not as a WebService (upgrade: websocket). Just using a simple stateless http-request. This opens up the possibility to push information to many other systems e.g. using apache with cgi-bin. The implementation effort on your side should be very small, because it's easier than a WS you already have. One thing I tried is to switch off by (re)setting the http header CONNECT and UPGRADE, but this is not possible / has no effect.

This was alread asked in 2020 with some other topics but not really answered. Therefor this single idea.

Currently it is impossible to create AF Element Template that has dynamic number of Attributes. Example scenarios I have been struggling with are focused on monitoring:
- monitoring many virtual servers with checking available free storage on each disk - each server may have from 2 up to 10 disks
- monitoring of PI OPC Interfaces - some are single interfaces, some in failover which affects a number of machines, heartbeat points etc.

Alternative solution would be to allow Element Template to be created with a group of sub elements in number depending on certain conditions. For one of my described scenarios I would have an Element Template with Attribut which number reflects the number of disks and thus a number of sub elements to be created where one element is considered to be one disk. Each of sub elements in such case follow the same Element Template.

https://docs.osisoft.com/bundle/pi-server/page/permissions-required-for-tasks.html

According to the documentation linked above, when permission to Point Security or Data Security is required, the same permission to PIPOINT is also required. This is redundant. The only times that PIPOINT security is used non-redundantly are to determine who has permission to create new PI Points and to assign default permissions to new PI Points. This last point creates a security issue: if a user needs permissions to only a few existing PI Points, then they need the same permissions to PIPOINT, which will give them the same permissions to new PI Points by default.

Please make the following changes:
• Do not require permission to PIPOINT if the permission can be expressed in terms of Point Security and Data Security
• Decouple the permissions to create new PI Points from the default permissions to new PI Points

As an AF designer I often have attributes indicating whether an element is enabled or disabled, this could be referring to a piece of equipment taken out of service, or a configuration element indicating a process is deactivated. The attribute is typically a boolean attribute, and I spent a lot of time going from one element to the next in order to disable or enable it, during operation and testing. It would be really helpful if I could tie this "Enabled" status attribute value to the icon PSE shows for an element, in order to quickly identify the elements which are enabled or disabled.

For normal AF databases I could create a PI Builder worksheet preloaded with the configs, but we normally put these configs in the Configuration database and this is not visible through PI Builder.

I envision the normal element icon to be grayed out if the status is disabled, or perhaps a cross/X over the icon. See attached image!

Related to this article: https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=000031389

I may have keys that are all spaces, and this may result in constant logging of the following error upon every database refresh (determined by /RATE in pihc.ini):

List <location 4 value>, searchForKey found invalid length key.

It may be hard to concoct a KEY wildcard that results in only the keys I desire, so using * as the wildcard, I am unable to prevent these all-space keys from being returned. As a result, the pipc/pisdk logs get flooded with these messages on each db refresh. As a user, I would like an option to suppress the logging of these messages.

By my understanding, only the PI User piadmin and the PI Group piadmins can ever have write access to the Database Security table PIDBSEC, and any write permissions to it assigned to any other PI User, PI Group, or PI Identity is ignored. However, PI Users and PI Groups are deprecated, and the use of piadmin is discouraged.

Please allow any PI User, PI Group, or PI Identity to be assigned write permission to PIDBSEC, just like the other Database Security tables, so then we can finally stop using PI Users and PI Groups and use only PI Identities.

The completion of this suggestion might involve creating a PI Identity that is equivalent to piadmin in the sense of having unrestricted access to the PI Data Archive regardless of any permission settings. If this suggestion cannot be implemented, then at least prevent any PI User, PI Group, or PI Identity from being given write permission to PIDBSEC in PI System Management Tools or other configuration tools, and make sure that piadmin's and piadmins's permissions cannot be edited in or deleted from PIDBSEC's security (i.e. they should remain as piadmin: A(r,w) | piadmins: A(r,w))

In PI System Explorer, when using the Preview Results function for analyses, I want the dialog to indicate which of the input attributes the current timestamp originates from.

Example: Two inputs with update frequency 1 min, Input1 without offset and Input2 with offset 00:00:30. In my Preview Results dialog I will see timestamps 12:00:00, 12:00:30, 12:01:00, 12:01:30, etc. for an analysis triggering from these two inputs. When hovering the generated timestamp I want to see if this originates from Input1 or Input2 (or both).

This is, of course, a simplified example, but in the real world I would typically have 10 or 20 inputs, which makes it more difficult to debug.