Relationships are the basis of relational database design. When set up properly, table relationships will ensure your database runs like a well oiled machine. However, sometimes we run into systems where relationship keys are open to the user, exposing data to the risk of human error if a relationship is changed improperly. It’s sometimes desirable to refactor these relationships to use a proper artificial key relationships to connect tables, a laborious task depending on the size of your database. This post discusses a convenient trick to populate Primary Keys, a reminder about mismatched data types, and a modular script to help populate foreign keys when refactoring a key relationship.
We had an interesting request on a recent project where the client wanted to navigate two portals on a layout using the keyboard. The portals needed to be setup in a way that makes them appear to be one large portal with a static header row in the middle. The client also wanted the interface design to allow for very fast data entry. We concluded that using the navigational keys to navigate the portal would be the best choice, since it performed similar to navigating a spreadsheet.
FileMaker 17’s new ‘Master Detail’ interface object allows the user to see and interact with a portal of the current found set and the detail of a single record at the same time. It can be very helpful in allowing the user to work with their data in a detail view, while staying in the context of a list of records. It’s easy to implement and even easier for users to navigate. Though the portal is handy when it’s being used, it’s often taking up valuable real estate when not in use. So, we’ve developed a helpful enhancement on the basic Master Detail implementation that utilizes the slide-control panel to show and hide the Master Detail portal when not in use, while still allowing quick access when it’s needed.
The current incarnation of our Blog was first published 6 years ago. During that time we’ve posted a lot of blog articles, included a number that include sample files that demonstrate a variety of techniques and ideas for features in FileMaker.
Are you looking for a reusable tool to be integrated with your FileMaker solution that provides an easy to use date range chooser popup window? Look no further! Portage Bay has created the Modular Date Range Chooser which can easily be added to your solution, either by copying and pasting the components into your existing solution, or linking the file as an external widget file. I am currently in the process of uploading this to modularfilemaker.org so it will be available to any FileMaker developer.
We are pleased to announce the release of our Map Widget v.1.0 product. This is a new tool built natively with FileMaker which can be easily integrated into your existing FileMaker solution. The Map Widget provides you with the ability to display your FileMaker data as locations on a Google Map, using the Google Maps clustering functionality. You can easily interact with the Google Map, click on each pin, display details about the location, and even click a link to return you to that specific record in your FileMaker solution.
We have been getting a lot of requests for a demo file to accompany one of our blog posts about google maps integration. While we aren’t quite ready to release an unlocked example file for the techniques we used, we have put together a sample file in order to allow users to try out the maps integration.
One of the more exciting new features of FileMaker 16 is the adoption of the cURL library within the “Insert from URL” script step. Using cURL as a command-line tool is relatively straightforward, but the syntax can often be a hurdle.
Pivot tables have always been difficult in FileMaker, that is until now. We have come up with a solution that makes them easy to create and share.
With the release of FileMaker 16, we have seen a great number of new and improved script steps. FileMaker 16 extended the capability of the Save as PDF script step, now allowing it to work partially with WebDirect, FileMaker Go, and Server, however there are a few things of note.
One of the missing features in FileMaker is the ability to add portal headers that can both sort portals and easily display the ascending or descending sorted order.
While incorporating address information to render markers on Google maps is fairly common these days, we have made some additional strides in working with the common Google API and are able to leverage some useful but obscure API services.
While it’s easy for FileMaker to keep a repository of indexed keywords, FileMaker cannot easily display those keywords in a format that resembles the UI found on most social networks. We can fix that.
Making FileMaker understand complex search instructions.
We wanted users to be able to click on a link within the web viewer and see the linked page in a window in their web browser outside of FileMaker. There was a 'gotcha'.