I don't believe this is possible.
I'm not sure how much value it would add to have it either. These queries use the indexes stored by the Indexed Search Crawler and they don't capture the PI Point values. This means that your queries will only be able to compare to static attributes.
For example, here is what the attributevalues look like for one of the elements in my database:
sinusoid and CDM158 are the tag names supplying the values to those attributes.
Table Lookup is the type of one of the attributes.
Five and 0 are attribute values that are typed in manually.
Maybe you have a different use case than I am envisioning. Could you share it?
yes it would be mostly used for static attributes. My intention for this was to be able to save me to pull a huge amount of the same element (based on element template) by adding this search operator to look up for the element with an datetime attribute greater then a specified date. Doing this would save me to pull this big list of elements into JSON on the server and parse that datetime attributes to only end up with smaller list. I want to pull as less data as possible through the network for performance.
1 of 1 people found this helpful
The search crawler only allows to index PI Point Attributes (of Point Class Classic). Because of this you cannot use the Search as suspected by Paul Martin already.
One option would be to use Search to get all Attributes and to use a StreamSet call to get the values pulled. You would than be able to do your comparison client side which I understand is not your preferred option. Therefore, CreateSearchByAttribute might serve you better.