We have two new open positions; one for an advanced FileMaker developer for custom projects, and one for a customer support role with JavaScript experience. Details, salary range, benefits, and an outline of the hiring process can all be found here: Working with Us.

Advanced FileMaker Developer

We’re looking for an advanced FileMaker developer to join the SeedCode team and help us deploy and extend large custom apps for our clients. In addition to building and supporting DayBack Calendar, we do a lot of small custom projects to help our customers deploy it. Some of those projects become very large, multi-year engagements.

You’ll be working on one or more of these large projects and collaborating with senior developers who have worked on the projects before you. (You’ll also have an opportunity to mentor junior developers, some of whom are new to FileMaker, having come from JavaScript or Salesforce backgrounds.) Learn More

Customer Support & JavaScript

We’re looking for someone to support and extend DayBack Calendar for our customers. You’ll be answering customers’ questions, augmenting our documentation, and helping customers modify the JavaScript snippets they use to customize their calendars.

For many of our customers, DayBack is the first opportunity they’ve had to design a scheduling app that works for them. It’s the first time they’re not overextended: not making promises they can’t keep. Helping customers get all this accomplished is incredibly satisfying. You’ll be joining a team that is beloved by our customers: a team that gets a lot of thanks and that our customers refer to as heroes. Learn More

Hiring Advanced FileMaker Developer

DayBack for FileMaker allows you to drag-select multiple events on the calendar and drag to reschedule them all at once. But what if you’d like to do something besides changing their date or time? You may want to delete them all at once or change their status.

Now you can add buttons to the calendar that will operate against the selected group of events. In this example, we’ve added buttons to DayBack’s “button launcher” to change the status of selected events.

Find example code and instructions for adding this to your DayBack here: Edit Multiple Events at Once.

We’ve collected nearly 100 of the most popular calendar customizations into a searchable library, making it easier than ever to change the way your calendar behaves.

FileMaker Calendar Customizations

Many of these mods are things you can paste right into your DayBack. Others you’ll want to download and modify. And a few will require our help to deploy. But most have example code and videos so that you can build the workflows and automation you’ve always wanted in your schedule.

FileMaker Calendar Customizations

Check Out the Library

Building realistic schedules gives customers confidence that you’ll keep your promises. Now DayBack gives your dispatchers the confidence to make those promises by visualizing drive times and distances in your schedule.

In this example, the DayBack compares a day’s mileage across a field service team:

SeedCode offers ProMaps as a stand-alone mapping template for FileMaker. ProMaps supports routes and filtering. But adding mapping inside DayBack can mean better scheduling decisions, not just better routing decisions for a schedule that’s not ideal.

Drive times in FileMaker Calendar

Drive time and mapping integrations in DayBack are customizations deployed as part of our implementation packages. We can create time and distance calculators to match your specific workflows and include warnings when your schedule exceeds your constraints.

  • Is there another agent closer to the customer this week?
  • Do you have enough time to travel between appointments?
  • Is one agent traveling too far overall this week?
  • In what order should we arrange today’s jobs?

Learn more here: Displaying Distance & Drive Times

Mapping and distance math are a big part of our calendar customizations. DayBack can warn schedulers if there is insufficient drive-time between appointments or if another asset is closer to the customer that week. And our ProMaps app lets developer add mapping into their own projects.

Occasionally we take this mapping expertise in entirely new directions. In this case study, engineering firm Marx|Okubo wanted to email damage assessment maps to property owners within minutes of a quake in their area. Ann Kiser, SeedCode’s director of custom projects, designed an excellent solution that listens to the USGS feed, finds potentially affected properties, calculates likely damage, and emails graphics and reports automatically.

FileMaker Map Seismic

SeedCode’s Ann Kiser with Alan Corkhill, director of technology for Marx|Okubo

This solution is now a vital component of the ASAP product (Automated Structure Alert Program) Marx|Okubo is marketing in seismically active areas. It’s one thing to build software for someone; it’s another for them to take our work into a product: we couldn’t be more proud.

Claris FileMaker Map Add-On

Damage intensity radiating from a quake

Plotting affected properties and their potential damage

Big thanks to Ann, Jason, and KC at SeedCode, who worked on this, and Alan Corkhill, director of technology for Marx|Okubo, for all the engineering know-how and inspiration. And thanks to the marketing team at Claris for filming a great customer success story.

Introduction to AI in FileMaker

Building an automated invoice processing app to scan, and code invoice line items using OCR and AI in FileMaker

