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.

When the crawler fails on an incremental crawl, the index search must perform a complete rebuild of the index. It would be beneficial for there to be a way to revert to a previous built index just prior to the failed incremental crawl so that the index file is available. This is particularly useful for large data sources that take hours or days to crawl before they're usable again.

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 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 system administrator I want to specify where search index files are stored or make sure that the index files are not consuming space on an OS drive , so that I can manage/optimize the disk usage on my server machine.

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 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.

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

As a programmer, I want to be able to use the PI Web API to find out about changes in the PI System. This mean Elements, Templates, Attributes, Event Frames and PI Point configuration changes.

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.

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

Add functionality to annotate AF Elements using Web API.

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.)

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.

In the https://pivision-us.oxy.com/piwebapi/admin/search/database.html page the Rebuild Index button does not work. It should allow the pi vision administrator to immediate re-indexing of individual AF database at the time without affecting the usability of the others.