eConnect Document Exchange: Does it work?

(0) Share

Report

Posted on by chadbruels

1,588

Specifically I am wondering about taPopRcptLineInsert.

More generally though, I want to know if there is a definitive answer on eConnect nodes which do not have an UpdateIfExists flag and state: "This node uses document exchange for updates. All existing values are overwritten with the value specified by the update document. If a field in the update is blank, the existing value is changed to be blank."

I am trying to recall a case I had with Microsoft, which eConnect node it was for I do not remember, where I asked about updating a transaction which stated it used Document Exchange and had no UpdateIfExists flag. The result of the case was Microsoft telling me that type of transaction could not be updated via eConnect.

Can such nodes actually be updated? Does it depend on the node? Does it depend whether you call the stored procedure directly or leverage the library in .NET?

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (0)

Tim W 2,925 on at

Like (0)

Report

Hi Chad,

Back when eConnect first came out (8.0 launch but had a 7.5 component) it did not have the update if exists feature (maybe 10.0 for that? something like that) and prescribed solution was to bang SQL in the pre and then pass the values needing preserve back through the call as parameters. I think first project I did was customer/sales order integration and had to query sql for a number of customer fields to then pass back through the call as parameters so values would be preserved (tax id, class etc... probably four or five total) and it was just something to figure out.

Looking at the taPopRcptLineInsert node seems that's what you need here also.

One comment on UpdateifExists, I always read the fine print on it for nodes I'm using, it would be better called 'Probably Update if Exists',

Ex: To modify an existing SOP line, set the UpdateIfExists element of the <taSopLineIvcInsert> XML node to 1. You must include all the SOP line elements in the update. This includes both the changed elements and the elements that are not being changed. You need to also consider the following: ...etc....

Tim

Was this reply helpful? Yes No
chadbruels 1,588 on at

Like (0)

Report

"prescribed solution was to bang SQL in the pre" - I hope you can forgive me, I am not sure what you mean here. You mention the pre so I assume a reference to the matching pre script. So do you mean one must query the header table, then set the values to flow from the pre into the main procedure? I have just tested that and I still receive "Input variable contains a duplicate document (POPRCTNM)".

Was this reply helpful? Yes No
chadbruels 1,588 on at

Like (0)

Report

I can confirm the taPopRcptLineInsert does check the POP10310 table for the existence of the line and then errors out.

Is it a crazy idea to select all the table's columns in the Pre eConnect script, change the columns I need and pass them back in, but ALSO DELETING THE LINE in the table so it passes the main procedure's test? I'll answer my own question. Yes, it might be a crazy idea, but is it a stupid idea?

Was this reply helpful? Yes No

Community site session details

eConnect Document Exchange: Does it work?

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Featured topics

Product updates

Community site session details

eConnect Document Exchange: Does it work?

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Featured topics

Product updates