I wish that the start time of a continuous view update cycle could precede the end time of the last cycle.

For example every day query the last 30 days of data and replace rows that have already been written to the target table with the most recent data. This would be a straightforward way to ensure that data in PI and the integrator View are the same for the last 30 days. Manual corrections up to 30 days old could then be captured automatically.

Update the naming convention used to create ArcGIS feature services and layers to use names that more accurately reflect the services and layers stored on the Integrator side. Customer Issue: The current convention is to use numbers instead of the layer names which causes confusion when trying to locate published items in ArcGIS Online or Portal for ArcGIS.

In PI Integrator for BA, to use filter on an attribute configured as Boolean Value Type, we can use Numeric filter. However, 'attribute' = 1 does not work because it filters out all the rows. We have to use 'attribute' = True. It is not intuitive that we can use string value in a numeric filter. Is there any way OSIsoft can improve the UI, like add a row filter option for Boolean?

I would to force the number of decimals the Integrator writes for a given analog value

Have an extra column in the view that indicates when the data row is actually written to the target.
The current timestamp column is the timestamp of the value itself, not when the data row is written.
This will be especially useful for troubleshooting, or when PI Integrator is updating existing value in a target table (will give indication of which data row was recently updated).

Improve performance of queries resulting in a narrow table. This can happen for queries with many Elements, each with a few Attributes, where bulk queries to the data source are not possible. A narrow table can also result when using * for the Attribute criteria, as each Attribute is then considered a separate match.

As a PI Integrator Administrator I need to grant permissions to a group of users to configure targets since they are the administrators of the target systems (SQL Server, ADLS, etc.), but they don't need access to other administrator tasks like security management.

When there are multiple attributes named the same for different elements, the full path is automatically done to avoid duplicated column names. Element without name duplication issue should also have the option to display the full path column name.

As a PI Administrator for a power company I am asked twice a month to verify that none of the products I support have had a security patch released.  Any such products in a NERC zone need to be patched within the next 12 days.

It used to be fairly easy to look at updates to all PI Client tools to find released security patches.  So far I haven't been able to find out if any have been patched.  This would also include interfaces which are prone to being run in a NERC environment.

To execute a view with the same parameters, it is actually mandatory to edit the view to be able to execute it again.
It would be nice to be able to force its execution using a right clic on it for example

When applying a filter when building a shape, the Integrator displays a limited amount of matching elements which is fine.
It would be useful do display the number of element matches as an additional info

The PI Integrator should validate any link entered in the endpoint section (PI Vision, Portal, GeoEvent). It should warn the user of any certificate issues or port that are not opened.

Support for element references within PI Integrator for Esri ArcGIS.

Our end users tend not to have SQL access. We would like to allow them to create clustered indexes to increase the performance of a SQL query on the target view.

Currently, the only available decimal separator is the period (.). In some cases, the customer may want to use other decimal separators such as the comma (,). It would make sense for the decimal separator to follow the convention of the region and language selected in the UI, or have an option in the menu set it to something custom.

add an option to skip line numbers in the output files

The output files can grow quite large.
Suggestion :Split the files. Here is an example using AF element name and date :
C:\Viewname\elementname\YYYY\elementname_YYYYMMDDHHssmm.csv

The AzureSQL Target should not need access to the master database

Current version of PII4BA gives this error message:
Ref the error message
The server principal "sqluser" is not able to access the database
"master" under the current security context.

Microsoft's words:
“Generally, non-administrator accounts do not need access to the master database”
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-manage-logins