Ideas

PI Builder cannot write to Attributes that are Data References. It should be able to.

Currently when backfilling an analysis with the PI Buffer Subsystem turned on, all values are sent to the PI Data Archive uncompressed. This is because values are perceived as out of order and these settings are not observed. This should be mentio...

Please exclude the information from PI Server 2018 SP3 installation and upgrade guide, which describe to check the Default Health Points as there are no default Points created in 2018 installation.

If PI Builder could upload raw data to PI, manual data entry would be greatly simplified. There are a few ways to enter data manually in PI, but each method has severe drawbacks: • Archive Editor in PI SMT Problems: hard to add data to multiple ...

Currently, PI Builder data is imported row by row. Each imported row causes all volatile cells in all open workbooks and any cells downstream of them in the dependency tree to recalculate. PI Builder will not import a new row until this calculatio...

It would be useful to have documented what the differences between OS versions for the PI Data Archive in terms of performance and capabilities.

Currently, if there is a problem in the user's PI Builder sheet, the user will not know until they click on "Publish" and see the error messages. To help avoid this, consider having PI Builder apply Excel's data validation feature to columns that...

A PI Server column would be a useful check to confirm which PI Server results are being published to, especially when a PI Admin has a drop down list of many PI Servers/Collectives.

Currently, if you publish a PI Point configuration that contains both excdev and excdevpercent or both compdev and compdevpercent, the "percent" versions silently take priority. This means that if a user imports excdev and excdevpercent, edits onl...