We need to be able to apply PI AF attribute categories via PowerShell! We can do this today via the AF SDK, by referencing it within PowerShell, but it's a pretty convoluted solution to move back and forth in between command-lets and direct AF SDK references!

Customer would like to write a query to return a time column with a negative offset in the PI OLEDB Provider such as:

SELECT time, (time - 1d) as datekey
FROM piarchive]..[picomp2]
WHERE tag='sinusoid'

This query works

SELECT time, (time + 1d) as datekey
FROM piarchive]..[picomp2]
WHERE tag='sinusoid'

A similar query can be written using a linked server but requires the additional overhead of a sql server or ssms.

SELECT time, DATEADD(day, -1, time) as datekey
FROM [PI_DA].[piarchive]..[picomp2]
WHERE tag='sinusoid'

As a PI OPC DA Server User, I would like to be able to create groups of tags (items) on the OPC Server, so that when I look for a specific tag in an OPC Client tool I don't have to search through the thousands of other tags that exist on my PI Server. This will make using the PI OPC DA Server more efficient and enjoyable.

How to use infopath with web API the same way it was documented how to use infopath with web services.

Can the PI Web API be configured to store its configuration information in a flat file or some other (non AF) mechanism?

In PI SDK Utility → KST Cleanup, there are 3 check boxes and 1 text box. When a check box is checked, the check box's label and description are added to the text box.

Since there are only 3 check boxes, just eliminate the text box and have each check box description show underneath its corresponding check box. This would look a lot neater.

Currently the GetEventFrames method returns only the properties of the event frame (start time, end time, extended properties, severity, ect.). In order to get a table including the event frame attributes, you need to get the event frame list first and then go through each event frame to get the related attribute values.
It would be helpful if the GetEventFrames function returned a snapshot of the event frame's attribute values to improve the speed of custom applications.

Add the ability to retrieve Attributes and Elements by category for Powewhell command-lets.

Example 1:

$cat = Get-AFCategory -Name "Product A Manufacturing" -Element -AFDatabase $afDB

get-AFElement -category $cat -AFDatabase $afDB

Get a list of all the elements in category "Product A Manufacturing"

Example 2:

$cat = Get-AFCategory -Name "KPIs" -Attribute -AFDatabase $afDB

Get-AFAttribute -category $cat

Get a list of all attributes in category "KPIs"

The stream endpoints should allow passing input attributes/values if the attribute's Data Reference supports it (refer to the AFDataReference.GetValues method in the AF SDK).

For example this could look something like:

.../stream/{WebId}/recorded?input.myInput1=myValue1&input.myInput2=myValue2

One strong use-case for this would be an attribute configured as a Table Lookup Data Reference that returns a time series but allows a parameter to be defined.

Recalculate an Event Frame after a manual entry through PI Vision.
So after inserting data in a manual manner, I want to be able to automatically recalculate the EF. In new AF version this works for analysis but not for EF. There is a way to do program it by using PI AF SDK? I would be happy if this can be done already from PI Vision with PIweb API.

Currently, a method like PIServer.CreatePIPoints returns AFListResults<String, PIPoint>. Very similarly, PIPoint.FindPIPointsByPath will return AFKeyedResults<String, PIPoint>. The functionality of each result is essentially the same; they even have, for most practical purposes, the same associated properties and methods and thus; they should not be different object types.

Sharing an object type across all of these PIPoint-related functionalities would allow developers to more easily share methods for these related functions (Such as error handling methods).

Currently, the AFSKD GetValue() method supports GetValue().ValueAsInt32, .ValueAsDouble, and .ValueAsSingle. However, there are other possible AF Value Types, such as "Boolean". The AFSDK should expand the GetValue().ValueAs functionality to include all possible AF Value Types.

When requesting time series data for multiple attributes using a streamset request and the PlotValues endpoint, it would be helpful if the response had the timestamps all lined up. This makes it easier to render the data, particularly if the data is being visualized in a stacked area series.