When retrieving AF attributes with a by Time Range setting of Not supported, the integrator will not return the data for the intervals as defined by the Query.

I need to create asset views that perform daily aggregation at midnight. Currently once I create an asset view I must wait until after the following midnight to see the output. It would be very useful to have the option to publish once and thereafter on a schedule so there is data to work from immediately.
Alternatively if it was possible to upgrade an existing single published asset view to running on a schedule this would solve the problem.

The integrator only includes EventFrames that are closed (have end time). That is not included in the documentation, so a major issue for me now.
The reasoning is that an open EF may not have all data or correct data. I would prefer to let the user decide on that and allow to include open eventframes. After all we can filter out the open ones using row filters.

I planned to use the integrator to get rid of OLEDB Enterprise. Now it turns out i cannot reach all my data. Looking seriously into returning the license.

The reasoning is

As an engineer looking to leverage hundreds of thousands of tags for BI, I would like to use a single integrator instance to publish all of the data rather than installing multiple instances on different nodes.

We would like a better way to manage views in the Integrator User Interface. For example, we would like the views to be able to be sorted into a folder structure. With many views it is hard to properly manage them without something to sort them.

As a PII4BA user I need to create same views pointing to different PI AF Servers, when I change the AF Server, the view model is lost. It should check if templates and attributes exists on this AF Server, and if it is consistent, preserve the view model.

As a PII4BA user I need to maintain on the target database only the data corresponding to the specified time range, older data should be deleted when new data is inserted.

As a PII4BA administrator I would like to specify a logging level so I can filter which logs I want to store and which ones I don't want to store in the database.

Make the PI Integrator handle DST transitions better by allowing users to choose between a sampling interval of 1 day (can be 23 or 25 hours on DST days) or 24 hours. Currently, the PI Integrator will publish 24 hours when a sample frequency of 1 day is selected, causing timestamps to shift during DST transition days.

In the output file for the text file target there are some default columns that get added to the file "ID, PIIntTSTicks, and PIINTShapeID ". It will be good if those columns are not automatically added to the output file.

When PI is used to gather equipment sensor information but Maximo is used for asset management, it would be helpful to have a simple way to get equipment information out of PI and into Maximo.  This would be useful for scheduling preventative maintenance, among other things.

As an engineer using PI View or SQL writers for a report, I would like option to remove data older than a certain cutoff. For example, a continuous view is used to generate data for a report on the last 8 hours. Data older than that are no longer needed for the report and should be removed to avoid unnecessarily large tables.

One workaround with Text and Hadoop writers is the Append Timestamp option, but there's no ability to remove data from other targets.

During Integrator installation, we would like to choose the name of the Integrator's backend SQL database instead of using the default name PIIntegratorDB.

Some use cases include:
-Being able to use the naming scheme that our organization's DBA requires for SQL Server tables
-Installing more than one Integrator instance on the same SQL Server

Workaround: Follow the steps in KB01640 - Installing multiple Integrator instances on one SQL server.

We are using file target to move data into a system that PI Integrator does not support writing to directly. We have a script that moves the files PI Integrator creates to our other system, but we need a way to tell when the Integrator has finished writing to that file. The Integrator should either lock the file it is writing to or have a processing naming pattern similar to UFL.

As an administrator for the PI Integrator for Esri ArcGIS 2017, I want to be able to change the SSL certificate bound to the application through an installer wizard. Currently, the only option is to uninstall and reinstall the application, or manually bind the certificate using the command line netsh.

Customer would like to do Batch reports in BI Tool and Annotations contain important information, like Operator comments, reasons for changed values etc.