Upgrading from DayBack Classic

We've been building FileMaker calendars since 2003, and with this FileMaker 19 version, we're able to offer features we've always wanted while making it incredibly simple to add DayBack to existing solutions.

What's "DayBack Classic"?

DayBack Classic is what we're calling the version of DayBack that was available for FileMaker 13 through 18. Now, thanks to improvements in FileMaker 19, you can use the same DayBack that folks have been using in Salesforce and G-Suite, now updated for improved performance and a much simpler integration in FileMaker Client and WebDirect.


Upgrade Pricing

Price Changes

The new DayBack is $9.89 per user per month when billed monthly or $8.00 per user per month when billed yearly ( saving you nearly 20%). There won't be unlimited user pricing anymore, but we offer tiered discounts to folks with more than 20 users. There is a pricing FAQ available here: DayBack Pricing.

Upgrade Discounts 

If you purchased DayBack as a one-time purchase (instead of on a monthly or yearly plan), we're offering 35% off your the first year (or your first nine months if you chose a monthly plan), with steeper discounts for folks who have subscribed to in-app updates or bought within the last year. Please get in touch so we can put together an upgrade offer for your specific situation.

If you have a monthly or yearly subscription and fewer than five users, there will be almost no change in your prices if you upgrade. If you currently have an unlimited user license, let us know how many users you need, and we'll put together an upgrade package that works for you.


Integration Steps for Upgraders

If You Linked DayBack Classic to Your File

You "linked" DayBack Classic if the calendar is running as its own file alongside the other FileMaker files in your solution. DayBack's integration with SeedCode Complete is also a "linked" integration.

You can link the new DayBack file to your solution as well, keeping both calendars running while you get the new DayBack set up the way you'd like.

You'll follow the linking instructions and none of the fields you add to your tables will have any name-collisions with the older DayBack fields already there.

Customizations you've made to the CSS in DayBack Classic can be pasted into the new CSS area in DayBack's admin settings.

If you've customized the script DayBack Classic uses to edit your events ("Create Edit Delete Event ( SourceNo..."), you'll find a very similar script in the new DayBack ("Create Edit Delete Event - DayBack") where you can make the same changes.

Your resources and statuses were stored in value lists in DayBack Classic but are now stored in DayBack's settings. Add statuses and resources in the left-hand sidebar to match the ones you have in Classic, or learn how to pull those statuses and resources from a request into your FileMaker file.

When you have the new DayBack set up the way you'd like you'll delete the Classic fields from your events table and remove the old Classic calendar file.

If You Embedded DayBack Classic into Your File

You "embedded" DayBack Classic if you pasted the calendar into one of the files in your as a new layout.

You can embed the new DayBack file in your solution alongside Classic, keeping both calendar layouts running while you get the new DayBack set up the way you'd like.

You'll follow the embedding instructions and none of the fields, scripts, or tables you'll add to your file will have any name-collisions with the older DayBack fields already there.

Customizations you've made to the CSS in DayBack Classic can be pasted into the new CSS area in DayBack's admin settings.

If you've customized the script DayBack Classic uses to edit your events ("Create Edit Delete Event ( SourceNo..."), you'll find a very similar script in the new DayBack ("Create Edit Delete Event - DayBack") where you can make the same changes.

Your resources and statuses were stored in value lists in DayBack Classic but are now stored in DayBack's settings. Add statuses and resources in the left-hand sidebar to match the ones you have in Classic, or learn how to pull those statuses and resources from a request into your FileMaker file.

When you have the new DayBack set up the way you'd like you'll delete the Classic fields, layouts, scripts, and tables.


System Requirements

The big difference is that the new DayBack requires FM19 or higher and won't work offline. Details are here: system requirements.

Still need help? Message Us Message Us