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 Forms
- 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
- Webhooks
- Windows
- XML
Our Library of Videos
How often do you really take advantage of Custom Menus? Personally, having worked with FileMaker for quite a while, I tend to ignore them and figure I'll just "teach the user FileMaker". When it comes to my interface, I'll just cram a ton of buttons on the layout and forget the menu. Wow, that's not a good idea! Why not just use Custom Menus?
The biggest hurdle I've encountered with using them is their approachability. The editor is poorly implemented, non visual and modal. This means you have to jump in and out of the Manage Custom Menus dialog and create a script to toggle between menu sets just so you can test your own menus. Testing is the biggest pain. So let's make that eaiser.
The solution is to create an easy system for creating and managing your own Custom Menus. This video will showcase a very simple, yet powerful, approach to using Custom Menus in FileMaker Pro. If you have any other suggestions then please leave a comment on this article.
It happened just a few months ago. It's one of those things you wish you'd done a while ago. It saves so much time, and makes things much easier. What was it?
I broke some bad habits when working within ScriptMaker (oops, it's not called that anymore - but it's such a good name). I started using Copy/Paste for script editing instead of using the Duplicate button. Yeah, maybe this should have been a no brainer, but there are other tips that come along with using the useful copy/paste. Doing a lot of editing, of your scripts, using the keyboard can be a big time-saver. The trick is to force yourself to do it that way. Don't click the 'New' or 'Duplicate' buttons within ScriptMaker. If you start to - then stop!
I also started using more and more visual clues about how my graph relates to the user interface and data structure. Granted, these are things FileMaker, Inc. should integrate into the graph (I personally suggested them to the FileMaker UI team back when the Graph first showed up), but hey, you gotta do what you gotta do in order to make sense of your own organizational mess.
Hopefully, this video with provide some time-saving tips about working in FileMaker Pro and help you develop your solutions that much faster.
Ah, calculating price breaks. "If only they knew how easy it really is!", is what I find myself saying - not because it's a super complex setup, and I'm some cool FileMaker developer who looks down on those who don't know. Rather, because it really is quite easy, and I'd like you to know all the inside secrets.
In this video, I walk through everything you need to know to take advantage of managing multiple price breaks. This is typically based on volume, but doesn't stop there. If you want to offer time-based price breaks, you could do this too!
The information in this video will send you well on your way to solving this complex problem in the easiest fashion possible!
Go To Layout [Invoices], New Record/Request, Go To Layout [original]
True, those are the minimum steps necessary to script the creation of related records - for the situations when a script is used for creation, instead of relying on the user creating the record.
However, the ultimate goal, of any software-based environment, is to code something once, and have it work for multiple situations. This is what this video is all about. It's about the process of scripting the creation of new records - and doing it efficiently.
It showcases this by starting with the very basic methods, then moves on to the most powerful and flexible methods. If you thought you knew everything there is to creating records, then you may want to watch this one. There's likely some tips in this video which you may have missed!
Aside from the word "tagging" taking on new meaning in this Web 2.0 world, the method of simply marking a record for later retrieval is what this video is all about.
The simplest method of marking a record, starts with a simple FileMaker check box. This method, however, becomes quite unusable when you throw more users into the mix. Each user of the database will inevitably want to flag a different set of records - and beyond that, save multiple groups of flagged records.
The solution to this is easily handled with a relationship from an unstored calculated field, using Get (AccountName), to the user's dedicated record within a Users table. The method of storing a set of records as flagged, is then just a matter of a return delimited list of keys within a text field.
Using some creative interface metaphors, you can quickly add a very useful feature to any FileMaker database!
Beyond any organizational tactics used to keep your own FileMaker solutions understandable, there are usually still certain things you can do which slim things down, and make the solution more condensed - essentially more accessible.
One of these things is optimized graphic storage and display. You know, storing and showing interface graphics, icons and such.
I've personally seen a larger number of FileMaker solutions, and it comes from experience that adding an additional global container, for yet one more graphic or icon, seems like such a trivial thing. However, each decision may have longer lasting impacts, which don't become apparent until later down the road.
When you choose to use a certain system of graphic display up front, you end up with a more manageable solution.
This video covers a technique I use frequently when creating a new solution. It takes advantage of older FileMaker technology, and is very forgiving - at least I think so. If you have comments, suggestions or feedback then please leave comments below!
While working on the latest and greatest Theme Library file, it dawned on me that I had a good number of techniques I was using. Many, of which, I may not have shared as of yet.
So, I gathered my thoughts and decided to highlight a couple of the most useful suggestions for anyone developing in FileMaker. Here, in the attached video, you'll find some useful developer tips for working within FileMaker. I hope they help you out.
If you have your own helpful developer tips then please leave them in the comments area below.
Many database developers ( and a lot of us in general ) have this quirk about ourselves - we want our stuff to be "clean". Not in the sense of being dirty, but rather avoiding duplicates. If there's only one Matt Petrowsky as a customer, there should only be one record
So, how do you solve this problem? Well, it all depends on your objectives related to duplicate data. To start with, the key is knowing about all the possible options and how they affect your decisions.
Using the poor example of a unique first and last name ( there is another Matt Petrowsky on this planet ), I talk about the various native and scripted solutions to solving the problem of duplicates. While there's no "one-fix" solution, you can get pretty close to eliminating the vast majority of accidental duplications.
Watch this video to gain a better understanding of what your options are within FileMaker and, by all means, make your own suggestions in the comments below. Like the suggestion of using global fields and pseudo-records prior to data submission ( I didn't even cover this one ) [grin] - but I did cover a lot of other stuff!
When calculation, local and global variables came onto the FileMaker scene, it was one of those "game changers". Especially, for how you go about creating a FileMaker solution. You no longer needed to create all kinds of global fields for the purpose of storing information dealing with how the solution operates.
Whether you've been a longtime FileMaker developer or you're just now joining the community, the information in this video will save you a lot of internal solution management headache. You should be storing operational information within global variables. The trick is coming up with a good method.
Using an example of storing the state of all front most clicked tabs, I walk through how I manage my use of global variables in most of my solutions.
Most every database system needs some type of note taking solution. If you can't take notes somewhere in the system, it limits the amount of information you can collect about issues, customers, transactions, communications and pretty much everything dealing with human interaction.
I remember the days when each table in my database would end up with a new field named 'Notes'. Well, I simply don't do that anymore. There's really no need, and I'll tell you why.
Using a relational structure, you can easily store all notes - for anything - within one table. All you need to do is classify the notes and identify what they belong to. There are a number of ways to accomplish this, and providing the interface to make it happen is now easier than ever. Watch this video for a comprehensive understanding of how to fully leverage note taking within any FileMaker solution!