Hi,

I wonder if anyone can shed some light on something rather worrying...

I have some XSL's written so that we can import XML files from a data-supplier they work fine except for a few which came through last week.

Please see the attached image for the error, if I re-import previous and some new XMLs they still import fine but there is a batch that don't.

I had them resent and tried parsing them through Validator and TestXSLT and they seem to be valid!!

I can provide samples if required.

Edited April 30, 200718 yr by Guest

Your XML file that you try to import is not valid XML.

please find attached an xml and one xslt, the xml "seems" valid from what I can see from a normal XML validator, but I'm no XML junkie (yet -lol)

xmldemo.zip

With Saxon 8.9 your example transformed fine.

Could be the encoding of the XML file (which is ISO-8859-15). Change it to UTF-8 and try to import again.

Which FileMaker version are you using? Could be that the Xalan XSLT processor used there is not the newest version.

It worked as is for me. Except you are missing a field in you Metadata definitions. The "Type" field, which goes between "TypeID" and "Text". Without it the order is thrown off; you already have it in the Resultset selections.

Hi fenton, when you say it worked for you do mean it worked in FileMaker fine without any modification?

I noticed that deleting the content of the Text column from the xml allows for FileMaker to import the XML fine, does FileMaker have any restrictions on XML or length of a file?

Yes, it worked for me fine. No, I don't think there's a length limitation, except the basic FileMaker text field limitation, which is HUGE (1 billion characters). It could be that there's some special character in the text that's making it choke. But, as I said, it imported fine for me, other than the field order being off.

The Text field has got quite a few little errors in it, extra characters, ^, #, %, extra spaces. It looks like it was hacked out of a web page or something.

Hi Fenton, may I ask exactly what you did...

i.e a step-by-step idiots click guide as i have tried it on 2 different macs and the same error occurs one mac is intel one is PCC both in FMP and FMA 8.5 running 10.4.9.