AnsweredAssumed Answered

Streamset AdHoc error handling

Question asked by AbelHeinsbroek on Aug 27, 2018
Latest reply on Aug 27, 2018 by AbelHeinsbroek

Hi All,

 

I'm building an optimized PI Web API wrapper that collects value, recorded, etc, requests and groups them into a single Streamset Ad Hoc request.

I'm running into the following problem however: as soon as a single WebID cannot be found, the whole requests fails with a single error.

 

For example:

 

https://devdata.osisoft.com/piwebapi/streamsets/value?webid=P1AbEUElTUlYxXE5VR1JFRU5cTlVHUkVFTlxMSVRUTEUgUk9DS1xESVNUSUxMSU5HIFBST0NFU1NcRVFVSVBNRU5UXEYtMjcyfEFTU0VUIE5BTUU&webid=P1AbEUElTUlYxXE5VR1JFRU5cTlVHUkVFTlxMSVRUTEUgUk9DS1xESVNUSUxMSU5HIFBST0NFU1NcRVFVSVBNRU5UXEYtMjcyfEJMQURFUw&webid=P1AbEUElTUlYxXE5VR1JFRU5cTlVHUkVFTlxMSVRUTEUgUk9DS1xESVNUSUxMSU5HIFBST0NFU1NcRVFVSVBNRU5UXEYtMjcyfE5PTiBFWElTVEFOVA&webIDType=PathOnly

 

Contains two correct WebIDs and one nonexisting, causing the complete request to fail with a single error. Ideally the PI Web Api would include the errors per WebID inside the returned Items array.

 

Does anyone know a good solution for this problem? Checking each attribute existence prior to the batched streamset request would defeat the purpose of batching the requests. Using templates alleviates the problem somewhat, but we still run into issues when elements contain custom attributes.

 

Regards,

 

Abel Heinsbroek

Vitens

Outcomes