[FX.php List] [Off] Import RAW XML to a field - FM9

Tim 'Webko' Booth tim.webko at gmail.com
Thu Nov 1 16:17:37 MDT 2012

Well actually, the php gets involved at the next stage, when I send it off
to an external API...

I just want the XML in a field to be available for part 2 - all of it,
already transformed, and without extra linebreaks that FM9 is inserting
when it exports it in the first place.

Export multiple fields via XML and use an XSLT to turn it into nice XML
Import back to a single field
Use a web viewer to self submit the XML and some other data to a php
handler to external API
Use a second web viewer to check the final results and scrape some info
back into FileMaker

So, very tangentally somewhat php - but the people here are smart ;_)

My current workaround - for step 2, import to a temp table, loop the
records and create a variable that then gets pasted into the relevant field
in the main table. Which works, but I'm just annoyed that different
versions of FM create slightly different XML files from the same input.

And that I can't web enable these systems for doing this...

On 1 November 2012 23:31, BEVERLY VOTH <beverlyvoth at gmail.com> wrote:

> how are you re-importing 'to a field', Webko? Since this is the fx.php
> list, I just wondered how php is involved, if at all?
> Thanks,
> Beverly
> On 31 Oct 2012, at 9:33 PM, Tim 'Webko' Booth wrote:
> > OK...
> >
> > I can quite happily get FM 11 to export a transformed XML and then
> re-import it to a field. It creates XML that looks like:
> >
> > <?xml version="1.0"
> encoding="UTF-8"?><party><party-type>Person</party-type><surname>Booth</surname><first-name>Time</first-name><birth-date>None
> of your beezwax</birth-date></party>
> >
> > This is good.
> >
> > FM9 seems to insist on:
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> >
> <party><party-type>Person</party-type><surname>Stevens</surname><first-name>Linda</first-name><birth-date>1970-3-15</birth-date></party>
> >
> > Worse, that return appears to be something like a CRLF, as I get three
> records if I import to a test database.
> >
> > Is there a way to persuade 9 to not do this?
> >
> > If it was just one return, the workaround is fairly easy - just tell it
> that the first record is headers, and then paste the XML declaration back
> in later. But two is annoying - I'd have to create a new sub-table, import,
> paste the master ID and create a link to then concatenate the related
> records...
> >
> > This project all looked so good until these old version compatibility
> issues started...
> >
> > Cheers
> >
> > Webko
> > _______________________________________________
> > FX.php_List mailing list
> > FX.php_List at mail.iviking.org
> > http://www.iviking.org/mailman/listinfo/fx.php_list
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.iviking.org/pipermail/fx.php_list/attachments/20121102/da33e0da/attachment.html

More information about the FX.php_List mailing list