Article Tags
Click or tap one of the article tags to filter down to a smaller selection.
- Accounts
- Add-ons
- AI
- Alerts
- Analysis
- APIs
- Apple Maps
- Auto-Enter
- Barcodes
- Base64
- BaseElements Plugin
- bBox
- Breadcrumbs
- Button Bars
- Caching
- Calculations
- Calendars
- Card Windows
- Charting
- Checkboxes
- Code Editing
- Code testing
- Coding
- Color Picker
- Colors
- Conditional Formatting
- Containers
- Context Management
- Cropping
- Crypto
- CSV
- cURL
- Custom Functions
- Custom Menus
- Data API
- Data Capture
- Data processing
- Data structure
- Data Viewer
- Date Ranges
- Dates
- Debugging
- Deployment
- Developer Tools
- Dialog Boxes
- Docker
- Drag-n-Drop
- Drop-down List
- Dropbox
- Duplicates
- Duplicating records
- Encryption
- Error handling
- Events
- Excel
- ExecuteSQL
- Exporting
- External Authentication
- External Files
- Field Formatting
- Field Storage
- Fields
- File IO
- File Management
- File Sharing
- FileMaker Go
- FileMaker Server
- FileMaker Settings
- Filtering
- Find & Replace
- Find Mode
- Found Sets
- Functions
- Fundamentals
- Global Fields
- Global Variables
- Google Maps
- Google Services
- Graphics
- Grid
- Grouping
- Hierarchies
- Highlighting
- Icons
- Images
- Importing
- Indicators
- Inspector palette
- iOS
- Java/Groovy
- JavaScript
- Join Tables
- JSON
- Key fields
- Layout Design
- Layout Mode
- Layout Parts
- List function
- Logging
- Looping
- Mapping
- Marking Records
- Media Storage
- Menus
- Merge fields
- Messaging
- Microsoft Surface
- Mobile design
- MonkeyBread plug-in
- Multi-key fields
- Multi-option fields
- Naming Conventions
- Navigation
- New Release
- Node-RED
- Notifications
- Oauth
- Object management
- OCR
- OnGestureTap
- OnLayoutKeystroke
- OnObjectKeystroke
- Parsing HTML
- Perform Script on Server
- Performance
- Permissions
- Photo manipulation
- Pickers
- Pivot tables
- Pop-ups
- Popovers
- Portals
- Preferences
- Printing
- Privilege sets
- Product review
- Productivity
- Progress Bars
- PSOS
- Python
- Quick Find
- Record Locking
- Regex
- Relationship Graph
- Reporting
- REST
- Sankey
- Schema
- Script Parameters
- Script Triggers
- Scripting
- ScriptMaster
- SDK
- Searching
- Security
- Separation Model
- Set Variable
- Settings
- Shortcuts
- Sliders
- Snapshot Links
- Sorting
- Spelling
- Spreadsheets
- Startup
- Summary Fields
- SVG
- Syntax
- Syntax Highlighting
- Tab Controls
- Table View
- Tagging
- Terminology
- Text Parsing
- Themes
- Time fields
- Time Savings
- Tips
- Tools
- Transactions
- Tricks
- Twilio
- UI
- Updating
- User Interface
- Validations
- Value Lists
- vCalendar
- Virtual list
- Web Forms
- Web Scraping
- Web Services
- Web Viewers
- Windows
- XML
Our Library of Videos
When you're the one creating the database, you're the one who says which data makes it in and which data doesn't. This all happens through the various methods of data validation.
Data is either considered valid or not - and this happens according to your data validation rules. If the data is valid, then everything proceeds as normal. If, however, the data isn't exactly what's required, then you get to choose what happens.
In most cases, you can let the user keep taking a whack at it until they get the right combination, or you can shuttle the user off to another part of your UI.
In this tutorial video, we take a look at the three primary tools FileMaker provides for data validation. You can use any single option or combine them to mix and match for the perfect data validation solution. We've even got a nice little text formatting mask feature which provides a great looking phone number field.
Prior to FileMaker 13 we never even had the option of performing scripted tasks where the data actually exists. The processing of a script, client side, always had, and still does, make a full round trip for all kinds of these processing activities. Many times, FileMaker does it's best to optimize whatever is being done, but it's still not as fast as executing certain things directly on the server.
With the addition of Perform Script on Server we gained a REALLY BIG performance boost by being able to perform most any script on the server.
While there are still various limitations, such as the number of simultaneous server side scripts, it's absolutely something that any serious FileMaker developer needs to know how to use.
One of the biggest issues with running server side scripts with Perform Script on Server is the fact that you need to know what's happening when the script is running, how to troubleshoot and most importantly, how to replicate the current user context. That is, the proper layout and the exact same found set to be used for processing the data. This video specifically covers how to restore the user context for processing a found set of data. If you're interested in making this process happen as quickly as possible, then using Perform Script on Server is what you should learn to use.
One of the most wonderful aspects of FileMaker, or any development project, is implementing a portion of the software which can be used system wide. Meaning you don't have to recreate functionality over and over again in order to benefit from what you implement initially. Especially when it can be used in all locations universally.
In this video, I show you how to implement a Universal Tagging System in which you can apply tags to any other element you're managing within your database system. Are you needing to divide up the people you are tracking into multiple different groups? No problem. Do you anticipate that those groups will change and vary over time? No problem. Do you have more than one thing which could benefit from being tagged for the purpose of organization? No problem.
This system implements tags in such a way that they can be used to pretty much tag anything you can think of within your database solution. The data is managed via a join table and the logic for the UI will handle tagging any system element universally as well. Watching this video and using the provided file should make your system that much more flexible in terms of data organization and you can expand upon it as much as desired. If you enjoy flexible, yet powerful features, within your database solution then make sure to watch this video and learn from the provided file!
While many FileMaker solutions will manage multiple parameter passing in very simple and straight-forward ways, there are some solutions which you know will grow over time. Because of this expected growth, you may want to have an additional level of comfort knowing you've implemented a very strict system for managing data transfer between scripts.
You also may be interested in working with external APIs and connecting to systems and data which is provided via the currently popular format of JSON (JavaScript Object Notation).
Since the release of FileMaker 16, we've had access to the fundamental JSON* functions. With their initial release, there were a number of developers who immediately jumped on the bandwagon. Since FileMaker 16 was released, we've had a good bit of time to codify some methods and helpful custom functions for working with JSON formatted data.
This video is all about providing comprehensive initial coverage about how JSON can be used for passing multiple parameters within FileMaker. If you never quite taken the plunge into using JSON for parameter passing then this video and the associated file may very well provide you with the incentive to take a more serious look. At the very least, you'll know what's going on when other developers mention they're using JSON parameters!
Having worked with FileMaker for well over 20+ years, and experiencing a wide variety of data models, it's always possible to get into a situation where you need to re-evaluate the data decisions you've made with regards to your structure.
The data model you may have initially thought would handle all situations may need to be modified. Knowing about the multiple options you may have available for structuring your data makes a big difference when you start to consider simply "adding that new field" to your database.
It may be that the workflow or process required would cause duplication of data and therefore increase the complexity of your solution unnecessarily. In this video, I cover the topic of a Single Source of Truth for storing field data. While the topic isn't limited specifically to fields, and should be considered for tables and data overall, it's good to know how to deal with specific cases where storing data becomes a big concern when dealing with additions, updates and deletions. Be prepared to learn more about strategic ways to store data in this video about Single Source of Truth.
It's a curious question and the answer may be good or bad depending on your perspective. "Why doesn't FileMaker have a time picker?". It has a calendar widget for working with date fields, why not time values?
The solution to the problem, as is often the case, can be managed by simply creating your own picker. In fact, if you don't like FileMaker's desktop based date picker you can create any variation you desire based on being able to create any style of layout you can imagine. While the same applies to a time picker, it may not be obvious how to implement if you've not worked with FileMaker for some extended amount of time.
In this video, I showcase a straight-forward time picker which works with both timestamp fields and time fields. It also includes some valuable utility scripts and concepts which can certainly be used in other areas of your FileMaker solutions. If you've ever come across the need for a time specific picker then adding this to your solution should save you a ton of time!
Unless you've got a billion dollars to send out tens of thousands of cars with specially fitted technology mounted on their roofs; and, you can send them all across the planet, then you'll likely need to rely on mapping data from a third party.
So, here we go with learning how we can leverage Google Maps APIs within FileMaker. This video will cover the essential knowledge you need in order to make the requests about geolocations whether they be latitude longitude coordinates or an address.
As you've likely used Google Maps within the web browser, it's great to know you can access that same data directly within FileMaker; even the traffic data. It's just a simple matter of creating the right url. Making a request for what you want, and then parsing the data right back into your FileMaker table. Let's learn about the process and wire up the technology!
If it's not obvious by the types of videos I produce, one of my most favorite areas of software development and design is the user interface. It's where the real test of your software happens. A user either "gets it" or not. If they don't, then you're back to the drawing board.
Of course, there's always the learning curve which is present for anyone, but if you can create something that has less of a learning curve, then you feel like a winner.
In this video, I cover a wide variety of topics related to FileMaker development. The video introduces a subtle ui widget which I implemented based on the intended usage of the software. This is what reflects the real process of software development within FileMaker. Not just taking the super obvious approach, but the one which might make more sense to the user and is a bit more difficult for the developer to implement.
This requires you to know how to get things done in FileMaker and implement a feature which is user friendly and facilitates a fluid workflow process.
These are often asked questions regarding setting up a new FileMaker database system. "How can I limit when the user can enter data into the field?" Or, the alternative, "Once the user enters data, how can I make sure they don't change it unless I want them to?"
Both of these types of questions can be answered using a variety of methods. The core to understanding their answers is that there's really only only two methods for limiting field access. One is controlling the display of the field and the other is truly limiting access to the field data itself.
Using the knowledge in this video you should be able to come up with a method which fits your exact situation. The video walks through the use of the various options which FileMaker provides for limiting access to a field. If you'd like to know which options you should use to control access, then give this video a view.
One of the nicest additions FileMaker made awhile back was within an area you wouldn't quite expect. It was within the Summary functions that FileMaker added a simple new option named ListOf. This happened with FileMaker version 13 and this one type of summary field can be use for so many different things within the user interface that it's quite invaluable for driving all kinds of user feedback.
With a ListOf summary field, you can control the content of a custom portal, grab data necessary for looping over, or simply show the user an overview of the records they have loaded in the current found set.
Understanding how to use, and take advantage of, the ListOf summary field is what this video is about. We'll walk through two different uses and take a look at a nice user feature which allows the user to determine which data they would like to interact with. If you've never used a ListOf summary field, then you certainly need to be aware of what's covered within this video!