PI Developer Technologies
Welcome to the
PI Developer Technologies
feedback page!
This forum covers the PI AF SDK, PI Web API, PI OPC DA and HDA Servers, and the PI SQL family. We created this forum to hear your ideas, feature suggestions and feedback. Please suggest your most important features and design change ideas on this site, and vote for your favorite ideas.
Please note that your ideas and comments posted here are visible to all other users.
- For bugs, please open a case with OSIsoft Tech Support through myOSIsoft Customer Portal (https://my.osisoft.com) instead of sharing them on this site.
- For documentation feedback and bugs, please report to documentation@osisoft.com instead of sharing them on this site.
-
Improve error logging when PI Web API fails to load attributes that are not marked as configuration items
As a PI Web API administrator, I would like to see errors logged when PI Web API fails to load any attributes because they are not marked as configuration items. This will decrease required troubleshooting for these issues.
1 vote -
PI Web API Joined should use a format which can be used in PowerBI
Currently the PI Web Api Joined, delivers the data in a json format which is not really "Power BI" friendly , it would be helpful to have a format where all the datavalues from the subordinated are in the same json object of the base.
1 vote -
Enable PI Web API to retrieve previous AF Tables versions
Internal AF table has been updated using AF versioning system, however retrieving it whole with PI Web API only works for current version: GetData method from Table controller (GET tables/{webId}/data) does not accept a time parameter.
Workarounds involve creating Table Lookup Data Reference attributes or joining all table versions adding columns for time range to be later filtered out.1 vote -
Allow Searching of PI Points by PointID or Crawling of the PointID attribute
Allow one to search points by PointID with PI Web API or add the PointID as a attribute that you can index with the search crawler
1 vote -
allow search where name contains space to return determinant results
querying for names which contains spaces is non-determinant. AFSDK has methods to search on name, but webapi OR's the search. For results sets which should contain one or few rows, this can result in thousands of wasted rows.
PI Query syntax EBNF specifies quotedescapedchar, which includes Char, so space should be honored.
1 voteCould you provide an example of this? Would encoding the space “%20” be a viable option?
- Don't see your idea?