There are a variety of reasons why being able to handle views in bulk would be nice. If I am cleaning up the UI it would be easier to delete multiple views at once. If I am doing maintenance on a target and I want to stop a subset of views, then I currently have to do them one at a time. Allowing the option to select multiple views would aid in these tasks.

Currently we can export PI data using a given interval, returning evenly-spaced rows of data.

However, for some uses i need to have the original events stored in PI, not interpolated.

E.g. i need to create a report that contains every value that the operator has entered (e.g. a catalyst dosing volume) in the duration of an EventFrame.
For that i would need Archived values like i have in OLEDB Enterprise.

When modifying a view that has already ran successfully, the First Run Time is not preserved.  The last time I configured it, it was set to a future date at 1AM.  When I modify it again, the field is populated with '*'.  It would be nice to have the last configuration saved even if it's not valid, so that I have the context of what I last configured.

We have customers which neither use Oracle or MSSQL as datawarehouse but have standardized heavily on PostgreSQL as Data Warehouse. We should support this as a target System for PII4BA.

When I click on the "Select All" button in order to select all the attributes of a view, the child attributes are not automatically selected and it is needed to select them one by one.

Could it be possible to implement a new version of this functionality in order to facilitate our work?

Currently it is not possible to change the TimeStamp format from MM/dd/yyyy 12h AM/PM to other formats. Since there are many potential different data endpoints, it may be a good idea to allow users to change to other formats, such as 24h Military time.

Allow the user to display more than 100 records in Modify View screen or at least show the total number of rows as additional information.

Being able to specify message keys for Apache Kafka targets would allow users to configure partitions.

Implement new target Azure Cosmos DB - this is today not available and not on roadmap

Allow Arrow keys to navigate sequential message logs in the Web UI

As a user for PI Integrator for BA, I would like to have an option to only publish data when the value changes. The use case: a point is calculated via analysis service once a minute, and the value does not change often. I want the data to be published only when the value changes. Right now, PI Integrator for BA publishes the same (unchanged) value at each run with a different timestamp.

To minimize the load off of piarchss and pisnapss, it would be helpful to be able to schedule views to run once at a specific time. For example, a view to collect data from (January 2018 to January 2019) for multiple years so that it doesn't interfere with other views running.

As a user, I'd like to utilize the columns in Statistics tab more effectively by being able to sort on the column so that I can sort by duration, error count, etc.

As a user of AF, we would like it to be the system of record for our data.  For some of our KPIs, we would like to leverage the Limits feature in PI System Explorer and have the ability to add those limits to the Integrator.  Then we can leverage the limits downstream when creating our dashboards to show if a KPI is below or above a limit.

At first I thought the Integrator only retrieved 100 rows of data.  It would be nice to know that the actual publication is not reflective of the preview and that the page is limited to the first 100 rows of results.

When a user starts making a new Shape in the Designer UI they are given a list of AF Servers/DBs to choose from.The list is currently in alphabetical order and the first item is selected. It would be great if there were some default could be reflected so the user can immediately start working on the shape.

As an Integrator administrator, I would like to be able to easily find specific Views in the Licensing tab of the admin page by filtering and/or sorting the table. Currently, when many Views have been created and deleted, it is hard to find specific Views or even find ones that have streams that can be recovered.

The customer is displaying grid sensors on their map. The grid sensor error attribute is a boolean, True or False. They would like to be able to filter on a time-enabled layer based on whether the sensors are in error or not.

As a data scientist, I would like the output from the integrator to only include values for tags that are actively updating. When the PI administrator disables scanning on a tag, I would like the option to filter the row or at least send a NULL value instead of interpolating the stale value.