The latest in-app update to DayBack introduces custom tooltips. These tooltips are completely scriptable. You can customize the content and can style the tooltips (and their content) using your own CSS.

How It Works

Tooltips are triggered by a new calendar action: On Event Hover. This new action can call FileMaker scripts or execute JavaScript. It’s JavaScript you’ll use for the tooltips, and you can call a simple function to show any content you’d like. Here’s the Javascript for the example above:


That’s passing the event’s title into the tooltip function. You can also pass in more fields and use HTML to make it more readable. Here’s another field (resource), separated by a line break:

dbk.tooltip(event.title + ‘<br />’ + event.resource);

The tooltip documentation covers all this and provides a more thorough description of this JavaScript, lots of examples, and notes on styling this with CSS.

Going Further

There are a lot of possibilities here when you combine the On Event Hover actions running JavaScript inline with tooltips that will show any HTML you put in there. By adding some logic to your JavaScript you can have different tooltips for different kind of events, or show different tooltips on different views. Tooltips have access to any of the JS libraries in DayBack, including momentjs for formatting dates.

Writing tooltips like this is probably the easiest way to get started with JavaScript in FileMaker. You can show meaningful, user-facing results with just a single line of JS, and we can help. Let us know what you’re working on and we can point you in the right direction.

And if you have interesting use cases for running a FileMaker script on hover, we’d love to hear about that too. Don’t forget, you can also add buttons to DayBack to run your own scripts (FileMaker scripts or JavaScript) and buttons may make more sense for some actions. More here: custom button actions in DayBack.

Get It Now

If you’re already using DayBack, tooltips and the new On Event Hover action are free in-app updates. Just click “Check for Updates” from the upper right corner. If you’re new to in-app updates, you can see them in action here: how in-app updates add new features and preserve your customizations.

If you’re not yet using DayBack, download an unlocked trial, link it to your files, and see if it can make a difference for your team’s schedule…

 Download an Unlocked 30-Day Trial of DayBack  

This is the second in a series of articles on using the Gmail API from FileMaker. The first article has some background on this approach as well as instructions for authenticating to the Gmail API and sending HTML emails. Please review that article here if you haven’t already. Additionally, there’s a great post by dbservices on integrating Gmail with FileMaker that lead to these articles and should be checked out as well.

As with the first article, all of these examples use the native Insert From URL script step so there won’t be any plug-ins required, and since the Insert From URL is supported in all aspects of the FileMaker platform, these techniques can be adapted to work on the Server, Go, FileMaker Cloud, and WebDirect. These techniques require FileMaker 16 or higher as they use the advanced cURL options introduced in that version.

In this article, we’re looking at sending large, multiple attachments via Gmail. Here’s a video overview along with a new free example file below.


FileMaker Gmail Integration: Example File

Please download the example file FM2Gmail v1.2 for a working demo. This new version adds the ability to send attachments and replaces v1.1 from the previous article.

FileMaker Gmail Integration

FM2Gmail Example File v1.2

Sending an Email with Attachments from FileMaker

Before we can send anything, we do need to authenticate our app with Google. Please refer to our previous article’s section on Getting Started / Authentication if you need to review these steps. Once we’re all authenticated, we can compose a new e-mail with attachments. You’ll notice in the new example file that the compose window has a new paper clip button for adding attachments. This button brings up a Card window which we can use to drag attachments in, add individual attachments and import entire folders of images or text files. Read Full Article →

This is the first in a series of articles on using the Gmail API from FileMaker. We’ll provide free example files for each post and these examples will all use the native Insert From URL script step so there won’t be any plug-ins required.

In this article, we’re going to look at sending HTML emails. In future articles, I’ll examine sending large emails (35MB) with multiple attachments, resumable uploading, and managing threads. This approach provides a first-rate email experience that is not available using the native Send Mail script step. And, since the Insert From URL script step is supported natively across the whole FileMaker platform, the techniques shown here work on the Server, Go, FileMaker Cloud and WebDirect. This technique requires FileMaker 16 or higher since we’ll be using the advanced cURL options introduced in FileMaker 16.

Here’s an introduction. Step-by-step instructions and an unlocked example file follow:

Background and Choosing the Gmail API

I recently had the opportunity to build a comprehensive Gmail integration into a client’s system. The main reason the client wanted to go the Gmail route was to have seamless integration with their native Gmail experience; at first they weren’t that interested in threads or large attachments, but those features soon became important once they started emailing from within FileMaker.

Before we started, the client and I discussed which route we wanted to take, like using a plug-in or rolling our own. Fortunately, right about this time, dbservices published a great blog post and example file on integrating with the Gmail API. This article provided great techniques for authenticating to Google as well as creating an inbox in FileMaker that would import Gmails with their attachments. Basically, they had already done a lot of the work we needed. I implemented their authentication and inbox routine and then added the techniques I’m going to share here.

