In a follow up blog post we shared more PSoS techniques, including how to set up the additional database folder to get imports to work on server. A few years ago we covered how imports on FileMaker Server are definitely worth it, especially for improving speed:ġ00x Faster – Flight Testing FileMaker Perform Script on Server – Part I With file-based script steps in FileMaker 18, you can perform imports natively, and take advantage of Perform Script on Server. If you have seen me present at a past DevCon you’ll note that I like to use intersection diagrams to explain how things fit together: Not only is my favorite number 13, but Perform Script on Server (PSoS) was introduced in FileMaker 13. Let’s start at the beginning! My favorite FileMaker version happens to be 13. Password: import A Brief History of PSoS and Imports Here is a demo file you can use to try out the techniques: Like it or not, we can’t always escape the flood of cheap spreadsheets, but maybe we can build more efficient FileMaker integration with output from tools like Excel. In this blog post, I’ll use the new FileMaker 18 file-based script steps combined with PSoS for a little import magic, and hint at how to improve data-driven workflows. Performing imports like this, natively, means avoiding the traditional performance overhead that would tax both FileMaker Server and FileMaker users over a WAN, and otherwise require waiting for imports to complete, synchronously. You can also take advantage of Perform Script on Server (PSoS), and handling imports asynchronously. I was thrilled to discover in FileMaker 18 that the new file-based script steps give us the ability to perform imports natively on FileMaker Server, with no configuration or changes needed. Combining functions, features, or steps in creative new ways can deliver productive results.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |