Options

Unexpected element in a xmlport

abultelabultel Member Posts: 14
Hello all,

I am trying to import an xml file and I have always the message :
"Unexpected Element HABILITATIONLIST although this tag is in my XMLport in the right position.

Does anyone have an idea to solve the problem ?

Thanks in advance

Arnaud Bultel
Bultel Arnaud
ATOS ORIGIN

Comments

  • Options
    DenSterDenSter Member Posts: 8,304
    Did you make sure it is spelled correctly?
  • Options
    ara3nara3n Member Posts: 9,256
    Make sure it's the correct CASE
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • Options
    abultelabultel Member Posts: 14
    Thanks for your answer.
    In fact, the problem was in the xml file.
    The opening tag must be closed at the end of each record and not at the end of the file.


    Best regards

    Arnaud Bultel
    Bultel Arnaud
    ATOS ORIGIN
  • Options
    jversusjjversusj Member Posts: 489
    hello. I am having this same problem and cannot figure it out!

    I have defined the element properly in the XMLPort: proper CASE, proper spelling, proper indentation, yet when i try to pull in my file, i get: the Element <ItemID> is unexpected.

    the file is formatted like this:
    <ItemOut lineNumber='1' quantity='10' requestedDeliveryDate='2008-10-20T00:00:00-00:00'> 
           <ItemID>
             <SupplierPartID>0117633603</SupplierPartID>
           </ItemID>
           <ItemDetail>
              ... more elements...      
    </ItemOut>
    

    when i remove the ItemID section from the XML file, and set ItemID minOccur to zero in my XMLPORT it works fine. it brings in my item details as expected.

    any ideas?

    edit: DANG! i need to step away from my cube. as soon as i posted this, i went back and looked at my XMLPort again, and while ItemID was setup properly, the subsequent element SupplierPartID was not.

    Sorry everyone. i knew it had to be something i was doing wrong!
    kind of fell into this...
  • Options
    SogSog Member Posts: 1,023
    Experienced the same problem but with a different solution.
    The element <element> was unexpected
    this error occured when I changed <element> from sourcetype field to sourcetype text
    When I edited the xml file from <element></element> to <element/> the import worked.
    Could this be a bug?
    |Pressing F1 is so much faster than opening your browser|
    |To-Increase|
Sign In or Register to comment.