on 09-17-2008 9:54 AM
Hi SDNers,
As we r using MDM sp06 therefore we have to use Xsd while importing but it showing error when we r using standard business content XSD .From where can i find xsd for the xml file iam using .Is we have to use an XMl spy?
If yes then recommend which one we should use?
or
there is a other way round?
Thanks in advance,
Neethu JOY
what is the error though?
It can be because of XML Name space, in our case it was because of maxoccurs = 9999/99999999 in the default XSD, we changed it to maxoccurs = unbounded, and yeah it is always a good idea to validate XML against XSD.
Generate a sample XML using the xsd and try importing that , even then if it errors out before opening that stuff , then it is the problem with XSD.
But if sample XML goes thru and actual; data is bombing then apparently data is the culprit XML does not like to see bunch of illegal characters in the data and yes these kind of checks , XML SPY or any XML workbench can handle. good Luck.
-Sudhir.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Neethu,
Remove the Namespace from the XSD file and add the XSD in the XML Schema table of the repository. Now try to import the XML file.
Regards,
Jitesh Talreja
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jitesh,
Thanks for your reply.Could you please tell me where is this Namespace in xsd file ?Iam attaching part of xsd file.Is the highlighted one the namespace you are referring to.
<?xml version="1.0" encoding="utf-8"?>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name="EDI_DC40">
<xs:complexType>
<xs:sequence>
<xs:element name="TABNAM" type="xs:string" />
<xs:element name="MANDT" type="xs:unsignedShort" />
<xs:element name="DOCNUM" type="xs:unsignedShort" />
<xs:element name="DOCREL" type="xs:unsignedShort" />
<xs:element name="STATUS" type="xs:unsignedByte" />
<xs:element name="DIRECT" type="xs:unsignedByte" />
<xs:element name="OUTMOD" type="xs:unsignedByte" />
<xs:element name="IDOCTYP" type="xs:string" />
<xs:element name="MESTYP" type="xs:string" />
<xs:element name="SNDPOR" type="xs:string" />
<xs:element name="SNDPRT" type="xs:string" />
<xs:element name="SNDPRN" type="xs:string" />
<xs:element name="RCVPOR" type="xs:string" />
<xs:element name="RCVPRT" type="xs:string" />
<xs:element name="RCVPRN" type="xs:string" />
<xs:element name="CREDAT" type="xs:unsignedInt" />
<xs:element name="CRETIM" type="xs:unsignedInt" />
<xs:element name="SERIAL" type="xs:unsignedLong" />
Regards,
Neethu Joy.
Hi,
your XML file should validate with the XSD delivered with the standard content. You can check this using XMLSpy or another good XML editor. If it doesn't, you can use it to create your own XSD.
If you manually import, you can choose "XML" in favor of "XML Schema" in order to import without using an XML schema. For Import Server imports you will need an XSD.
Best regards
Christian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.