title: Best Practice in OData for exceptions
body: <p>We are consuming OData service using dot-net.</p>
  
  <p>When any exception throws in the odata service code or any business logic problem fails, service code handles that exception or error and return dotnet consumer a new error object with that error details.</p>
  
  <p>Is it good way of doing as I am thinking it should throw an exception and at consuming end I should handle it in my own way. </p>
  
  <p>What are your suggestions ? </p>