Returning service fault when overriding HistoryReadRaw

Questions regarding the use of the .NET SDK 2.0 for Server or Client development or integration into customer products ...

Moderator: uasdknet

Post Reply
stephenTissot
Full Member
Full Member
Posts: 9
Joined: 24 Jan 2022, 17:13

Returning service fault when overriding HistoryReadRaw

Post by stephenTissot »

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

User avatar
Support Team
Hero Member
Hero Member
Posts: 3064
Joined: 18 Mar 2011, 15:09

Re: Returning service fault when overriding HistoryReadRaw

Post by Support Team »

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.
Best regards
Unified Automation Support Team

Post Reply