Hi
To allow historical access on our server, we are overriding HistoryReadRaw.
In some cases (example when 2 of 3 required parameters are not specified - StartTime, EndTime and NumValuesPerNode) the server must raise a service fault (BadHistoryOperationInvalid in this example).
When in HistoryReadRaw we do this :
return new HistoryReadResult() { StatusCode = StatusCodes.BadHistoryOperationInvalid }
The status is returned but at an operational level.
So question is : how can we set the service fault using code in HistoryReadRaw methog ?
Thanks
Returning service fault when overriding HistoryReadRaw
Moderator: uasdknet
-
- Full Member
- Posts: 9
- Joined: 24 Jan 2022, 17:13
- Support Team
- Hero Member
- Posts: 3070
- Joined: 18 Mar 2011, 15:09
Re: Returning service fault when overriding HistoryReadRaw
Hi Stephen,
you are not able to trigger a service fault from the application side. These can only be raised by the sdk.
But good news, we have addressed the history details check in the upcoming V3.2.2 release.
Stay tuned.
you are not able to trigger a service fault from the application side. These can only be raised by the sdk.
But good news, we have addressed the history details check in the upcoming V3.2.2 release.
Stay tuned.
Best regards
Unified Automation Support Team
Unified Automation Support Team