One of the things our clients often request is for us to set up their custom application so that it is mandatory for users to fill in certain fields. You all know what this looks like, right? You go to a website to sign up for a service and next to the places you have to put your email and password, you see a little red asterisk. And then at the bottom or top, or somewhere on the page, it will be explained that these fields are required. Now you can specify required fields in FileMaker Pro quickly and easily.
The Support Group Blog
Data is powerful! It's generally the backbone of most strategic business decisions to improve products and operations. But the data that businesses collect can be mutually beneficial to consumers as well. Our trackable behaviors and habits make innovation and efficiency possible by allowing computers to process and interpret data in such a way that it can actually help to fulfill a task or goal . This is known as artificial intelligence (AI) and we'll continue to hear a lot about it going into 2018 in terms of research, development and controversy, so we'll save a serious discussion about that and custom applications for another time. For now, we just want to have a little fun with AI.
We rely on indicators to let us know that a process is running. We can hear our engines running or see the timer ticking down on the microwave – all positive indications that something is working. Have you ever been on hold with no hold music or regular automated updates? It can be frustrating because you don't know if you're still in the queue or wasting your time. So it's good, virtually expected, to include a progress bar or an alert within a process in order to maintain engagement.
We’ve been writing FileMaker scripts for over 25 years now (ever since FileMaker Pro 2.0, when the ScriptMaker first appeared) and we’ve developed our own set of best practices in terms of managing them here at The Support Group. Every FileMaker developer has his or her own set of methods, preferences, styles, etc., but we all agree that writing and maintaining scripts properly can save you a lot of time and frustration in the long run. Whether you're an experienced FileMaker developer or new to development, you should find these seven scripting tips useful.
Thank you, FileMaker 16! My wish has been granted; we are now able to Save Records as PDF in FileMaker WebDirect. Goodbye robot processes and hello FileMaker WebDirect!
“Where is that field? How do I select the sliding panel behind the portal?”
In FileMaker land, we've had the ability to stack objects since version 1.0. And ever since then, it's also been possible to lose objects behind one another. You have to know exactly where the object is in the FileMaker Layout Objects window and move things around until you can actually click on it with the mouse in order to select it.
FileMaker, Inc. announced the newest version of their flagship database environment, the FileMaker Pro 13 family. It marks the latest in a progressive line of evolution for the product. As a long-time FileMaker developer I, along with my colleagues at The Support Group, am excited about the new features that will help us build even better solutions. In this post we’ll take a look at a few lower-level enhancements and peek at the possibilities of the UIX refinements.
This is my first week at The Support Group, and I get to kick it off with FileMaker 12!
FileMaker 12 is here and with it comes a new file format. However, this isn’t your father’s file format change (i.e. fp5 to fp7), full of architectural rewrites, modifying scripts, and changes in behavior. If planned for correctly, it is a fairly painless and worthwhile adventure, chalk full of performance increases and development possibilities (awesome layout themes, better and easier charting, more robust container field behavior and many more).
Sometimes, when writing a FileMaker script to do a find, sort, or export, doing it manually first can save you LOTS of time.
I was just tasked with creating a script to export all the fields on a layout. The layout, however, is non-trivial and contains fields from multiple different tables, and the relationship graph I inherited is very complicated and nearly impossible to decipher. It would have taken me HOURS to identify the table occurrence and field name of every field on this layout and then set up the export in a script.