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
While younger generations of Internet users are increasingly adopting communication tools like Discord, it's challenging to envision a future devoid of at least one distinctive means of communication - email. Could a world without email imply that government agencies, utility providers, and other entities transmit messages based on your DNA sequence, linked to your registered devices? The possibilities are intriguing.
But for the present moment, email remains a crucial part of our digital landscape. The transition toward a paperless society is still underway and is likely to persist for many decades to come.
So, the key question is, have you seamlessly integrated HTML emails into your FileMaker solutions? If not, rest assured that you'll acquire a comprehensive understanding of both implementation and troubleshooting when it comes to facilitating communication between FileMaker and an SMTP server. This video offers a practical script and in-depth insights into successfully sending multipart mixed emails. Whether your HTML email simply involves basic formatting, like bolding certain text, or incorporates intricate features like a logo-adorned letterhead, sending the email via SMTP is your destination. Let's make that journey a smooth one and ensure you're well-equipped with all the requisite knowledge.
When embarking on your journey with FileMaker, you encounter the wonderfully visual tool known as the Relationship Graph, which grants you the ability to visually comprehend the intricate interconnections within a complex solution. In fact, the relationships used to link table occurrences in FileMaker are fundamentally akin to those in SQL.
FileMaker essentially offers a visual representation of what would otherwise be a textual definition of a SQL statement. The key distinction lies in the fact that SQL operates within the realm of text and only executes when required. Conversely, the Relationship Graph in FileMaker is persistent and is continually assessed by FileMaker. Consequently, comprehending the implications of specific relationships in your solution becomes vital as your solution expands. Relationships that appear ostensibly simple, serving utility purposes within your user interface, might have more profound ramifications than you initially realize. Hence, it is imperative to comprehend and effectively employ all of your available tools.
One of these indispensable tools is FileMaker's full SQL implementation. In this video, I delve into the advanced aspects of using SQL within FileMaker. If you've constructed your FileMaker solution exclusively using native FileMaker features, you might unknowingly incur a big cost if you haven't invested time in learning FileMaker's SQL capabilities.
One of the primary reasons developers cherish FileMaker is the freedom it offers to unleash their creativity within Form and List views. You have the power to craft virtually any type of software you can envision. However, when it comes to Table View, it might seem like you're merely replicating what most end users overuse - spreadsheets. Table View was likely introduced to ease the transition for spreadsheet users into the world of databases. Nevertheless, a well-structured data model renders a spreadsheet-like view of data as useless.
Despite this, the inclusion of Table View comes with some concealed features that can significantly enhance your development process as you create your ideal software solution. This video will unveil all these hidden treasures for you.
In the world of FileMaker solutions, it's almost inevitable that a solution will experience significant growth during the initial stages, followed by a transition to the everyday pace of normal use. When developing those initial features, one of your key objectives should be to emphasize reuse and repurposing. As is often the case, the less you have to manage, the easier it becomes to maintain and update your solution. There's less to re-learn, and your scripts, layouts, calculations, and other elements are more straightforward to locate and update.
However, if you tend to create numerous one-off duplicates within your code, you may end up with a collection of disparate elements that require attention or become obscured over time as additional features are added, potentially duplicating some earlier functionality. In complex solutions, it's not uncommon to become confused about what was implemented earlier and inadvertently replicate entire feature sets.
In such scenarios, you're left with the burden of either consolidation or selecting one implementation to retain while removing the others. A more effective approach is to proceed by making aspects of your solution universal and the default method for accessing specific functionality. This is where creating universal pickers that apply solution-wide can yield substantial benefits. In this video, we address precisely this situation and guide you on how to approach their implementation.
Despite the FileMaker platform being several decades old, the original design of Layout mode and the ability for developers to harness existing tools to either mimic operating systems like iOS or craft entirely unique user interfaces remain monumental advantages for those who opt for this platform.
One of the most significant additions to the Claris/FileMaker platform was the introduction of Card Windows. I remember creating some of the initial videos showcasing this feature; the capacity to exercise complete control over a rendered window was an immensely valuable advancement in FileMaker development.
Granted, there are areas where this feature could be refined to enhance its functionality even further. However, the current capabilities allow us to effortlessly generate our own windows whenever and, more notably, wherever we desire.
This video, along with the accompanying technique file, introduces a feature I refer to as "Object Card Windows." To put it simply, you specify a target object that will determine the boundaries within which a new card window will appear. The advantage is a straightforward yet incredibly practical script for generating new card windows in specific locations. This utility script is an absolute necessity for any solution, and its inclusion in your toolkit is highly recommended.
Even when discussing seemingly mundane topics like Default Fields, there are always valuable insights to uncover. This video offers an exploration of the default fields I consistently incorporate into every table I create. While you might be familiar with or have utilized some of these fields, there could still be a surprise or two in store.
For those who are relatively new to Claris/FileMaker development, this video holds significance. Learning about core techniques for data loading and effortlessly achieving desired results is crucial. Whether it involves displaying a count of related records or utilizing the internal Record ID for various UI functionalities, understanding how to accomplish a range of tasks within our preferred database software is truly beneficial.
Discovering ways to make software faster and more efficient brings a great amount of joy to developers. The reason behind this is simple: with enough experience, you come to realize that straightforward and simple code is much easier to maintain than complex and hard-to-maintain code. Self-contained code with fewer dependencies is both easier to understand and refactor.
In this video, I share one of my all-time favorite functions in Claris/FileMaker development, the Custom Function named CustomList. Although this function has served me well, it has now been surpassed in terms of speed and optimization by a newer method - the ValuesWalk function. This video demonstrates how you can utilize FileMaker's calculation engine to calculate the results you need and then seamlessly display those results within your user interface using the ValuesWalk function.
Moreover, the ValuesWalk custom function extends far beyond the simple use case presented. It can be employed to process any type of data, from generating ad-hoc delimited text files to processing simple lists. The ValuesWalk function is absolutely a valuable tool that every developer should be familiar with. With built-in performance testing, you can determine the optimal chunk size for processing the data you are working with. This knowledge is essential for advanced Claris/FileMaker development and is a must-know piece of information for developers aiming to optimize their solutions.
If you don't pay close attention to the fields you add to your record load in Claris/FileMaker, you might end up facing a transfer penalty, especially when dealing with container data. In many cases, your end users may not require the data from heavy multi-megabyte container fields. Nevertheless, every time the record data is loaded, that large container data gets included as part of the transfer.
Unlike SQL or a document database, where you can request only the necessary data, FileMaker provides the entire record, including all field data. Therefore, it is essential to create a structure which optimizes the utilization of containers. While I have previously covered this topic, this video offers a walk-through experience as I demonstrate how to implement support for a singular Files table, which can be used in multiple locations across a solution. I also discuss various options, such as one-to-one, one-to-many, and many-to-many relationships, when it comes to loading associated file data.
If you have ever wondered how to further enhance the speed and performance of your FileMaker solution, this video provides valuable insights into how you should likely structure your use of container fields. Understanding the concepts covered in this video will likely improve the performance of your solutions.
One of the major challenges that any solution or developer encounters is effectively managing the growth of their solution. As the solution expands, the issue of "dilapidated code" arises. This refers to code that either gets replaced or continues to be used without being updated to leverage the latest enhancements in FileMaker. Consequently, a significant portion of the code may become obsolete over time.
One of the most effective solutions to tackle this problem is the use of utility scripts or code that addresses a wide range of use cases. This video showcases the implementation of a commonly used pattern, namely, obtaining user confirmation to ensure that their intended actions align with the expected outcome. By employing a utility script called "Confirmation Prompt", we can prompt users not only for record deletions but also for various other situations.
This powerful utility script allows us to manage a variety of user interactions, such as setting a temporary $$UI.VARIABLE or modifying the value of a hidden field. Furthermore, the video presents one of the best approaches to learning and utilizing JSON, in case you haven't embarked on that journey yet. JSON proves to be an excellent method for managing serialized data within Claris/FileMaker. If you aim to streamline your solution and reduce the total number of scripts, incorporating the utility script from the provided technique file will undoubtedly save you a significant amount of time.
Being able to develop and test your solutions within a FileMaker Server environment is the ideal scenario. You can test Perform Script On Server, external binaries, and plug-ins that perform a variety of tasks. Essentially, you can perform all the necessary tasks in a real solution.
When you develop your FileMaker solution locally with a single copy of Claris/FileMaker Pro, you not only face limitations in what you can test but also risk the possibility of a crash. While running FileMaker Server on your local machine is a satisfactory solution, the next step is being able to run multiple versions of FileMaker Server without the need for multiple uninstall/install scenarios.
This video showcases my return to using Docker Desktop on an M1 Mac Studio ARM-based machine. Previously, I had to stop using Docker and resort to a full virtual machine when I switched to using Apple Silicon. However, with the release of an ARM-based version of FileMaker Server and most plug-ins being available for the ARM architecture, we are now able to use Docker Desktop again. The trick lies in learning how to use containers. This video provides a great opportunity to learn a new skill. If you want to run multiple variations of FileMaker Server on your M1 or M2 Mac, this video has what you need.