You are correct, Morgan. On Mac there is a work around for "export field contents":
there is an issue on windows, so the best bet is to loop thorough the "xml" field and push the data into a single field such that each 'return' (ascii 13) is a new record. This preserves the return-in-field that otherwise might get converted with Export as Tab-delimited.
Yes, plugins can export the contents 'as is'. As well as AppleScript.
Hi, you can do it using native Filemaker functions or using BaseElements plugin, which by the way is free.
In this URL you'll find a sample file with both methods, hope you find it useful:
Do you really need UTF-8? Most of XML processor can parse UTF-16, so you have chance to try writing your calculation as encoding="UTF-16", then "export field contents".
When the result is TEXT, it is not XML, so no xml processor and UTF-8 may be needed. But that's a good suggestion for XML!
Your One Field XSLT saved the day.
Not sure how useful the following is for is for anyone else - I'm sure there are much better ways to solve these problems, but if you are stuck making XML via text calcs (because like me you can't learn another way fast enough), this XSLT is extremely helpful. I'm keeping it in my 'very useful resources collection',
It exports a single field of text formatted as XML from a record verbatim.
But beware (this took me ages to learn), it only worked for me if my found set was 1 record- makes sense as it is not used with export field but rather used with 'export record' script step.
here is Beverly's link again
yes! one record, one field.