Read Full Article →

Track estimated vs. actual time right in your FileMaker Calendar

We recently customized DayBack for a team tracking the manufacturing and assembly trade show displays. Folks on the manufacturing floor use DayBack to see what they’re scheduled to work on AND to log their time. They can then compare estimated to actual time with Calendar Analytics.

DayBack is designed to be customized and provides several hooks where you can add your own time tracking scripts and layouts. This post illustrates five different approaches and includes instructions/examples below.

If you’re using DayBack to see what you need to work on, it makes sense to log time right there as well. Here’s what we did for this customer:

Time tracking in FileMaker Calendar

Logging time in a card window from within DayBack Calendar.

Time Tracking FileMaker Estimated Actual

Comparing estimated to actual time in Calendar Analytics

Time Tracking in FileMaker: Five Methods within DayBack Calendar

1. Card Windows

Read Full Article →

By modifying just one FileMaker script, you can add CSS specific to certain users or privilege sets. Use this to…

  • Swap out or remove buttons
  • Show or hide different calendar views
  • Show or hide individual fields in an event
  • Add icons for certain event statuses
  • Show or hide help icons
  • Code examples for all of these, and more, are here.

Edit the script “Export Theme ({Preview})” and in the Else branch, replace the single ExportFieldContents line with lines 22 through 31 in the screenshot below. You’ll see just a single branch here for the user “Bob”, but change that to “=” and you can create a separate branch for each user who needs special CSS. (Click on the image for a larger version.)

Custom CSS for each DayBack User

Line 25, which you can’t really read in the screenshot, is where you actually add new CSS. Here is the second part of the SetField dialog and the example here just turns off the green plus button:

Don’t forget to include the regular CSS at the end, in the last two lines which reference the CalendarInterface::ExportGlob. You’ll find examples of some common CSS changes here: customizing DayBack’s CSS.

Note that the script above only runs at startup, so if you are having users log in and out of your solution after startup, you’ll want to run DayBack’s “Upon Opening” script after each login change.


Analytics (charting) is now available on all scheduling views in DayBack for FileMaker. Here are some screenshots of the same data, first in the multi-day scheduling view and then in horizon view.

Calendar analytics in multi-day scheduling for FileMaker

Three trucks over 10 days: when the chart crosses the orange threshold, that truck is overbooked.

Here’s the same data in Horizon view.

Both views have their advantages: horizon view is easier to read, but the scheduling view is great if you need to see what times are open. So now you can use analytics on both views.

In this example, we set the dotted orange threshold at three-installations-per-day and can now quickly see which days are exceeding our capacity. (If this field service use case applies to your work, we have a video going over the example in more detail.)

Learn more:

Overview: how analytics drive better decisions

How we use analytics at SeedCode

Download an unlocked 30-day trial of DayBack and add it to your file.

Add this to your copy

This is a free in-app update to DayBack, so existing users can add it to their file without disrupting customizations they’ve already made. If you’re new to DayBack Calendar or in-app updates, here’s how they work and how they let you take advantage of new version of DayBack while you continue to customize it: in-app updates.

SeedCode can now customize your ProMaps solution so you can run your maps in FileMaker WebDirect.

ProMaps doesn’t work in WebDirect by default, but KC Embrey and Jason Young have figured out how to customize it to create a seamless user experience. Check out this short video showing ProMaps running in WebDrect: notice how it can call FileMaker scripts in WebDirect and pass found sets between WebDirect layouts and the map. We’re thrilled with how this turned out!

Add This to Your File

If you’d like to run your copy of ProMaps in WebDirect, it’s a pretty complex modification. The description below meant to show advanced developers what we’re doing with WebDirect and how they can replicate that or extend it. Unfortunately, it’s not intended to be a step-by-step guide for getting your copy of ProMaps running in WebDirect. That’s not something we can describe in a blog post, but it is something we can set up for you if you’reinterested.

If you’re a developer fluent in custom web publishing or the new Data API, read on, and we’ll describe how we’ve set this up. If you need more guidance than that, we’re happy to get you an estimate and set this up for you: once it’s up and running, you can customize it like regular ProMaps. Please get in touch.

Maps in FileMaker WebDirect – Why Is This So Hard?

Until now, the problem has been that it’s tough to call scripts in a WebDirect session from inside a web viewer in the same session. If you ask your web viewer to run a FileMaker script by URL, for example, WebDirect will ask you to log in again and start a second WebDirect session, run your start-up scripts, etc. This is a terrible user experience. WebDirect has no support for tokens or deep linking which make this kind of thing simple in most web apps: once you’re logged into Google Apps, for example, you can open a document by URL without having to log in again.

