![]() It is partially supported in FileMaker Go, FileMaker WebDirect, and FileMaker Server & Cloud. There are quite a few script steps that have listed “partial” in the supported column. So you have to consider each incompatible script step and decide if the script will break if the process is incompatible. If, on the other hand, the step included input fields which are used in the rest of the script, there’s a problem. That’s okay if the script step was meant to show a success message. Show Custom Dialog is not compatible on FileMaker Server, and Server will skip that step. When the FileMaker runs a script, it will skip over any steps incompatible with that component. _IsWin will return 1 if a Windows machine is running the script. There are also custom functions that provide this functionality as well. The functions Get(SystemPlatform) and Get(Device) are good candidates for component-checking. This involves checking for the component that is running the script, and then, at each step in question, skipping over it or performing a different set of steps that do work for that component. In-Script LogicĪnother strategy to use when working with FileMaker script compatibility is to use logic in your scripts that skip over incompatible script steps for any component. I’d build the script, duplicate it, and adjust it for the Data API as necessary. I might start with FileMaker Pro Advanced on macOS. ![]() To start, I’d build a script that works completely on the most common component used in my custom app. My script workspace might have folders for each component: Even if that same process is used in FileMaker on Windows, there is a benefit to having two separate scripts that do the same thing (roughly) that are customized to that component’s script compatibility. If I need a process to run using the FileMaker Data API, I should write a script just for that process and component. This strategy involves writing a script for each component that will be used. Once you know how a component of the platform performs or works, you can more efficiently pick those steps that will work and work around those steps that you need that won’t work (if possible). Since FileMaker 16, it has partial support. The script step “Save Records as PDF”, back in the old days of FileMaker 15 and earlier, was not compatible on server. Script steps that were not compatible in a part of the platform in the past are now compatible. continually updates their platform’s functionality, and thus FileMaker script compatibility changes. FileMaker developers in the game for a long time know this. We know this because that component does not have access to a client’s file system. Likewise, the script step Get Directory does not work in FileMaker WebDirect. We’ll discuss its consequences further down). ![]() (if you do use this step on server, nothing bad will happen. That’s why it’s not compatible with server. There’s no window, so the Move/Resize Window step is useless. It opens an instance the custom app only in memory. Each of these uses the scripting engine inside Server. I don’t think it’s that these developers know all the compatible steps for, say, FileMaker server, but they know what FileMaker Server can and cannot do.įor example, we know two ways to run scripts with FileMaker Server: Perform Script on Server or Schedule Scripts. Many seasoned developers have an encyclopedic knowledge of the entire platform, and that includes knowing which steps are compatible with a part of the platform. Here are some strategies you can use to ensure you’re scripting smarter: efficiently and effectively. And if you think about it, what’s worse: more work or incorrectly-performed scripts? Either I’ll have to create one script per component to do the same thing, or I’ll have to have a lot of logic inside a script to handle all the possible places a script will be run. Scripting compatibility sounds like a lot of work. ![]() We need to review existing scripts to make sure each step will perform correctly in the chosen components. We need to design scripts that are the best for each part of the platform. So the lesson is: when we are writing a script, we should use the FileMaker script compatibility checker to make sure each step will work. You’ll see any incompatible script steps grayed out.Īdditionally, we can use this dropdown to examine the script step list to see which steps are compatible. We can use it to examine a current script to see which steps are not compatible with the selected component. Many of my script steps do not work for the FileMaker Data API component.Īt the top right of the script workspace is a button that opens this dropdown.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |