In this case, we need to provide the plugin with a standard path, not a FileMaker path. One example of this is when a plugin is used to interact with the file system. Occasionally we have to use a path (that we have constructed within FileMaker) with an external system. For example: 'file:' & Get ( DesktopPath ) & 'my.pdf' External Systems Specify file for Import Recordsīut if we want to adhere to the documentation, we can simply add the appropriate prefix – such as file: – to the path. The product documentation states that script steps and FileMaker dialog boxes requiring a file path should use a properly formatted FileMaker path (although the paths constructed without a “file:” prefix seem to work just fine). = '/C:/Users/mkos/Desktop/' // on Windows = '/Macintosh HD/Users/mkos/Desktop/' // on mac FileMaker Get FunctionsįileMaker Get functions that return file paths also use the FileMaker path format, but most of them omit the scheme prefix. You can read more about the standard file URI scheme. Depending on what the rest of the path looks like, this kind of path could be either a FileMaker path or a standard file URL path. The exception is paths that begin with file:// (two forwards slashes).

In other words, the operating system won’t know what to do with the path. With one exception, if a path begins with any of the prefixes described above, it is exclusively a FileMaker path.

Here are some examples of OS-specific FileMaker paths: Using one of these extensions is optional and is done to explicitly indicate that the path is only intended to be used with that particular OS. The file/image/movie prefixes can also have an OS extension: mac, win, or linux.

Filemaker 19 mac