Users run into this any time the map takes you to a FileMaker layout or runs a FileMaker script. When you click on a button to view a property record in your own layout, or when you perform a find in FileMaker and then as the map to show the found set: these kinds of action require communication between the web viewer and the WebDirect session. And this communication is not built into WebDirect.

The Solution

Using a Session Table. KC and Jason figured out that on-timer triggers in WebDirect could call scripts seamlessly: the trick would be telling the on-timer to run a different script depending on what the user asked to do. So they created a session table in ProMaps which has one record for every logged in user. Now when you click a button in ProMaps that would typically run a script, ProMaps instead sends the name of the script to your record in that session table. An on-timer script in ProMaps queries your session record to see if there are any scripts it needs to execute and when it finds one, it runs that script along with any parameters.

But how does the WebViewer write to your record in the session table if the whole problem is that the WebViewer can’t call FileMaker scripts without spinning up a new session? Instead of editing your session record with a script, ProMaps uses the web publishing gateway or the Data API to edit your session record. In our deployments, we use fmxj.

fmxj.js is an open source JavaScript wrapper for FileMaker XML web publishing. Jason Young created this in 2015 for DayBack Online. We wanted a dead-simple way to talk to hosted FileMaker databases in JavaScript without a lot of dependency on third-party apps. In this ProMaps solution, it’s used to let the web viewer edit your record in the ProMaps session table; we could have used the new Data API, but we’re very familiar with fmxj and it already has a method in place for handling authentication server side.

If you’re interested in using fmxj in your own projects, here are some resources:

Note: the “drop a pin” example in this video is not a stock ProMaps feature–KC added that for a customer and wanted to show that it also worked in WebDirect. All the other functions shown in the video are built into ProMaps. If you’d like your map to do something fancy, just get in touch.

SeedCode’s Ann Kiser has added a version management component to SeedCode Complete as part of a custom project she’s working on. Complete comes with a built-in audit log, but document versioning goes further by preserving all previous iterations of an attached file and tying that to an approval process so you can know which versions are available for use. This is part of a thorough customization Ann is doing with Mark Thomas for Okamoto Corporation, the largest sock manufacturer in Japan. (We love manufacturing projects at SeedCode!)

The solution runs in both Japanese and English, and Splash, Inc. is helping with the localization.

FileMaker is a great tool for tracking this kind of approval flow since it’s so easy to send email notifications when documents pass each stage of the approval process. SeedCode Complete makes this even easier as it includes template scripts for server-side email notifications. Details on the built-in audit log can be found here: audit log.

Complete even includes a process template builder that you can customize to add milestones to your calendar as project pass through different statuses. That doesn’t do document versioning, however, without some customization. If you’re looking for a new approach to document versions and approvals, please get in touch: we’d love to chat with you.

The new analytics in DayBack Calendar have really changed the way we work at SeedCode. Here’s a closer look at how we’re using it to manage custom projects, along with some of the things that have surprised us about the user interface and design.

Your Calendar is Not a Poster


New to calendar analytics? This is a free, in-app update to DayBack Calendar for FileMaker. Videos, screenshots, and use case examples here: calendar analytics.

Here’s an extension of SeedCode Complete designed by Jim Parvin of Parvin Paving and Sealing. In addition to the master-detail location browser on the left, Jim brought all the slide panels forward as tabs since he had large monitors and lots of space.

SeedCode Complete FileMaker Template

I like how Jim used the slide panels in Complete as a palette of interface elements and brought forward the ones he wanted, arranging them on a single screen. (Jim designed these layouts, and SeedCode’s Dan Wheelon and Ann Kiser put them together.)

We’ve seen many folks do this, moving things off slide panels into tabs or card windows and arranging them to build new interface elements. For example, the master-detail pane used for selecting locations above borrows filters from Complete’s contact selector. That was our goal with the SeedCode Complete template: to wire up the hard stuff and the basics so that developers could quickly add value with customizations specific to their business.

Big thanks to Jim at Parvin Paving and Sealing for letting us show off his app!

 Download SeedCode Complete  

Shop The SaleYear End Sale: up to 25% off all add-ons
DayBack Calendar
DayBack's 30-day trial is unlocked so you can customize it and integrate it with your files.
Download DayBack and we'll send you a couple short emails with tips on how to modify it and use some of the coolest features.
Thank you! Please download: DayBack Calendar
Need More?
SeedCode tips & example files in your inbox
Need More?
SeedCode tips & example files in your inbox
Want More?
Be the first to see articles and tips like these
Download TimeZync and we'll send you a couple short emails with tips syncing your FileMaker Go files.
Thank you! Please download: TimeZync
Want More?
Be the first to see articles and tips like these