![]() 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 |