PI Server
Welcome to the
PI Server feedback page!
We created this forum to hear your ideas, feature suggestions and feedback on PI Server. 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.
-
AF Transformer sync functionailty
- AF Transformer should be able to sync changes made in the source AF Database: if an element is added, deleted or edited. For the deletions there should be a way to select the behavior: delete an object from the target database, place it under a different hierarchy, rename or do nothing.
- It would be also helpful to have an additional AF property in AF - deletion flag. A power user will be reviewing a list of elements flagged for deletion and will be making a decision - delete, rename, move or do nothing (similar to functionality in the connectors admin…
21 votes -
Allow passing parameters to XML script file so that I can maintain one general script for many sites
Below in the examples are the parameters that would change from site to site. Other than these parameters the transformation XML script is identical across sites. With parameters, it would be simpler to maintain these files.
• Host, Database and DefaultPIServer for both the DataSources and the Writers
<DataSources>
<DataSource MEFClass="AF" HighID="0" ID="5001">
<Properties>
<Properties Key="Host" Value="Param1" />
<Properties Key="Database" Value="Param2" />
<Properties Key="UserName" Value="" />
<Properties Key="Password" Value="" />
<Properties Key="DefaultPIServer" Value="Param1" />
</Properties>
</DataSource>
</DataSources>
<Writers>
<Writer MEFClass="AF" Enabled="true" Encoding="UTF8" ID="5002">
<Properties> …9 votes -
AF Transformer logging improvements
Improve AF Transformer logging:
In some cases it's hard to investigate why AF Transformer doesn't include certain elements in transformation.
it would be helpful to have a debug level that enables following features:
- log element names that were returned as a result of an entry point search that AF Transformer performs;
- log elements that were discarded by additional Value/Name filters in the Search shape.9 votes -
Allow specifying conditions (or case constructions) for ParentID/ElementID functionality
Allow specifying conditions (or case constructions) for ParentID/ElementID functionality. Example:
if [1].Value=x then ParentID=[2].value ElementID=[3].Name
else
if [1].Value=y then ParentID=[4].value ElementID=[3].Name
else
ParentID=[2].value ElementID=[3].Name8 votes -
Improve AF Transformer PostProcessing logging and performance
PostProcessing stage of the transformation (if using ParantID and ElementID) should use paging (or another approach) for a better performance, it should also be better logged and display number of objects processed, a number of objects in the list and paging statistics. It should also have a retry logic in order to avoid losing transformation results in case of AF Timeouts.
7 votes -
Allow specifying a path for orphaned elements for ParentID/ElementID functionality
Implement following logic for ParentID/ElementID functionality :
if a parent element is not found (invalid and/or empty ) - put a child element under specified hierarchy. there should be a separate configuration for both options: what to do when the parent is invalid and what to do when the parent is empty.6 votes
- Don't see your idea?