Upgrading from DayBack Classic

Since 2003, we've been creating FileMaker calendars, and with this new version for FileMaker 19 and higher, we’ve finally achieved the features we've always wanted, while making it incredibly easy to integrate DayBack into existing solutions. With the new DayBack now installed as an add-on, adding it to your file just takes a few clicks, allowing you to focus more on customizing it rather than spending time on the installation process.

The New DayBack for FileMaker 19

What's "DayBack Classic"?

"DayBack Classic" refers to the version of DayBack that was available for FileMaker versions 13 through 18. With the advancements in FileMaker 19, you can now use the same updated DayBack that has been popular in Salesforce and G-Suite, offering improved performance and a much simpler integration process in both FileMaker Client and WebDirect.

Upgrade Pricing

Price Changes

The new DayBack is priced at $9.89 per user per month when billed monthly or $8.00 per user per month when billed annually, saving you nearly 20%. While we no longer offer unlimited user pricing, tiered discounts are available for organizations with more than 20 users. You can find more details in our pricing FAQ: DayBack Pricing.

Upgrade Discounts 

If you originally purchased DayBack as a one-time purchase (instead of on a monthly or yearly plan), we’re offering a 35% discount on your first year (or your first nine months if you choose a monthly plan), with even greater discounts for those who have subscribed to in-app updates or purchased within the last year. Please contact us so we can create an upgrade offer tailored to your specific situation.

For customers with a monthly or yearly subscription and fewer than five users, your pricing will remain almost the same after upgrading. If you currently hold an unlimited user license, let us know how many users you need, and we’ll work out an upgrade package that suits your needs.

Integration Steps for Upgraders

If You Linked DayBack Classic to Your File

If the calendar is running as its own file alongside the other FileMaker files in your solution, your previous setup involved "linking" DayBack Classic. The integration with SeedCode Complete also falls under this "linked" approach.

You can also link the new DayBack file to your solution, allowing both calendars to run simultaneously while you configure the new DayBack to your preferences.

Follow the linking instructions provided, to ensure that none of the fields you add to your tables will have any name conflicts with the existing DayBack Classic fields.

Migrating Customizations:

  • CSS Customizations: Any custom CSS you've applied in DayBack Classic can be easily transferred by copying and pasting it into the new CSS area found in DayBack's admin settings.
  • Script Customizations: If you’ve customized the "Create Edit Delete Event (SourceNo...)" script in DayBack Classic, you’ll find a similar script in the new DayBack ("Create Edit Delete Event - DayBack"). You can replicate your customizations in this new script.
  • Resources and Statuses: In DayBack Classic, resources and statuses were stored in value lists. In the new DayBack, these are managed within the settings. You can manually add your resources and statuses in the left-hand sidebar to match those in Classic. Alternatively, you can learn how to pull these directly from a request into your FileMaker file.

Once the new DayBack is configured to your liking, you can proceed to delete the Classic fields from your events table and remove the old Classic calendar file from your solution.

If You Embedded DayBack Classic into Your File

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

To transition to the new DayBack while maintaining your existing setup, you can embed the new DayBack file in your solution alongside the Classic version. This allows both calendar layouts to operate simultaneously as you configure the new DayBack to your preferences.

Follow the embedding instructions provided, and rest assured that the fields, scripts, and tables you add for the new DayBack will not conflict with the existing DayBack Classic components.

Migrating Customizations:

  • CSS Customizations: Any custom CSS you've applied in DayBack Classic can be transferred by copying and pasting it into the new CSS area found in DayBack's admin settings.
  • Script Customizations: If you’ve customized the "Create Edit Delete Event (SourceNo...)" script in DayBack Classic, you’ll find a similar script in the new DayBack ("Create Edit Delete Event - DayBack"). You can replicate your customizations in this new script.
  • Resources and Statuses: In DayBack Classic, resources and statuses were managed via value lists. In the new DayBack, these are stored in the settings. You can manually add your resources and statuses in the left-hand sidebar to match those in Classic. Alternatively, you can learn how to pull these directly from a request into your FileMaker file.

Once the new DayBack is configured to your satisfaction, you can proceed to delete the Classic fields, layouts, scripts, and tables from your solution.

System Requirements

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