![]() The location of the XML files also isn't critical, although BaseElements does write to the folder containing the XML files, so you do need read and write access to that folder. The name of the report isn't critical, although it's simpler to just leave it as the default ( Summary.xml on English platforms ). Click Create and choose a location to save your XML files to. Change the Report Format to " XML", and you can also uncheck the "File Handling" checkbox. In the dialog, make sure all of your solution files are checked ( default ) and all of the options are checked ( default ). Open a copy of all of your solution files in FMPA and then go to the Tools menu, and to "Database Design Report.". Without this report, and thus also without a copy of FMPA to generate it, you can't run BaseElements. Installed and used the plugin 'Windows exe runner. to analyse if there is an issue with Jenkins resources. exe as a service by using the keyword 'start', but this time Jenkins does not freeze but the executable does not run. We use this report and tranform it into useful data which we then import into BaseElements. As some have suggested I have tried to run. The DDR is generated by FileMaker Pro Advanced and is a complete documentation of all of the elements in your solution. ConvertFromFileMakerPath ( $filemakerPath PosixPath ) //Convert FileMaker to Mac/Linux Plugin PathĬonvertFromFileMakerPath ( $filemakerPath WinPath ) //Convert FileMaker to Windows Plugin PathĬonvertToFileMakerPath ( $pluginPath PosixPath ) //Convert Mac/Linux Plugin Path to file://Mac path.ĬonvertToFileMakerPath ( $pluginPath WinPath ) //Convert Windows Plugin Path to file://Windows path.BaseElements requires the Database Design Report ( DDR ) to get the data that it imports. A "plugin" path is the same as the PosixPath for Mac or Linux, and the WinPath for windows operating systems. By passing the AWS key and secret in the command the problems with environment variables is solved which makes troubleshooting from the command and BaseElements identical environments. The best way to convert paths is to use the native FileMaker functions ConvertFromFileMakerPath and ConvertToFileMakerPath. Simple way to interact with AWS CLI using FileMaker, BaseElements on Mac OS. Note the consistency of the type of slash used, vs the difference in \ vs / in Windows/Mac. If command is a null pointer, checks if the host environment has a command processor and returns a nonzero value if and only if the. Returns an implementation-defined value (usually the value that the invoked program returns). ![]() bin/sh, cmd.exe, ) with the parameter command. Windows : file:///C:/Users/John Smith/Documents/test.xlsx Calls the host environment's command processor (e.g. FileMaker Path Examples Mac : file:///Volumes/Clients/contacts.txt You can then adjust this path to suit whatever location you need, or to get an example of the difference between selecting a file on the desktop and running the Get ( DesktopFolder ) function. This will return an example of the sort of path used by the function. To get an example of the sorts of paths that the plugin uses, use the BE_SelectFile function in the Data Viewer, and choose a file with a known path. ![]() If I want to change directories then return the working directory, this doesn't work as I onl. Windows : C:\Users\John Smith\Documents\test.xlsx Am I missing something - but I can't run more than one command using BEExecuteSystemCommand. Plugin Paths Examples Mac : /Users/John Smith/Documents/test.xlsx" So if you're mixing and matching FileMaker paths and plugin paths, you will need to convert them between the types in order to use them in other places. These file: prefixes that you get from things like the Get ( FilePath ) function and others, are unique to FileMaker and don't work anywhere else other than FileMaker itself, including not in the BE plugin. On the Mac, they usually start with /Volumes or /Users and on windows will be something like C:\Folder\Path.įileMaker paths often start with file: or filemac: and these WILL NOT work in the plugin. The paths used by the plugin are Operating System paths. Please note :įileMaker paths and plugin paths are not the same thing. Lots of the BE plugin functions use paths in the parameters or in values they return.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |