This module contains handy FileMaker-specific Angular directives.Ĭontainer field with drag-and-drop editing support. Returns a promise containing the updated record. $performScript(scriptName, scriptParam)Ĭonvenience method which saves the record, passing in a -script and optional -script.param as well. It runs as a web-based java application which allows you to upload, view, and download scaled images and files from an embedded web viewer in FileMaker (introduced in FileMaker 8.5). Will execute a -delete operation for the record. SuperContainer eliminates the hassle of dealing with container fields in FileMaker. Will save the record to the database, returning a promise containing the updated record. In addition to data attributes, Records have the following methods: $save(optionalArgs) Most FMAngular methods return a promise containing an array of Record objects. (Thanks to Michael Wallace from for contributions here.) Returns a promise containing metadata about the given layout (currently only valueLists by name). Consult the XML publishing guide for details on how to format this request. Note that find request keys must use the FileMaker field names, not the sanitized JavaScript identifiers.įind a random record. Specify find requests in the parameters object, in addition to the required -db and -lay parameters. This returns a promise object containing an array of parsed record objects.Īt minimum, you will want to specify -db and -lay parameters as well as an action such as -find, -edit, etc. Most FMAngular methods are convenience wrappers around post. Sends raw POST request to the web publishing engine, parsing any resulting records. ScriptMaster integrates tightly with your FileMaker solution. It comes out of the box with modules for file manipulation, URL and network utilities, Web Services, shell scripting, event/script triggering, and many others. config ( function ( fmangularProvider ) ) 360Works ScriptMaster ScriptMaster is a free, general-purpose, modular plugin. This keeps your FileMaker files trim and. SuperContainer stores all data as individual files outside your main FileMaker database. This can lead to very large file sizes, which are difficult to transfer and back up. Example Usage The following illustrates the various ways of working with the ScriptMaster plugin. In addition, there is a handy fm-container directive that allows you to send upload data from the browser to FileMaker as a Base64-encoded string. Also, to use regular container fields with FileMaker Go, your container data must be embedded inside your FileMaker database. jar is stored in FileMaker, deploying new versions of the java code to the FileMaker clients is as easy as updating a single container field. Specific steps on setting these headers are discussed here: #4įMAngular converts FileMaker XML with potentially unusable field names to JavaScript objects with $recid and $modid attributes as well as $save(), $delete(), and $performScript() methods.įileMaker dates and timestamps are parsed into native JavaScript Date objects, which allows correct sorting behavior. If the app and database are on the same host, there is very little configuration required to start using FMAngular. Be aware that pointing to another server will require setting Access-Control headers on the FileMaker server. Want to add a field? Just put it on your layout, and it will be available to your Angular app.įor this to work, your Angular app must be hosted on the same machine as your FileMaker XML Publishing engine, or else use the fmangularProvider.url() method to specify an alternate URL. Publish your FileMaker database to the web with no PHP back-end. Meanwhile, here's another way to fix the dot-in-filename problem that eos pointed out: The two colons before Title make it an impossible/illegal export path, aside from which it isn't what you want and each record would overwrite the previous record's exported file if it was working. What you've got it doing is setting $ExportPath to the literal textstring filemac:/Macintosh HD/akafm/Documents/test/XXXX Collection::Title So that if XXXX Colleciton::Title happens to contain the value "Venice Bridge.jpg", for example, $ExportPath would be filemac:/Macintosh HD/akafm/Documents/test/Venice Bridge.jpg You want the $ExportPath to consist of a text string consisting of the hardwired path part, "filemac:/Macintosh HD/akafm/Documents/test/", concatenated with the field value, XXXX Collection::Title The ampersand, &, connects to it the actual value in the field XXXX Collection::Title. That's the end of the literal text string. Note of the end-quotation mark after test/. If not, assuming that you inserted the files originally using Insert File and that the files had extensions (i.e., that they don't date back to MacOS 8.6 and don't have them) this may not work as intended if you pasted from the OS clipboard into container fields or if you used Insert Picture instead of Insert File. This assumes that your text field contains the.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |