FileMaker 15 users are no longer blocked from interacting with a layout due to a portal that is taking a long time to load. The new portal in-line progress bar feature (a.k.a. threaded portals) offloads the task of loading “expensive” portals onto separate worker threads, so that the main thread can finish more quickly and return control back to the user.
FileMaker 15: Portal In-Line Progress Bar Learn More ❯
The new FileMaker Server 15 “Top Call Stats” feature helps us identify potential bottlenecks by showing the most expensive user activity, broken down by user and by the type of action that is being taken.
FileMaker 15: FileMaker Server Top Call Stats Logging Learn More ❯
Mislav Kos explores techniques for recreating FileMaker found sets so they can be used across different sessions.
Recreating a FileMaker Found Set Demo Learn More ❯
There are certain situations in FileMaker development where the current FileMaker found set needs to be recreated. A good example of this is when the Perform Script On Server (PSoS) step is used. Since it runs on the server, the current context (including the found set) is lost and has to be reconstructed. I used
Recreating a FileMaker Found Set Learn More ❯
I wrote a blog post last month showing a way to quickly find where unstored calcs and summary fields are being used in a solution. This post is a sort of follow up, in that here we once again look at a way of quickly finding something out about a solution that would otherwise require
What Layouts Is This Field On? Learn More ❯
Certain types of fields, like unstored calculation and summary fields, can really slow down a solution, especially if they are used on layouts that are primarily accessed in list or table view. It’s not uncommon to come across list layouts in inherited solutions – files which you are maintaining but were originally developed by someone
Quickly Find Unstored Calcs and Summary Fields Learn More ❯
The team at Soliant has created a cheat sheet (in PDF form) and a demo “playground” file that you can use to see when a trigger fires and whether the action or object that initiated it completes before or after your script runs.
FileMaker 14 Script Triggers Cheat Sheet & Demo Learn More ❯
Learn how to use the Test Data Generator tool to create realistic sample data for your FileMaker solutions from certified developers.
Generating Random Test Data in FileMaker Learn More ❯
The team at Soliant has created a handy cheat sheet and a demo file that you can use to learn when a FileMaker trigger fires and when the associated action or object is affected.
FileMaker 14 Script Triggers Learn More ❯
Manual Entry of Test Data Discourages Testing When testing the functionality of a solution, software developers frequently have to create test records, which requires them to enter in test data. If the fields requiring a value include a name field, I’m good to go for about 5-6 records, until I exhaust the ‘first name’ supply
Test Data Generator Learn More ❯