Share
Report
5We are working on an integration from a CRM system where users update sales order headers and lines within CRM. The requirement is that either updating the header or line should trigger a corresponding update to the order in GP. My client does not want to use the GP Web Services since they had a miserable experience with them. We've investigated the econnect DLLs, but the serialization/deserialization is something they would like to avoid. Ideally, they want to use just the econnect stored procedures. In reading the documentation it sounds like you have to be super careful on updates. For example, when updating a line, do you have to call taSopLineIvcInsert on just the line being updated or all of the lines. Additionally, do you also have to call taSopHdrIvcInsert as well (or other econnect procs)? When calling the procs, do you really have to retrieve all the values for the existing line and header form the database and pass those into the parameters to the stored proc?
I noticed on the GP web services that the entire order object (header, lines, payments, holds, etc) is retrieved before you try to update the order. Do you have to do the same thing with the stored procedures?
*This post is locked for comments
All responses (
Answers (
