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.
-
PI SQL Commander Lite 2018 R2, view edition impacted by limited number of characters
When you alter a view with many attributes, there is a characters number limitation that prevents you from seeing the total content of the view, so basically you cannot edit it because it's kind of "corrupt".
2 votesWe are aware of this issue and we have characterized it in the link below. Please see the workaround listed in the article.
https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=78766-78766
-
Rebuild Index is not working as expected
In the https://pivision-us.oxy.com/piwebapi/admin/search/database.html page the Rebuild Index button does not work. It should allow the pi vision administrator to immediate re-indexing of individual AF database at the time without affecting the usability of the others.
4 votesWe understand that it is confusing to not be able to rebuild the index unless you are a member of the PI Web API administrators group, even though we are requesting to rebuild from PI Vision. With that said, with PI Vision 2020, the PI Web API Search Index is no longer used for PI Vision’s search, and the PI Web API service can be safely disabled after upgrade, so long as its only consumer was PI Vision.
-
PROBLEMA NA ATUALIZAÇÃO PI JDBC 2017-2018
Problemas encontrados na atualização da versão 2017 para 2018.
Quando a biblioteca de conexão tenta acessar tal funcionalidade ocorre a excessão "PreparedStatement#addBatch() is not implemented yet".
Problema similar ocorre com o uso da opção setReadOnly que deixou de ser suportada na versão 2018 do driver. Quando
o método abaixo é invocado uma excessão é lançada o que causa problemas na nossa implementação. Talvez uma solução
seja adicionar uma mensagem de warning como a realizada no método setTransactionIsolation.public void setReadOnly(boolean readOnly) throws SQLException {
throw new SQLFeatureNotSupportedException("setReadOnly() is not supported by PI JDBC Driver.");
}public void setTransactionIsolation(int level)…
1 voteThis issue is captured in the following article: https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=9082033616497176861-131099
-
Time Context Value Retrieval
Example Scenario:
We want to know the Specific Electricity Consumption (kWh/mt) over a time period (selected by users).
Specific Electricity Consumption = (Electricity Consumption(kWh)) / (Raw Feed Consumed(mt))
Where, Electricity Consumption (kWh) and Raw Feed Consumed (mt) are both attributes with PIPoint data reference, using value retrieval method: TimeMethod = Time Range; TimeRangeMethod = Total; EventWeighted
Then, Specific Electricity Consumption is attribute with Formula data reference, simply: A=Electricity Consumption; B=Raw Feed Consumed;[A/B]
So, on PI Vision, it can display the specific electricity consumption with the correct values. However, if we query through PI Web API for our own webpage, it…
7 votesThis can now be done natively with PI Vision 2020 using the Time Range retrieval mode without using PI Web API.
- Don't see your idea?