Epicor REST API Help - InspProcessingSvc

Epicor ERP 10
1

Hi everyone, I was trying to work with my Rest APIs specifically Erp.BO.InspProcessingSvc.
I tried to send a GET request as below and just got back an error. Did I do anything wrong?

I really appreciate all the help I can get~
Thanks

image
image860×913 27.8 KB

image
image860×528 11 KB

2

Don’t use odata, just don’t.

Use the rpc endpoints.

3

Oh tysm, that was actually very helpful!

4

Unrelated question–I am just getting started with the REST API, is there a particular reason why you recommend avoiding using odata?

5

OData is a wrapper around the RPC endpoints and some have, uh, issues. We’re adding an extra layer of abstraction that might have errors.

And SOME PEOPLE will also recommend not to call the RPC endpoints at all unless it’s for a very basic single GetById. The recommendation is to only call Epicor Functions and perform the BO calls there. Why?

  • Calling the REST endpoints directly tightly couples your client to Epicor code making upgrades more brittle. You will potentially need to update each client on an upgrade where a function encapsulates the changes. Fix the function at the server and all your clients run without even knowing there was a change.
  • You have better error handling within functions, and you keep that error handling out of your client code.
  • You can reduce the number of calls over the wire by making multiple business object calls in a single function call.
  • Your payloads will be smaller than the generic REST endpoint
  • You have control of the function signature to make it easier for the client to consume.
  • You can shape the data that better suits your client.