![]() ![]() saw fit to add that little dialog box in Export Field Contents. In the end (ian) it seems like a lot of hoops to get what you want - it would be great if the development team at FileMaker Inc. I hope to have a demo of FM-TimelineJS posted soon which will demonstrate the technique I employed with ScriptMaster. ![]() I found the documentation for 360Works easier to follow and settled on it, although BaseElements doesn’t require Java, so it might have been the better option. Next up, I had a look at two free plugins: BaseElements free plugin and ScriptMaster from 360Works both of which offer the ability to write out text files. I dismissed AppleScript because it was not cross platform. This is the point where I started to look at plugins or AppleScript to achieve my goal. Since we are exporting from a Global Field and a single record, we should have no repetition in the exported file. When you Omit that record and Show Omitted Only, you end up back where you started, but with only one record showing. When FileMaker does a ‘Show All Records’ it remains on the record you started with. The net result is to isolate a single record for the purpose of exporting. Choose whichever technique works best for you. and finally, use the ‘Export Records’ step instead of ‘Export Field Contents’.Īnother way to achieve the same result would be to put the record ID you are on into a script variable and ‘Perform Find’ on it.We are using a step designed for exporting multiple records on a single field of single record, a workaround necessitated because the popup is missing in the Export Field Contents dialog box. ![]() Firefox would not load the UTF-16 files.īack to the drawing board, I decided to try the other Export route, Export Records, because it does have the ability to specify the character set.įortunately, there is a workaround.In my situation, the switch to UTF-16 caused problems because when the Javascript ( TimelineJS ) I was using reached out to Google’s Youtube API (which is UTF-8) it became confused and would not load a preview of a YouTube video.I could view the files in Safari on a Mac properly. It would be very useful if the next revision of FileMaker Pro included the ability to select different character sets in the Export Field Contents dialog box.Īt this point, I tried re-saving all my Javascript files as UTF-16 to see if this would solve the problem. The Javascript files that will read this JSON file are formatted to use UTF-8 characters. The only thing missing here is there is no way to select the file character set format and the problem is that FileMaker Pro defaults to UTF-16 at this point. In this case, I have generated a meaningful name and the path is set to my Desktop. Once I select the field to export, I am given the option to Specify the Output File’s name and path. This can create problems because JavaScript files are usually interpreted by the browser as UTF-8 encoded. There is a big gotcha in using Export Field Contents however-it exports to the UTF-16 character set with no option to select UTF-8. When generating an HTML or JSON file, it is often more convenient to put all your text into a single field and then just export that field. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |