![]() ![]() FILEMAKER BASEELEMENTS LIST FOLDER ON MAC REMOTE PATH HOW TOĬan anyone point to documentation or guide me in how to call these routines within a script?Īll of these can be done in this plugin if you want to use it. You need to convert the internal ( OS ) path into a FileMaker path, set it into a variable and then use the variable in place of a full path in the import step. The "from" and "to" parameters are paths again. The best way to understand the paths are to run the functions BE_SelectFile ( "" ) and BE_SelectFolder ( "" ). They put up a dialog, and you can select a file or folder and then it will return the path to that file/folder. That way you can tell what the path should be, and convert to or from the standard FileMaker paths as appropriate. I must have a thick skull because I've tried several ways to get this to work. I have the path TO the files in a global field and need to get the LIST of the files into another field to loop through importing them. I have pasted the filenames into the field and the import script loop works fine. FILEMAKER BASEELEMENTS LIST FOLDER ON MAC REMOTE PATH HOW TO.We use a recent feature in FileMaker to have a dynamic file path, and calculate the path to the prefs folder on startup. ![]() We do this by keeping the ClipManager file in the preferences folder, instead of alongside the three main BaseElements files. Where are the clips stored?Īnything you put in the ClipManager is kept even if you upgrade to a new version of BaseElements. Just remember to set the Type field on the top right if you want to copy them in FileMaker format. ![]() ![]() You can create your own Clips and store in them whatever you want. Especially useful for things like script steps or Custom Functions. If all the items are of the same type, you can then copy multiple items and paste them at once back into FileMaker. You can select multiple items by shift clicking in the portal on the left. The Copy icon will copy the currently selected to the clipboard using the FileMaker internal type, so they can be copied back into a FileMaker solution. The Delete icon will delete the current record. The Find ( magnifying glass ) icon in the toolbar brings up the FileMaker Find and Replace dialog, so you can replace some text in the local field, or even across all the records. I've pasted an object, some Scripts and some Custom Functions, and currently there is an Object selected, which also shows the PDF representation of the object at the time it was copied.įrom here you can do all the usual things you can do with a FileMaker text field. What does Clip Manager look like?īelow is an example of what you can put into Clip Manager in BaseElements 17. If you're working in another file, BaseElements could be purely a Clip Manager storage location for you. You don't even need to have a DDR from that solution in BE. If the cursor is not in a field, it will create a new record with your copied object as XML. There's nothing to it really, open Clip Manager by clicking it's icon, and then just hit Paste ( CMD-v / Ctrl-v ). How do I get to Clip Manager?Īny time you want to open the Clip Manager, just click the icon in the toolbar. The best thing about the Clip Manager is that your clips are kept in a separate FileMaker file in your Preferences folder, so you can upgrade to new versions of BE or switch copies, or move from local to server and the clips you've previously used are retained. BaseElements version 17 introduces a new Clip Manager function to allow you to store copied FileMaker data inside BaseElements for future use.įor example, if you're working in a solution and need a script or a set of script steps that you're going to repeat a few times, you can paste them into BE and then copy them back out at any time. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |