March 10, 2010 at 9:56 pm
I am using SSIS to import data from xml.
I have xsd files supplied by the vendor.
The initial issue was that the SSIS import using xml source did not pick up attributes in the root node.
I resolved this using xml task to do an xslt operation and basically put a <Root> node at the beginning and end of the xml file and then modify the xsd to have the extra level. So far so good (but man that feels like a hack).
However now a new vendor has given us a new set of xml files and they use ref= in the xsd.
When I whack the root node in now all the ref statements fail as they can't see the element definition as they are no longer "blah" but "Root\blah".
I have tried every type of delimiter I can think of to change the ref="blah" to ref="Root:blah" (substitute \ and / and : and a few others for the : in that example) but I still can't use the xsd.
If anyone has an idea to resolve this in a simple manner (ideally "oh yeah fix the root thing by applying this service pack" hehehe) I would be eternally grateful and happily buy beer.
I would prefer not to have to do a massive xslt write as this is, like everything in my sad unfortunate life, on a tight deadline. We can apparently go back and do it properly later (yeah right).
Thanks in advance anyone with ideas.
Viewing post 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy