Consistency among tag search GUIs within client products (PI Builder, DataLink, SMT, ProcessBook, etc.)  The search in PI Builder has limited functionality and would be nice to have the same search GUI as used in SMT and ProcessBook.

Using the SMT tool with the PI archive editor you can enter current values using * as time. This enters directly into the snapshot but is not recorded in the audit trail. All changes made should be recorded

As other vendors do, offer customers the option to purchase extended support for PI ProcessBook for security updates only past 2022 for at least one year, and reevaluate annually based on number of customers interested.

This would only apply to security-related fixes, not enhancement or other functionality updates.

When troubleshooting intermittent issues, using AFGetTrace may be problematic as the trace can consume quite a bit of disk space, and setting a maximum file size will cause the trace to stop once the file is full. Without knowledge of when the issue will reoccur, we are stuck either risking filling up the disk and having a huge trace file to analyze, or set a max file size and possibly miss the issue.

Linked Tables can cause bad behaviors (freezes; attributes waiting for values) in PI System Explorer when the password supplied is no longer valid. The solution is to update the password, or delete the Table Connection if the new password isn't available.

It would be handy to have a "Disable" option when you right click on a table connection (in the Library Module) to disable it in order to avoid such behaviors until a new password is obtained.

Microsoft Power Apps enable low-code development of connectors to integrate data sources and applications. Rather than customers developing and maintaining their own connectors, it is requested that OSIsoft develop, maintain, and update a connector to read and write PI Server data.

add additional highlight on the external articles that are "Not Validated". e.g. Red highlight on the confidence section or highlight on the title name. This would allow the reader to pay more attention that the proposed in solution section of the article is not 100% tested or verified.

Creating a Polybase External Table with a PI SQL Client connection via ODBC causes query errors showing only it only supports column-wise binding. Polybase attempts to utilize row-wise binding which is not supported. Developers and customers have shown that Polybase is unable to be instructed to utilize column-wise binding instead.

When querying against an External Polybase Table the following errors are shown:
Function "SQLSetStmtAttr(0x2485bf85640, 5, 0x1d1f, 0)" was called.

Function "SQLSetStmtAttr" exited with an error code -1.

Error: [PI SQL Client] Only 'SQLBINDBY_COLUMN' is supported.

The UOM Database is incomplete. Important units are missing. Please add at least the standard SI units or provide a library/xml-file which has the SI Units included.

When connecting Redis database via DSN we get error. As interface is ASCII and Redis is Unicode. Please add the unicode support for RDBMS interface.

This applies also to pharma industry, but customer wants exact documentation of what has changed between releases in the underlaying infrastructure. As example after an upgrade, a particular COM technology was no longer used. This could have resulted in catastrophic results if by chance was not discovered in time.
For pharma: facilitates validation of the system if only the delta needs to be validated.

There many posts with similar content. to get a better overview (for people who want to vote as well for osisoft). the feedback webpage should be managed and similar postings should be merged/grouped. one example is manual data entry for PI vision, but i think there more.

There are Modus supporting devices that feature 32bit single registers (e.g ROC800-Series). PI Interface for Modbus should be updated to have support to output to these 4byte (32bit) registers.
Currently PI Interface for Modbus only has support for output to single 2bype registers or output to multiple 2byte registers to store 32bit data. There is a need to have the interface support output to single 32bit registers.
Example device manual: https://www.emerson.com/documents/automation/roclink-800-configuration-software-user-manual-for-roc800-series-en-132340.pdf

Please delete the blank hidden sheet. It's a useless waste of space.

On the PI Data Archive sheet, please use named ranges to make your formulas more readable. This will also make it easier for you to catch any mistakes and quickly check if formulas are still valid for newer versions of the PI Data Archive.

Download link for the spreadsheet:
https://customers.osisoft.com/s/productcontent?id=a7R1I000000Xz7K

A way to add notes to a PI tag at a certain time, with an indicator that will appear any time that tag is trended during that time period.

For example when a worn pump is replaced we see a step change in motor amperage. It would be nice if a note could be added with an indicator at that time any time that tag is trended to explain why there was a step change.

the compatibility of products (e.g. Data Archive with PI AF) is not straightforward. e.g. regarding to documentation (release notes, Instal-guides) it's possible to combine Dataarchive 2012 with AF 2017-R2. and indeed it's possible to use it in combination, but the installation is requiring the following steps:

• Install AF Server 2017 R2
• Install AF Client 2017 R2 on Dataarchive Server
• Uninstall PI Network Subsystem on Dataarchive Server
• Install PI Server 2012 (Dataarchive)
• Install AF Client 2017 R2 on Dataarchive Server
• Perform MDB to AF migration

thats not straight forward and should be mentioned in the documentation (list the restrictions / requirements).