Create Dynamic JSON for Related Records Using This Custom Function
Check out this custom function for dynamically creating JSON arrays for related records in FileMaker, built by Technical Project Lead, Makah Encarnacao.
Learn more about top FileMaker custom functions from a team of platform consultants and experts. In our resources below, we share our favorites and how to leverage them in your business application.
FileMaker custom functions are constantly evolving, so if you have any questions or would like to leverage them in your FileMaker solution, please contact our team.
Check out this custom function for dynamically creating JSON arrays for related records in FileMaker, built by Technical Project Lead, Makah Encarnacao.
Download the custom function for dynamically creating JSON arrays for related records in FileMaker, built by Makah Encarnacao, Technical Project Lead.
FileMaker 16 introduced a series of functions to work with JSON data, but creating a custom function can take your solution even further.
Learn how how to use the custom function for creating variables from JSON data in FileMaker with this free demo.
Need to combine multiple PDF files into a single PDF document? This post examines how to combine PDFs and explores techniques involved to run as a server-side script that is multi-user safe.
The Data Viewer is a feature of FileMaker Advanced that gives you under-the-hood access to your data. Agnes gives you some examples of how to use the Data Viewer when creating custom apps.
How do you show related records in a “portal” within a popover? Agnes demonstrates a quick and easy method using a custom function.
There are certain situations in FileMaker development where the current 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 to …
Mislav Kos explores techniques for recreating FileMaker found sets so they can be used across different sessions.
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 …