Currently the PIPointQuery cannot contain a filter condition with same filter name twice per AND condition of the query string.

PointId:>5 AND PointId:<10.

This would cause an error.

Therefore filtering for a certain range is annoying as both result lists then have to be compared for common elements, workaround for the AND in above condition.

Enhancement:

Introduce a "BETWEEN" operator for the filter condition.

Allow multiple use of filter names in the same AND condition.

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"

https://pisquare.osisoft.com/message/116957-pi-sql-commander-and-ssrs-how-to-retrieve-multiple-values-with-the-same-timstamp

In the current implementation of the transpose archive in OLEDBEnt, a user is unable to retrieve data that may exist at the same timestamp as  another piece of data. This is because the time column is treated as the primary key of the transpose table. I would like to be able to retrieve all data using the archive transpose function regardless if timestamps are duplicated.

Expose interfaces for asynchronous data method calls (ex. InterpolatedValues, PlotValues, RecordedValues, Summaries) that:
    1. Take an asynchronous enumerable of `AFAttribute`s as input
    2. Output an asynchronous enumerable of results
    3. Throttle the calls made to PI Data Archive so that it does not overwhelm it

The use case is to be able to make end-to-end asynchronous data method calls on a set of AFAttributes.

The PIPoint.ReplaceValues method requires a replacement of every event in the timerange, however it also may reorder or miss events with the same time stamp. The issue is that if the client wants to replace only a certain event, but must find that event - the replacement is for all the events at that timestamp and the method doesn't seem to allow for precise replacement of a value.
The use case is programmatic correction of operator manual entry error, where multiple events have the same timestamp.

Enable functionality for PI OLEDB Enterprise that will allow the client to specify which member of a PI Data Archive collective they wish to connect to. This functionality has already been enabled for PSE and would like something similar for PI OLEDB Ent.

Currently, as shown in the link below,

https://techsupport.osisoft.com/Documentation/PI-Web-API/help/controllers/search/actions/query.html

The "instrumenttag" as well as other PI point attributes are not selectable in "fields".

The selectable ones are shown below:

afcategory; attributes; datatype; description; endtime; haschildren; itemtype; links; matchedfields; name; plottable; starttime; template; uniqueid; uom; webid

As a Web API developer, I would like to be able to use time PE functions in the Web API using the streams/streamsets controller to allow for complex time queries.

As a PI Web API administrator, I would like to natively restrict which users can and cannot see particular URLs and controllers on my PI Web API endpoint.

PercentTrue is missing in the WebAPI. Would you consider adding it? For some context, I come from here:

https://pisquare.osisoft.com/message/115587-re-calculation-percenttrue-is-missing-on-the-webapi

Several customers have asked for ability to search on multiple categories.  I understand from developers that a generic OR in AFSearch can be quite expensive, but allowing for search filter Category to support Equal or IN should not be expensive.

Have PI OLEDB work with structured annotations.Hopefully at the very least with String Type annotations.

As a PI Web API developer, I would like to retrieve values by specifying a count like you can do in PI SMT and other PI clients. This functionality is exposed by the RecordedValuesByCount in the AF SDK.

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.

Expose AF element modification timestamps to WebAPI so that caching mechanisms in middle ware or consumer apps have a programmatic way to determine if the structure needs to be crawled/refreshed.

As a developer of custom applications that use the PI  AF SDK, I'd like to be able to easily determine if an attribute based of an attribute template is configured for tag creation. Currently the AF Attribute Template class does not have this property. The current work around is to look at the configuration string which is less efficient.

See https://pisquare.osisoft.com/message/112944-is-there-a-way-to-limit-the-size-of-pi-channel-messages for the originating question.

Clients connecting via PI Channels have limits on the size of messages they can receive, for security reasons.  It is possible for PI Channel message sizes to exceed these limits.  There should be a way to configure the max message size for PI Channels.