Allow multiple PI or AF servers to be selected when searching for Data Items. Currently, search allows only searching on a single server or all servers.

Note: This was previously Enhancement 26673OSI8.

Currently the search does a string match on the following things: 1) Tagname 2) Tag Descriptor 3) Element Name 4) Element Description 5) Attribute Name 6) Attribute Description All columns can be made visible except for Element Description.Note: This was previously Enhancement 26433OSI8

Customer would like to see AF models in the hierarchy of elements in the AF database as part of Datalink Search.Note: This was previously Enhancement 26943OSI8

In PI DataLink, using the Explore Events function, I would have expected the list of Event Frames displayed to refresh with newly created event frames when my end time is current time '*'. I would also expect that the list of Events is up to date when I open Excel and PI DataLink.

Allow users to choose to AND or OR each filter condition in the PI tag search. Currently all filter conditions are AND.Note: This was previously Enhancement 26991OSI8

The Search menu in PI Datalink 2016 is confusing for users used to PI Tag searches elsewhere in the PI System. "In a row" and "In a column" are particularly confusing, as they suggest that searches are being performed within the row or column. This UI could use improvements to make it more intuitive for users who are used to older-style search dialogues.

Customer wants to see extra user selected columns in the search results pane with more information instead of via a right click menu.Note: This was previously Enhancement 27008OSI8

As a user of PI Datalink in Excel, I would like to return the values of attributes specific to a "Category" as specific in AF.  Currently I can perform this search using PI Builder but cannot easily combine PI Datalink functions without the implementation of a custom wrapper and VBA.

When searching for PI AF element attributes, be able to filter on tag or instrumenttag.

Allow users to save and reuse searches.Note: This was previously Enhancement 26992OSI8

In data item searches, it would be useful to have a column that shows the engineering unit or default UOM of the returned results. This helps assure the user that they chose the correct data item and confirms the data item's unit with the user.

PI DataLink 2017 added the ability to filter searches based on a PI Point's current value.   For searching on PI Point's with string values, it would be great if there was a way to do a case-sensitive search.  A ‘case-sensitive’ checkbox would be useful (so you could toggle it on/off).

Allow users to do a SQL style search for data items similar to the PI SDK Advanced Search.Note: This was previously Enhancement 26993OSI8

Currently, the same filter used in the search term text field when searching on an AF Database.    The user would like to be able to use independent filters on the attribute name and element name so that they can filter down their search results.

In the search dialog, the user has the option of filtering by many point attribute filters; however, customers may prefer some over others.   Perhaps the filters preferred by the user could be preserved across user sessions.