Jump to content

FileMaker Magazine

Moderators
  • Content Count

    669
  • Joined

  • Last visited

  • Days Won

    4

FileMaker Magazine last won the day on August 4 2016

FileMaker Magazine had the most liked content!

Community Reputation

11 Good

About FileMaker Magazine

  • Rank
    member

Profile Information

  • Gender
    Male
  • Location
    Murrieta, CA

Contact Methods

  • Website URL
    http://www.filemakermagazine.com

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. When you first start writing scripts within FileMaker, you're typically so focused on the feature or solution you're working on that you integrate it directly into the area where you're working. It takes a bit of time and skill, however, to quickly recognize when you need to make a particular script more generalized in nature and treat it like a routine which simply needs to take input and provide some output. Once you get to this point in your development path, you discover all kinds of opportunities where one script will serve the purpose of many. And, you may find that some of your scripts are in the range of 80 to 90 percent redundant. Possibly varying by only a few lines of code. In this video, I present a very common pattern for many scripts. Treating them like a function and simply following a format for inbound and outbound data from that script. You'll also find a good number of tips regarding documentation, script composition and the big bonus is that we do this with a script which will give you the instant ability to send out text messages via the Twilio API! Click the title or link to this article to view the video. View the full article
  2. When you first start writing scripts within FileMaker, you're typically so focused on the feature or solution you're working on that you integrate it directly into the area where you're working. It takes a bit of time and skill, however, to quickly recognize when you need to make a particular script more generalized in nature and treat it like a routine which simply needs to take input and provide some output. Once you get to this point in your development path, you discover all kinds of opportunities where one script will serve the purpose of many. And, you may find that some of your scripts are in the range of 80 to 90 percent redundant. Possibly varying by only a few lines of code. In this video, I present a very common pattern for many scripts. Treating them like a function and simply following a format for inbound and outbound data from that script. You'll also find a good number of tips regarding documentation, script composition and the big bonus is that we do this with a script which will give you the instant ability to send out text messages via the Twilio API! Click the title or link to this article to view the video. View the full article
  3. The number of features available within FileMaker Go on a mobile device is more than icing on the cake. It's just downright cool we have access to so many features. And, all without having to write super complex code. There is, however, some learning to do when it comes to interacting with URLs and web viewers. It turns out that many web sites, including Google's web based maps site, will change its url as you interact with the web viewer. This causes a problem when you supply an original url to the web viewer and the user expects the same result when clicking on a button which opens the external Google Maps iOS app. The url, which includes needed pieces of information, may vary depending on the interaction with the web viewer. Fortunately, this video covers all the information you need to know when working with urls and parsing them from either web viewers or from any other location. This video will help you not only interact with the Google Maps iOS application, but also with any other external application which is to be opened from within FileMaker Pro. Need to integrate other iOS apps with your FileMaker Go app? Give this video a view! Click the title or link to this article to view the video. View the full article
  4. The number of features available within FileMaker Go on a mobile device is more than icing on the cake. It's just downright cool we have access to so many features. And, all without having to write super complex code. There is, however, some learning to do when it comes to interacting with URLs and web viewers. It turns out that many web sites, including Google's web based maps site, will change its url as you interact with the web viewer. This causes a problem when you supply an original url to the web viewer and the user expects the same result when clicking on a button which opens the external Google Maps iOS app. The url, which includes needed pieces of information, may vary depending on the interaction with the web viewer. Fortunately, this video covers all the information you need to know when working with urls and parsing them from either web viewers or from any other location. This video will help you not only interact with the Google Maps iOS application, but also with any other external application which is to be opened from within FileMaker Pro. Need to integrate other iOS apps with your FileMaker Go app? Give this video a view! Click the title or link to this article to view the video. View the full article
  5. When mobile devices first became prevalent over a decade ago, it was a pretty easy process to design for both mobile and desktop. You just made one layout for each respective device. There weren't as many variations as there is now. In fact, these days, things are much more complex. If you decide to design for smartphone, tablet and desktop you could easily end up having to create three layouts for each possible view. This isn't something I'm personally fond of. I'd much rather limit myself to a maximum of two layouts for each possible view. One for the smaller form factor and the other as a hybrid approach for both tablet and desktop. Fortunately, this is totally possible within FileMaker. It's a simple matter of finding the most ideal width and height which will account for the widest range of devices your solution will run on. Figuring this out, however, does take a little bit of work. By walking you through my own process, and the tool I use for creating a hybrid design, we'll get you familiar with hybrid layout design. A design which would work on a Microsoft Surface Go, iPads and both Mac and Windows desktops. You'll establish a strong understanding of how to approach your hybrid layout design by watching this video. I also provide a few tips about working in Layout Mode with regards to making sure you create a consistent look across all of your layouts. Click the title or link to this article to view the video. View the full article
  6. When mobile devices first became prevalent over a decade ago, it was a pretty easy process to design for both mobile and desktop. You just made one layout for each respective device. There weren't as many variations as there is now. In fact, these days, things are much more complex. If you decide to design for smartphone, tablet and desktop you could easily end up having to create three layouts for each possible view. This isn't something I'm personally fond of. I'd much rather limit myself to a maximum of two layouts for each possible view. One for the smaller form factor and the other as a hybrid approach for both tablet and desktop. Fortunately, this is totally possible within FileMaker. It's a simple matter of finding the most ideal width and height which will account for the widest range of devices your solution will run on. Figuring this out, however, does take a little bit of work. By walking you through my own process, and the tool I use for creating a hybrid design, we'll get you familiar with hybrid layout design. A design which would work on a Microsoft Surface Go, iPads and both Mac and Windows desktops. You'll establish a strong understanding of how to approach your hybrid layout design by watching this video. I also provide a few tips about working in Layout Mode with regards to making sure you create a consistent look across all of your layouts. Click the title or link to this article to view the video. View the full article
  7. 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. Click the title or link to this article to view the video. View the full article
  8. 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. Click the title or link to this article to view the video. View the full article
  9. 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. Click the title or link to this article to view the video. View the full article
  10. 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. Click the title or link to this article to view the video. View the full article
  11. 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! Click the title or link to this article to view the video. View the full article
  12. 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! Click the title or link to this article to view the video. View the full article
  13. 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! Click the title or link to this article to view the video. View the full article
  14. 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! Click the title or link to this article to view the video. View the full article
  15. 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. Click the title or link to this article to view the video. View the full article
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.