If a PI Point doesn't exist for an element attribute as part of a template, allow us to link the tag value to null. Currently if the PI point doesn't exist, the integrator or other client tools will raise PI point not found message. To get around the issue, we have to map the attribute to a tag that has a dummy value. It would make more sense for it be marked as a null value.

Some kind of infomation such as PI Data Archive version is easily retrieved using PI Web API. If a DLL on AF is created to this end, retrieve the value obtained from a PI Web API URL, this king of information could be easily added to AF attributes.

There is limited search options in the PSE management screen. I'd like to see more, specifically be able to search/filter on the "Element" field that is displayed on the screen.

Attributes set as configuration items are used as variable inputs to PI Analyses expressions. When this analysis is performing calculations based on empirical tuning parameters, a tracking method is needed to record changes of these parameters. Adding annotation capability to element attributes set with "Configuration Item" property would provided a tracking method.

Ex:
2020-06-15 Component replaced with new. Adjusted tuning parameter to value ### in order to reset wear rate.

I think this may be a bug. But currently the datasecurity and ptsecurity tag attributes assigned in the AF Tag Creation Settings appear to be stored on the machine where they were created and not on the AF Database for which they were created.

In the PI Asset Framework Database SQL Scripts, there are 3 "GO.BAT" files and 1 "afbackup.bat" file. These should be replaced with PowerShell scripts for several reasons:

• PowerShell is easier to read and is a more powerful language than the batch language.
• Batch scripts are best used in Windows, whereas PowerShell is cross-platform. This replacement will support OSIsoft's expansion outside of Windows.
• Microsoft is pushing for PowerShell and leaving batch files in the dust.
• The scripts are short and therefore easy to convert to PowerShell scripts.

I know this has most likely been brought up before, but i'd like to see the option to change the new Pi tag created name in the window that pops up after clicking Map, new Attribute. I don't need the %ID% added to the point name.

It would be great to have a new filter in substitution parameters based on an attribute value.

Example:.\Elements[@Template=EquipmentChild][@|Motor Type=Primary]|Attribute_B
where "Motor Type" is an attribute of child element(s).

Thanks

Enable Keyboard shortcut F5 to Refresh PSE Trend Displays

By allowing for attribute templates to be referenced across element templates allows for increased flexibility in build AF hierarchies without the need for duplicating attribute templates. .

The option for users to create a list of commonly used Contacts for use in PI Notifications subscribers would save the hassle of individually searching contacts each time members are added to a subscription. Additionally, using Contact Groups are too rigid because the desired subscribers can vary, depending on the Notification because you have to subscribe everybody in that group when that might not be necessary.

Since it's already possible to import a table through an AF Client, it would be nice to be able to do the same for Table Links.

Currently doing so results in an error: "Unable to link to external table: Unexpected Server Error". See KCS: "Unexpected Server Error" trying to link an AF table to a csv file

We currently have an issue with Docker based windows applications that we cannot enable windows authentication due to outdated AD architecture. Once suggestion is that we use claims based authentication, but this will only work for PI Web API and not AF SDK, correct. It will be good to enhance AF SDK to use claims like PI Web API.

When changing the value type to string of an attribute with an associated UOM, the following error is observed:

"...cannot be changed to type 'String' because it has a unit of measure and 'String' does not support UOMs."

When you have an existing string type attribute and add a UOM, the value type is automatically changed to a numerical type without warning. It would be helpful to include a similar message as the one mentioned previously.

When an element has a large number of attributes defined (e.g. 400), then it is very difficult to select an attribute as an input to the Formula DataReference because the dropdown does not have a scroll bar.

In PI System Explorer, when creating a filter for looking at Event Frames, in the dropdown box, the selection items aren’t sorted in alphabetic order.  It is an arduous task to review each of the selections to pick the one that you want. It would be nice if they were in alphabetical order, or if there was a search feature.