You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
V5 introduces a new way to handle errors typically through ODataError object. In V4 we were using ServiceException object for the same purpose. I will provide an example on user fetch.
When you have single operation, calling GetAsync with inexistent user id would raise:
V4: throws ServiceException with ex.Error.Code == Request_ResourceNotFound
V5: throws ODataError with ex.Error.Code == Request_ResourceNotFound
But when you execute the same operation in batch, here is the output:
V4: throws ServiceException with ex.Error.Code == Request_ResourceNotFound
V5: throws ServiceException where you don't have an Error object anymore, information now is a part of RawResponseBody which you should deserialize manually.
Is it an expected behaviour? I would expect the batch request to throw the same error as when calling the statement directly, like it was in V4.
The text was updated successfully, but these errors were encountered:
V5 introduces a new way to handle errors typically through ODataError object. In V4 we were using ServiceException object for the same purpose. I will provide an example on user fetch.
When you have single operation, calling GetAsync with inexistent user id would raise:
But when you execute the same operation in batch, here is the output:
Is it an expected behaviour? I would expect the batch request to throw the same error as when calling the statement directly, like it was in V4.
The text was updated successfully, but these errors were encountered: