There are automatic updates for PI data in Asset Views and Streaming Views, but not currently in Event Views which is what's used for Event Frames. This is important for propagating changes in EFs

Use case example: GADS classification. Data comes in and EFs are created. The integrator picks this up and sends the info along. Some time later (maybe a few days / maybe month end) data comes in re-classifying / updating the original data (ex. GADS code or attributes). In order to accommodate this manual intervention using the "Update Data" button is required.

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?

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 data science user, I would like to be able to include additional PI/AF tag information such as is Questionable so that I may filter out data down stream easier.

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.

This request applies to any OSIsoft product that requires a web browser: If certain browsers or browser versions are not supported by an OSIsoft product, the browser version should be detected and an error message shown to the user so they know to use a different browser or version.

During View import process, have the option to preserve or change the View's GUID. This comes into play if multiple Integrators share the same SQL backend; there will be a GUID collision. Use case: split a large view among Integrators (for performance reasons) by using the Export/Import option.

The Integrator application server should have a status page ("OK" or "Running") so that clients or load balancers can easily determine whether the site is up or not.  This should be implemented when the Integrator eventually supports high availability.

I am using PI Integrator to write data to file and then importing the file into a system PI Integrator does not natively support. Since I have to copy files over the network to get them to my other system, it would be nice if PI Integrator compressed the files once publishing is complete.

My users want to see the PI Point names in their views and not just the attribute name. I would like to be able to add the attribute configuration string as a column in my view.

The actual version just allows to create a text file output. It would be nice to be able to manage the format of the columns in that target

SAP recommends using compression on column store databases to conserve RAM and disk space resources (https://blogs.sap.com/2016/08/12/how-and-why-to-do-compression-of-column-store-tables-in-sap-hana/). Since date+time values are typically unique and compression in SAP HANA is column-based, compression of timeseries data like the data published by the Integrator is more effective if date and time are in separate columns as opposed to a single time column containing both date and time.

Native ArcGIS Feature Services allow for features to be updated by performing a POST to the REST endpoint to "Apply Updates".  It would be good to be able to record new values to the PI Data Archive by "Applying Edits" to the features / Elements made available for read access by the Integrator Hosted Time Enabled Feature Services.

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.

The installation path should be consistent with all other OSIsoft products that are installed in PIHOME64.

I would like to be able to have more control over the format of the views. For instance, right now it automatically populates every included attribute as a column. For my continuous data attributes I would like to be able to condense the 50+ individual attribute columns into 3 columns : attribute, value, timestamp. This would make the table a long format instead of wide.

As a PI Integrator user, I would like to be able to publish metadata about a given element's/attribute's AF version metadata (such as number like 0, 1, 2) so that I am aware when an element/attribute version has changed.