We use attributes to reference elements and attributes extensively to model context and relationships in our AF models. Is this going to be supported in the future? Kind regards, Gregor6 votes
This item is under review. Currently considering the following behavior for attributes links:
Error returned: “Unsupported data type: ‘OSIsoft.AF.Asset.AFAttribute’.”
Similar error for AFElement.
Change under consideration:
Value link for Attributes of value type “Attribute” returns the referenced attribute’s GET response (“/attributes/[webid]”)
Value link for Attributes of value type “Element” returns the referenced element’s GET response (“/elements/[webid]”)
Add auditing or a view of statistics for the calls or requests done by each individual application. Allow a PI Admin to see which user or application is making a specific call and see how long it takes to complete to monitor performance and potentially resource intensive Web API calls.51 votes
We are researching and evaluating opportunities to expose PI Web API health, diagnostic, and basic telemetry data.
The channel/websocket feature of PI Web API would be more useful if it was possible to subscribe/unsubscribe to attributes on an existing channel connection. Currently you have to open the connection with all the WebIds you want in the resource URL. If you want to change which values you are receiving, you would have to close the connection and open a new one. Adding this new feature would also solve issues with maximum URL length limitations.4 votes
This is an issue we definitely need to address for both the reasons you suggested. We should be able to add and remove attributes while a channel is open. We also need a mechanism for signing up for large numbers of WebIds when the list would be too long for a URL.
The OPC landscape is shifting away from DA/HDA and towards UA servers. A significant number of OPC client tools are being created that connect to OPC UA servers, and none of these are compatible with PI without the use of a third party UA wrapper since we only provide DA and HDA servers.131 votes
We have been gathering use cases and information about OPC UA Server functionality as it pertains to OSIsoft products.
There are a number of different requirements to consider, and as such we’re changing the status back to “UNDER REVIEW / RESEARCHING” to more accurately reflect the current status of the work.
At this time, we are not committing to bringing this capability to market.
We will update this thread if the status changes.
As a programmer, I want to be able to use the PI Web API to find out about changes in the PI System. This mean Elements, Templates, Attributes, Event Frames and PI Point configuration changes.6 votes
“Finding changes in the PI System” is still being evaluated.
Correction: Previously this was shown as “planned” and part of Stream Updates. Stream Updates will allow you to retrieve data updates instead of having to retrieve the entire stream.
The upcoming PI Web API 2018 SP1 release will tell the caller if the stream has changed (e.g., the PI Point data reference was changed to a different PI Point), so that the caller can re-subscribe to the correct stream. It will not provide a mechanism to know what specifically those changes are on the stream, nor on the entire PI System.
As a PI user, I want the OPC DA and HDA Servers to honor the Windows identity of any connected OPC client.3 votes
We understand the requirement. It makes sense. We have been looking into it but it turns out to be difficult to do. We used a third-party framework to build the PI OPC DA Server which separates interactions with the OPC client from interactions with the PI Data Archive. It solved a number of problems but unfortunately there is no easy way to have OPC client user credentials flow to the PI Data Archive. We are evaluating our options.
- Don't see your idea?