Preparing Your File - DayBack for FileMaker
Preparing Your File: Overview
Once you've prepared your file, you'll do the real integration inside DayBack, using the forms and drop-downs in the calendar's admin section to declare how you'd like your tables to show up on your calendar. But first, you need to get DayBack into your solution, and that's what this page of instructions is for.
There are two approaches to integrating DayBack with your existing FileMaker file: embedding and linking.
Two Options: Embedding vs Linking
Embedding the calendar into your file means the calendar ends up as a layout (its own layout, not part of an existing layout) in your file so you'll discard the DayBack example file when you're done. Embedding can be accomplished in two ways:
Embedding Using an Add-On
The new add-on technology in FileMaker 19 lets you add new scripts and layouts to your file with one click. This is by far the fastest way to add DayBack to your solution.
Embedding by Hand
This is the old, pre-19 method to add new scripts, layouts, etc. to your file: copying and pasting. The pasting has to be done in precisely the right order so this is a bit more tedious integration process but if you follow our instructions carefully it doesn't take that long.
Linking is the second fastest way to get DayBack working with your solution since you don't need to make new scripts or layouts in your file. If you often want the calendar to appear as its own window, it does that naturally when linked.
When you link DayBack to your file, you'll keep the DayBack.fmp12 file as a separate file in your solution, though you may rename it. You'll add your own table occurrences to the DayBack.fmp12 file, one for each table you'd like to see on the calendar. Or you'll use DayBack's SampleEvents_DayBack table as your events table, perhaps linking it to contacts or projects you already have.
One downside to a linked file is that, like all multi-file solutions, you'll need to have your accounts and privilege sets in both files (unless you set the calendar file to auto-open with its own, low access password for everyone)-- that's the only downside of linking And if you're using external authentication, then it's no downside at all.
Instructions for Preparing Your File: Embedding Using an Add-On
Watch the video here showing how to install DayBack as an add-on: DayBack's FileMaker 19 Add-On.
Please download the add-on here: http://dayback.com/filemaker-calendar-add-on/
Once the add-on is in your file and you can see events in DayBack, continue with step 3 here to get your records in the calendar: Integrating DayBack.
Instructions for Preparing Your File: Linking
All you'll need to do is add DayBack's six required fields to the table(s) whose dates you'd like to see in your calendar. You'll copy these fields from DayBack's example table: SampleEvents_DayBack.
Once you paste the fields into your file, a few of the calcs require some editing: you'll find instructions here: Copy & Paste Six Required Fields
After you've pasted and edited these fields, continue with step 3 here: Integrating DayBack
Instructions for Preparing Your File: Embedding by Hand
This is the old technique we used before DayBack was an add-on. This is only here for reference: for those customers who used this method in the past.
Embedding the DayBack takes a little more work as you'll need to add new layouts and scripts to your file. Fortunately, most of these things can be copy and pasted from the DayBack example file. So embedding isn't "harder" than linking, it's just a bit more tedious. But if you follow these instructions in order and don't rush ahead, you'll be done in no time.
Here we go.
Keys to Success
The most common mistake folks make integrating DayBack (or moving any FMP code from file to file) is performing steps out of order. FileMaker is very sensitive to the order in which new code is pasted into a file--create layouts before you paste in a script looking for that layout and all will be well; paste the script in before the layout expected in that script has been created and you'll have some busted code that is particularly hard to unravel.
So, even if you're an experienced developer, follow the steps here carefully and in order--at least for your first calendar integration. =)
You may not need all six tables from the DayBack example file, but that's certainly simplest. Here are some notes on each of the tables and where to paste them.
DayBack and DayBackHelper are absolutely required. If you're using the separation model, these get pasted into your interface file.
SampleEvents_DayBack and SampleToDos_DayBack. These are DayBack's example data tables: you may very well have tables for the data you'd like to see in the calendar. But you may want to paste these as well in some cases. Maybe you don't have a table to To-Dos yet? Maybe you have a project table but want a table for the appointments and tasks related to that project: you'd paste in SampleEvents and use that as a child of your projects table.
SampleContacts_DayBack and SampleProjects_DayBack you probably don't need because you already have tables for these. You may call your projects, "jobs," but if you have neither contacts or projects you may be more interested in SeedCode Complete than DayBack.
2. Relationship Graph
If you pasted in DayBack's SampleEvents_DayBack table in step 1 above then please skip this step: it has all the required fields in it. If you're pointing DayBack at your own events table, however, you'll need to copy and paste six required fields from the example file into your events table.
Follow the instructions here and then return to this page, and to step 4 below, when you're done: Copy & Paste Six Required Fields
4. Value Lists
Open the DayBack example file and recreate the two value lists from our example in your file. Feel free to use your own list of statuses, resources, but rename them to the value list names we're using in DayBack: you can name them back later. Sadly there is no way to copy and paste value lists in FileMaker 19.
5. Theme & Layouts Part 1
The previous version of DayBack had 22 layouts. This new version has only 13, but it can still take a while to create them, so take your time.
Before creating your layouts, import the DayBack theme from the DayBack example file. Go to File / Manage / Themes in your file and select "Import". Down the road, you can change the way all these layouts look: having a theme for them will make that process easier.
Finally, delete the default layouts created when you imported tables in step 1 above.