Add auditing or a view of statistics for the calls or requests done by each individual application. Allow a PI Admin to see which user or application is making a specific call and see how long it takes to complete to monitor performance and potentially resource intensive Web API calls.

I would like the ability to pass response values from one request into the body of a dependent request using the batch controller to avoid making 2 calls to the PI Web API.

Currently,  I can only use Parameters in subsequent URLs, but not bodies.

Currently calling any of the AdHoc StreamSet actions causes the entire call to fail if the request includes at least one bad WebId. It would be better if the response came back successful and only the sub-items with bad WebIds included an error message.

As an PI administrator I need to monitor the health of the index files created by the PI Web API Crawler. In particular, if the last crawl date has not been updated recently or other errors show up. This is currently done by manually visiting the PI Web API database page. A performance counter that reports things like "the number of databases who have not been updated in 1 hour" or  "the number of databases in error" existed, we could store that info in tags and act on the crawler getting in a bad state in a proactive manner.

As an end-user, I want to be able to see to which PI Collective member I am connecting to. I also want to be able to toggle programmatically from one PI Collective member to the other so I can make sure the informaiton I am seeing is aligned and in synch accross all PI Collective members without going into thick PI clients or through log files.

As a PI Web API user, I would like a simple method to perform bulk deletes of a particular attribute or PI tag. Currently, a bulk delete requires 2 calls. One to retrieve the event I wish to delete and another to delete it.

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.

OMF 1.2 specification includes an enhancement to allow the use of propertyoverrides keyword in container messages.
Request is to add this functionality to Web API OMF endpoint specifically for the uom property

For example:
1. device configured with uom, OMF application creates a type specifying that uom.
2 new version of the device changes the uom. OMF application needs to create containers with the new uom, retaining other properties of the type.

The customer would like the ability to schedule crawls for a specific AF database (it's quite large), so that crawls don't interrupt users who need to access the elements in the PI Vision search during their working hours.

It would be great if as an addition to conventional documentation there was a SWAGGER page with short explanation of methods and parameters (including return types, etc.)

The PI Web API exposes a "CanBeAcknowledged" property when reading Event Frames. However, this property is read-only: it cannot be supplied when creating a new Event Frame or updating an existing Event Frame. I would like the ability to include this parameter when creating an Event Frame.

Enable Create,Read, Update, Delete operations for OMF applications via an API so that the process is standardized and efficient/effective as opposed to manual and error prone, especially for larger numbers of apps.

We use attributes to reference elements and attributes extensively to model context and relationships in our AF models. Is this going to be supported in the future? Kind regards, Gregor

My client is interested in writing annotations to Stream (time series) data via the PI Web API. I know it's possible to pull this data via the ?associations=annotations query parameters but the write feature is missing.

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

The channel/websocket feature of PI Web API would be more useful if it was possible to subscribe/unsubscribe to attributes on an existing channel connection. Currently you have to open the connection with all the WebIds you want in the resource URL. If you want to change which values you are receiving, you would have to close the connection and open a new one. Adding this new feature would also solve issues with maximum URL length limitations.

Add functionality to annotate AF Elements using Web API.

Support Type updates on PI Web API OMF ingress

I would like to be able to setup the PI Web API OMF endpoint to point to multiple PI Systems, so that way it is easy to send from this single instance to different production systems or to our development and production environments concurrently