This is a WT* moment in my opinion. Filemaker Go does not support the Import script function except from Filemaker databases and NOT from XML datasources from a website. Enter “Import From URL script step” to solve my issue. For the interim this means that for a work-around for my deadline, I had to copy the dB, work with Filemaker Pro desktop version to do the import, then upload this 2nd file to Filemaker Go a 2nd database. The alternative was to change the special API I made to prep the data into a properly formatted Filemaker FMRESULT xml file. The Import script step does NOT tell you on the help page this is the case – just the FM Go developer guide and the “NOT COMPATIBLE” text (the script line does NOT turn grey). This means at least 30% of the work I did to make the XML output from the other system was wasted effort.  I fought a little with the aspx that worked on a previous project and found that with the new .NET 4.5, I had to export an application\xml header explicitly before spitting out the XML data – had I known, I would have not had to fight because exporting text on a webpage is VERY clear to me. Alas, lesson learned – use Import From URL and parse text. This seems like a step backwards.

Well, I think there is hope to get my one FM dB on Filemaker Go by using the Import from URL script step. This guy as a great article about the topic which I wanted to save and share. I will have to export the data in a simple format, but I can use a loop through the text and import one record at a time from this text. I THINK I also need to put a retry loop in the system and a marker for end of data to ensure I have all the data (perhaps I don’t require it, but paranoia and only doing this once reigns!