For the last few years, I’ve enjoyed the opportunity to work as the primary developer on the custom FileMaker app for Blueprint Capital REIT, a real estate lending and development firm based in Seattle, WA. Although their app uses and integrates with a variety of tools and services, my head is usually living exclusively in FileMaker-land, extending the data model, building new layouts, and scripting workflows. So when the opportunity comes to integrate with something new outside of FileMaker, I get excited. And maybe a little nervous. And much more so (both excitement and nerves) for the prospect of adding some Artificial Intelligence to their app!

I, like many software developers, can often hold a (healthy?) skepticism of AI.

But as Blueprint’s accounting team took on more customers, they faced some challenges that improving the data-entry workflow alone couldn’t resolve. They estimated it cost $8 to process a single invoice; multiply that by an average of 1,200 (and growing) per month, and invoice processing quickly becomes an expensive task. Perhaps even more costly were the long hours and late nights the team put in each month. To make a significant impact, we would need to automate more of the process with the help of AI. Read Full Article →

Now filter your resources by skill or location to focus on just the resources needed for a particular job. Resources get a big upgrade in this release of DayBack for FileMaker 19: you can now add a description and any number of tags to your resources.

The new resource filter sees these tags so you can quickly narrow the schedule down to your relevant assets.

Resource Filters in FileMaker Calendar - screenshot

Watch a video of this in action and learn more: Resource Filters and Skill-Based Scheduling.

Single Page Applications (SPAs) have a significant advantage over traditional multi-page applications in that they load assets when a client initially accesses the app. This means that routing can be very fast; the user doesn’t have to load a new HTML file every time they navigate within the application. But this advantage also creates a unique problem: after deployment, users will only have the latest version of your app once they refresh the site.

Create React App uses Webpack to generate new builds, and Webpack will automatically hash filenames to make sure the client doesn’t hold on to old assets. Assuming your cache is properly configured, all you need from the user is a refresh to ensure they get the changes from your last deployment.

Alerting the User

So how do we let the user know they should refresh the app? Well, you may have seen an increasingly popular pattern for handling this: the new version available alert.

New version notification in Inbox (Screenshot)

Google Inbox (RIP) letting you know their team has deployed a new version

This pattern is used in many of Google’s products, including the Firebase Dev Console and Android Messages for web. It’s also used by my favorite budgeting app, YNAB. There are several ways to detect a version change on the frontend, including using service workers, regular calls to a server, and timers that run a check on index.html. All of these work, but they’re also fairly involved. Read Full Article →

KC Embrey has written a custom action to turn the “new event” button in DayBack into a calendar selector. This lets you make new events even faster and is the basis for creating event templates.

Here’s a short video of this mod in action:

KC wrote the original version back in May but just updated it to work in DayBack for FileMaker 19, since FileMaker’s web viewer blocks the right-click listener from firing. In FileMaker, you’ll activate this feature with a key combo like shift-s.

Find details and code you can paste into your DayBack here: make your own calendar selector.

With the move to replace Internet Explorer with Edge as the web viewer backend in FileMaker 19.3, the new default security settings make FMP URLs require more user interaction. You’ll be prompted much to authorize your web viewer to run FileMaker scripts once a session or as often as every time.

(If you’re new to these changes, our blog post on FileMaker 19.3 Web Viewers explains the issue and changes required in DayBack Classic.)

Thanks to Christian at Monkeybread Software for providing the correct registry key, we now have a way to tell the web viewer that we don’t need to be prompted every time we use an FMP URL link in our file. We’ve modified Christian’s instructions a bit to also include the version-specific fmp19 URL that is used in DayBack Classic. We’ve also provided a one-click registry patch file if you’d like, so you don’t have to modify your registry manually.

Here’s a link to download the patch file. To install it, open the FM193FMPFix.reg file that’s inside the compressed zip folder and acknowledge that you want it to be installed on your machine. Then re-open FileMaker and you should no longer be prompted when using FMP URL links from web viewers.

If you’d rather add the key manually in your registry:

1. Open up Registry Editor on your machine.

2. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft

3. Select the “Edge” key, or create a new one if it doesn’t exist

4. Create a new “WebView2” key, or select it if it already exists.

5. Create a new string value named “AutoLaunchProtocolsFromOrigins” with the following value:

This is how it should look:

6. Exit Registry Editor and re-open FileMaker and you should no longer be prompted when using FMP URLs from web viewers.

Thanks again to Christian at Monkeybread for the help with this one!

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