COMMUNITY FORUM

That error normally occurs if the map is grouped correctly compared to the key fields selected for the data source.

What can happen is if the grouping isn't correct on the header node (taPoHdr) then it will appear in the xml file sent to eConnect multiple times. This causes eConnect to throw the error you posted.

If you send the map to GP-File you should be able to look at the xml file and see how many times the taPoHdr record appears in the xml, it should be just once. Then you can adjust your key fields/grouping on that node to get it working.

H

Thanks Chris.  That got me over the hump.  I played with the key fields and was able to get past this issue and onto the next one.  I'll keep working at.

Thanks again.

It appears I'm at an impass on this map. I have an xml file which I need to import into a GP purchase order. The xml file structure is as laid out below:

<PO Header>
<PO Num></PO Num>
<PO Date></PO Date>
…
<PO Line Item>…</PO Line Item>
<PO Line Item>…</PO Line Item>
<PO Line Item>…</PO Line Item>
<PO Line Item>…</PO Line Item>
</PO Header>

If I choose an XML source I only see the PO Header info and none of the line item nodes. If I choose an XMLQuery source it flattens out the xml file into a nice table like layout. The only problem is that all of the PO Header fields only appear on the first row in the results.

Next I attempt to map the import and feed it into GP. It runs successfully, but finds two PO's in the source file when there is only one (1 valid PO and 1 PO with a blank PO #). Only the header and first line item import to GP because there is no PO# on the other 3 lines. If I switch the key field to be the PO# that is referenced in every line of the flattened xml preview (from the <PO Line Item> node) then I get the 'Node taPoHdr not found in POPTransactionType' error.

So it seems that I either need a way to get the PO Header node repeating in every line of the flattened XmlQuery OR I need a way to use a different key field that doesn't come from the PO Header node. Can you make any suggestions?

PS. When I output it to a GP File, I found that I am allowed to use the PO# from the <PO Line Item> node without error and it generates a perfect file. The run only identifies one PO in the source file and produces an xml file for eConnect to consume with 4 line items in it. So it seems the GP File output behaves differently than the GP output.

It appears I'm at an impass on this map. I have an xml file which I need to import into a GP purchase order. The xml file structure is as laid out below:

<PO Header>
<PO Num></PO Num>
<PO Date></PO Date>
…
<PO Line Item>…</PO Line Item>
<PO Line Item>…</PO Line Item>
<PO Line Item>…</PO Line Item>
<PO Line Item>…</PO Line Item>
</PO Header>

If I choose an XML source I only see the PO Header info and none of the line item nodes. If I choose an XMLQuery source it flattens out the xml file into a nice table like layout. The only problem is that all of the PO Header fields only appear on the first row in the results.

Next I attempt to map the import and feed it into GP. It runs successfully, but finds two PO's in the source file when there is only one (1 valid PO and 1 PO with a blank PO #). Only the header and first line item import to GP because there is no PO# on the other 3 lines. If I switch the key field to be the PO# that is referenced in every line of the flattened xml preview (from the <PO Line Item> node) then I get the 'Node taPoHdr not found in POPTransactionType' error.

When I output it to a GP File, the run properly identifies one PO in the source file and produces a perfect xml file for eConnect to consume with all 4 line items in it. It seems the GP File output behaves differently than the GP output.

So it seems that I either need a way to get the PO Header node repeating in every line of the flattened XmlQuery OR I need a way to use a different key field that doesn't come from the PO Header node. Can you make any suggestions?

Take a look at this thread, it is trying to do the same thing you are talking about. http://www.eonesolutions.com/Support/Forum.aspx?forumid=21&fpage=1&threadid=105

I am already using the XmlQuery source and only getting the header row and first line item coming through in the results when I send it to GP.  If I send it to a GP File I get the header information and all 4 line items.

It seems that the main issue is evident when I preview the data and it looks like this:

HdrPONum   HdrPODate   LineNum   LinePONum   LineItem
—————    —————   ————   —————-   ————-
10023            12/12/2012   1                10023            LUGNUT
                                           2                10023            COG
                                           3                10023            NUT
                                           4                10023            BOLT

The XmlQuery source isn't repeating the header node on each row of the flattened information.  So when I run the map it says it found 2 PO's in my file:  PO#10023 (line 1) and a blank PO# (lines 2, 3 and 4) and fails to import the lines with the blank PO#. 

How can I either get the header information repeated on all 4 line items OR use the LinePONum as the key which works when going to a GP File?

[quote=marcb@progressive-solutions.com]I'm attempting to build a purchase order import for GP and am stuck on an error that I can't make sense of.  When running the map it finds 1 record to import but fails every time with this error:

     "Node taPoHdr not found in POPTransactionType.  The element node is required for this transaction type"

I have mapped this node (aka. Create purchase order) in the setup of the map and see records when I preview from the mapping window.  It seems to be picking up different information when running the map vs building it.

Details:
– Version 20.12.1.8
– Source:  Folder xmlQuery
– Destination:  Dynamics GP Purchase Order[/quote]