When looking at element attributes or event frame attributes in PI System Explorer I would like to see [string1, string2, string 3] for the value field of an array attribute, instead of "String Array" as we see today.

When you quickly check out the current values of an EF or element, it much easier to recognize the values you're looking for if you see (a preview of) it directly in the Values field for the attribute.

"Hiding" it under the "String Array" key word makes it more difficult to spot!

it will be useful to schedule an analysis with a specific Time Zone in order to be aligned with the local time and, especially, with the local setting for DST.

If Excel is installed as a Windows Store Application instead of a Desktop Application, the PI AF Client installer doesn't allow PI Builder to be installed. The reason for that is that it can't determine the Excel version through the registry.

PI DataLink faces the same problem, but there you have a workaround by editing the Setup.ini file. See this KCS: "PI DataLink setup kit does not detect Office that has been installed via Windows Store (220739)". This does not appear to exist for PI Builder.

Either a workaround or a genuine solution would be appreciated.

You should be able to urge EFs using more complex search criterias' than the ones provide in the latest PI Server 2018 SP3 (StartTime, EndTIme, EF Template).
Most important criteria would be EF categories, but also some honorable mentions:
1. EF category
2. Analysis Name
3. Primary Element Name
4. Duration
5. Others

When querying PI Points within PI Builder we see the changedate and creationdate properties show up in the format "yyyy-MM-dd hh:mm:ss" which is not the default format that Excel wants for filtering and sorting columns by date/time. However, we do see the proper format for these two properties shown after clicking any cell in the same sheet as the PI Point query and hitting "Retrieve". This yields the format "MM/dd/yyyy hh:mm" which is easier to sort and filter through.

Some interfaces such as PI Modbus allow the polling of a 64-bit signed integer value or a 64-bit unsigned integer value. Yet the database does not allow you to store these values in their native formats. You must store them as a 64-bit floating point but some precision is lost. Please add the ability to store these values in their native format.

It would be nice to have the possibility of setting a global resend and non-repetition interval.

At the moment PI API 1.x without Windows Integrated Security is installed as standard. For customers who want to use PI API 2.x with Windows Integrated Security an additional installation is needed. please include both APIs in install-pack and ask during installation what Version should be installed.

I would like to be able to insert a new variable above or below a highlighted variable, instead of having the new variable always go to the bottom of the list. This is very problematic when needing to add a new variable to the top of the list when there are many variables already existing (50+).

I would like to be able to select multiple adjacent variables in a PI Analysis calculation to move them up or down as needed as a group. For calculations with many variables, it takes a long time to move them one row at a time and one variable at a time.

Requesting the ability to be able to filter at BOTH the root level (parent attribute) and child level (child attribute) when doing a rollup analysis.

If you have the same child attribute names under different parent attributes (i.e. Children: YTD, MTD ; Parents: Energy Consumed, Energy Produced), you are unable to filter on them explicitly unless you make the name unique enough. This ultimately causes a repeat in naming from the parent (i.e. Children: YTD Energy Consumed, MTD Energy Consumed).

We have a number of predictions stored in future tags. A prediction will typically stretch 7 days into the future and they are updated and revised several times per day. Sometimes we want to sum two or more predictions into a summary prediction in a new future tag and to have this new summary prediction tag automatically recalculated for the duration of the prediction when inputs are updated.

Also there should be an option to use the timestamp of the latest future data as timebase for the calculation of a future tag.

It would be interesting to be able to permanently disable an AF analysis if this one is not used within the template.
This could be a scheduling option: Permanently Disable
The status of the analysis would indicate that this analysis is permanently disable and this is "normal".
There are many cases that this feature will be used to avoid creating multiple templates.

It would be great to have an indication / status for analysis which are not connected to "PI Point" DR (A.k.a On demand Analysis)
This allows to find them quickly and administrtators are not afraid when they see it disable.

Currently the NoReplace event mode will Append data if a value with the same timestamp as the snapshot comes in. Customer would like an event mode that would discard the value if there is existing data with the same timestamp regardless of the value for both archive data and snapshots.

The integrated installer will not perform as expected, as there is no explicit way to preconfigure the MSIs required to install the PI System.

This creates a very stressful scenario for very restricted environments. Please reach directly to me in case you want to have more information,

It'd be nice to dynamically set the Event Frame category within Asset Analytics.

Preferably have this as an option for each 'Start Trigger'.

This would be advantageous since 'category' is on the top level object and thus much more efficient to query than needing to go down into the EF attributes in order to filter further.