Article Tags
Click or tap one of the article tags to filter down to a smaller selection.
- Accounts
- Add-ons
- 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
- 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
Videos about "scripting"
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!
Every craftsman should know how to use his or her set of tools effectively. When you know all the various uses and features of a given tool you then become more efficient at your trade.
In FileMaker Pro Advanced, now available to pretty much everyone in version 17, there's one tool which helps you both understand what's happening and figure out what's not happening. The Script Debugger is an absolutely essential tool.
Creating a well functioning script is a lot like Michelangelo creating David. It didn't just appear because he held the tools in his hands. It was because of the constant refinement with the tools until the beauty within was finally present. Writing a script is no different. You won't get it right the first time and you with almost always be able to refine and make it better.
So, it goes without saying that knowing how to use the Script Debugger is one of the number one things you should know how to do when coding in FileMaker Pro.
The ingenuity of developers has always extended beyond the limitations presented within any given environment - both physical and virtual. If you can't cross a river with your cart and horse, then you learn how to build a bridge and make it last.
Such is the case with FileMaker's script parameters. There's always been only one way to pass anything into a script - as one big blob of text. There's nothing which controls what type of data is embedded within the block of text and it's up to the developer to create a method for passing discrete pieces of data. From the most basic method of simply passing a return delimited list of data we can always take the individual pieces one by one from the list.
Things, however, can get a bit more complex with larger amounts of data. When you need to pass return delimited data as a single parameter out of many you have to be a bit more creative. This is where FileMaker's addition of its JSON functions within FileMaker 16 have helped moved the feature set forward. While there is no native methods for passing multiple parameters, we do have a standard structure for name/value pairs now when working with FileMaker.
When it comes time to “professionalize” your FileMaker solution, this typically includes integrating a splash screen. Even if your solution is only used internally, that extra bit of branding solidifies that mental spot of recall when a user needs to communicate which database they’re using.
So what better way to say “You are here” than presenting a nice, attractive splash screen? In this video, I walk through the step-by-step process of adding a cool-looking splash screen to our ongoing project of the Custom Function database.
In the process of doing so, I explain a variety of other reasons as to why I choose the method showcased in the video. It’s more than just the pretty picture which shows on startup. It deals with startup speed and other helpful features such as increased security potential. If you’re going to put your best foot forward, then follow the method shown in this video!
This video will teach you all about using the new FileMaker 16 Card Window and show you how to take advantage of the fact that you can have a totally different position for the card window outside of the parent which where it belongs.
With a bit of creative FileMaker scripting you can create some really nice features for your FileMaker database.
While it would be wonderful if FileMaker Pro had built-in functionality for all of the features we can possibly think up, it’s not too practical. Besides, what would be left for us to develop?
So, what about saving user state? Do you think you would enjoy leaving your desk for a few moments and coming back to a completely rearranged environment? I doubt it, and that’s almost exactly what FileMaker does when working within a hosted file.
The most common approach to solving this problem is to simply provide a “directory like” structure. Like walking into a mall and heading to the directory map in order to find out where you can possibly go. Call it what you like, a dashboard, main navigation, whatever. You’re simply reseting the user each time they leave and come back into the software.
Well, if you’d like to take another approach, then all you need to do is save the user’s last know state. What you save and how you return the user to their last known state is in your full control. It’s not that hard to do and this video will give you all the details you need to know.
Developing in FileMaker Pro is rewarding because of the speed with which you can accomplish things. The speed, however, isn’t worth much when you only know one possible way to do things. It’s the master carpenter, who knows all the tools and methods for getting things done, who is the most efficient.
When it comes to replicating a found set within FileMaker, there are many paths to take. Your standard Perform Find script step will simply pull up a found set of records based on predefined or dynamic criteria.
There are, however, many cases where a found set is composed of data which has been filtered. This could be a list view of data where individual records have been omitted or a set of related records derived from a filtered portal.
Regardless of how the found set is derived, if it’s a random set of records which need to be recalled, then saving this found set becomes valuable. It turns out, there’s a method for saving this found set and it’s the most optimized method possible. This is because it’s the same method which FileMaker itself uses.
This video is about recreating a found set and being able to use it in various ways. It could be used for a PSOS (server side) script or simply to provide the user with a feature of being able to save and recall a found set of records at any time. No matter what your needs, knowing how to use this feature is a valuable piece of FileMaker know-how!
In FileMaker, if we only had list and form views for viewing data, then we’d probably be just fine. But, who wants to just get by with a minimal set of methods for viewing data? The ever valuable portal provides a wonderful view into whatever data you wish to show.
It can be related data, menu options, a list of users or pretty much anything. Especially, when using a portal as a Virtual List of something being held within a $$GLOBAL.VARIABLE.
The key thing to understand about portals is that FileMaker just provides you with the bare minimum. The level of expected user interaction just might not be there for your solution. For example, take a basic portal, select a given row and hit the delete key. What’s the result? The default FileMaker dialog. What if you’d like to run your own script when the delete key is hit?
How about that wonderful trash can icon, or any other icon placed in the first row in Layout mode. Well, you see them on EVERY portal row. Yuck! Take off that obvious UI distraction. Instead, make it show only when a given portal row is selected.
This video will provide you with all kinds of inside knowledge into how you can make your portal interactions just that much better!
Learning how to efficiently create scripts within FileMaker is a never ending process. It's a balance of leveraging what you know and mixing in newly added features along with new ways of doing things. Optimization and cleanup will always be part of the ever growing software solution.
In this video, I present the topic of using utility scripts in order to save precious development time. You know, those reusable scripts which prevent you from writing unique and dedicated scripts for every possible scenario in which the user will interact with your solution.
They're the scripts which end up saving you a ton of time and get used over and over again. They can be used stand-alone or they can be called by other scripts. But, no matter how they are used, it's certain they are valuable pieces of reusable code.
If saving time and reducing the number of scripts you write is of any interest, then this video will have the information you need.