May 3, 201015 yr Given this XML... <?xml version="1.0" encoding="ISO-8859-1"?> AB:123456 AB ALPHA BETA 123456 FUNK FUNKINESS MEDINA FUNKY COLD MEDINA AB 123456 FUNKY COLD MEDINA AB 123456 FUNKY COLD MEDINA WITH 14 SILVER SPARKLY THINGAMAJIGS This is the best Medina you've ever experienced. Really redefines the concept of Medina in all its funkiness. FUNKYCOLD.JPG http://www.example.com/images/FUNKYCOLD.JPG http://www.example.com/images/thumbs/FUNKYCOLD.JPG FUNKYHOT.JPG http://www.example.com/images/FUNKYHOT.JPG http://www.example.com/images/thumbs/FUNKYHOT.JPG User Guide FUNKYGUIDE.PDF http://www.example.com/pdf/FUNKYGUIDE.PDF Quick Specs FUNKYSPECS.PDF http://www.example.com/pdf/FUNKYSPECS.PDF N/A N/A $39.95 29% true N/A N/A 21% N/A N/A $99.95 $89.95 true $69.95 $59.95 $49.95 true $29.95 ZIP:008999 ZIP ZIPPADYDOODAH 0089999 SLIPPERS SLIPPERS FOR YOUR FEET GLASS GLASS SLIPPERS ...is there a reason this XSL won't work? Getting "invalid document structure errors"... <?xml version="1.0" encoding="UTF-8"?> 0
May 3, 201015 yr AFAICT, the problem is with the source XML document - it appears to be cut off in the middle.
May 3, 201015 yr Author Sorry...I was just posting a sample. The XML document does in fact continue, containing 9799 items (or rather sections). Thought a single example might suffice : But it is properly terminated at the end. Note that this document does import if I use the generic msdso_elem.xsl stylesheet which comes with FMP, so I'm thinking the basic XML is OK. The problem with using that is that it only picks up the "parent" elements (4 fields for each record: classification, marketing_copy, media, and managed_data. I need to get the stuff under those elements.
May 3, 201015 yr Can you zip your XSL stylesheet and attach it here? What you posted seems fine to me (apart from some path errors - but those wouldn't cause Filemaker to stop). However, the forum doesn't like XML code, so one cannot be sure.
May 4, 201015 yr I have no problems importing your source XML (after closing the open tags) using your stylesheet. source_Converted.zip
May 4, 201015 yr Author Thanks again for all the help - the problem turned out to be a namespace declaration in that top element. For some reason the FMP "msdso_elem.xslt" didn't care about that, but the one I wrote did.
Create an account or sign in to comment