REST Question on PO Detail

Epicor ERP 10
1

Hey all,

I am working with a developer on an integration to SalesForce. We are working on creating new PO Lines and he is telling me Part Class is required to create new lines on PO’s.

I am trying to validate if this is correct. I know Part Class is a required field but my assumption was that as long as the part has a part class on it, the part class value wouldn’t need to be passed in the REST call.

Any insight is appreciated and please excuse my ignorance, I am just starting to learn these REST API’s, excited for the course in Vegas!

Thanks,
Mitch

2

Have you worked with the ‘legacy’ API methods from a BL Tester or client customization POV?

The REST Methods are just wrappers over those existing methods. The Tracing, reverse engineering approaches applied there are the same for REST.

Are you taking the REST Extended Ed course or just break out sessions on REST?

3

I am really solid on the client customization/embedded toolset side. Not sure what you mean by legacy API methods? Like SOAP and Service Connect?

I think I understand what you are getting at there, I should just treat this like I am writing it from BPM and troubleshoot as if it is coming from there or a screen customization?

I am in the extended ed course. I assumed you would be involved there. Can’t wait.

4

I believe he is referring to the custom methods in REST. There is a link in the top right of the REST help page to switch between standard calls and custom methods (BO methods).

image
image.png1050×351 4.74 KB

These methods are mapped to the BO methods that you would call from inside the client.

5

A little of both. I was checking to see if you understood the legacy customization model and the normal approach for calling services in that customization through the client BOs.

Since you have that nailed, you can add a trace and determine what services, methods and data are needed for the functionality you are interested in mimicking.

Now you have a decision point. Do you want to use the same exact APIs as the client does today (the Custom Methods Chris mentioned above) or do you want to use the OData Methods?
Pro - They give you more granular control and are a bit more stable to use from version to version.
Con - Since they are not what the win forms client uses, the functionality is not 100% the same

Another alternative is to use a combination of BAQs for data querying and the OData update approach’s - Post, Patch