Integration
SeedCodeCalendarFree.Integration History
Hide minor edits - Show changes to output
Changed line 9 from:
-> %newwin% [[http://www.youtube.com/watch?v=tvS53fXoWU8 | '''Movie: Linking the Free Calendar''']]
to:
-> %newwin% [[http://www.seedcode.com/videos/?youtube=tvS53fXoWU8 | '''Movie: Linking the Free Calendar''']]
Changed line 30 from:
-> Edit the definitions for these calcs, removing any leading / trailing comment tags if you pasted the fields in using FielMaker Advanced (that is, remove the /* and */ from the beginning and end of the calc. Then replace the DateStart, TimeStart, etc. fields in these calculations with the relevant fields from your events table. Make sure both calcs return the form "timestamp" and that both are indexed.
to:
-> Edit the definitions for these calcs, removing any leading / trailing comment tags if you pasted the fields in using FileMaker Advanced (that is, remove the /* and */ from the beginning and end of the calc. Then replace the DateStart, TimeStart, etc. fields in these calculations with the relevant fields from your events table. Make sure both calcs return the form "timestamp" and that both are indexed.
Changed lines 9-10 from:
-> [[http://www.youtube.com/watch?v=tvS53fXoWU8 | '''Linking the Free Calendar''']]
to:
-> %newwin% [[http://www.youtube.com/watch?v=tvS53fXoWU8 | '''Movie: Linking the Free Calendar''']]
Changed lines 1-2 from:
!! Adding SeedCode Calendar Free to your File: the Quick Version.
to:
!! Integrating the Free Calendar: Linking It
There are two ways to get the free calendar to work with your file. You can paste it into your FileMaker file (instructions follow below), or you can "link" it to your file.
Linking keeps the calendar running in a separate window, but it's the fastest way to get things working together.
You can learn how to do this by watching a short movie...
-> [[http://www.youtube.com/watch?v=tvS53fXoWU8 | '''Linking the Free Calendar''']]
...where we do the whole thing in < 7 minutes (while talking slowly). If you'd rather have the calendar IN your file, read on...
!! Adding SeedCode Calendar Free to your File: Pasting It In
There are two ways to get the free calendar to work with your file. You can paste it into your FileMaker file (instructions follow below), or you can "link" it to your file.
Linking keeps the calendar running in a separate window, but it's the fastest way to get things working together.
You can learn how to do this by watching a short movie...
-> [[http://www.youtube.com/watch?v=tvS53fXoWU8 | '''Linking the Free Calendar''']]
...where we do the whole thing in < 7 minutes (while talking slowly). If you'd rather have the calendar IN your file, read on...
!! Adding SeedCode Calendar Free to your File: Pasting It In
Changed lines 85-86 from:
-> '''11.3 Map your data.''' Then go to the layout "Source No 1" and follow the directions on the layout to map the fields there to the fields in your SampleEvents table. Map the "Summary" to a simple field for now like your event's title, just to get you up and running, then return here and try mapping the summary to something more interesting to create a [[MultiLineEvents | multi-line event]] display.
to:
-> '''11.3 Map your data.''' Then go to the layout "Source No 1" and follow the directions on the layout to map the fields there to the fields in your SampleEvents table. Map the "Summary" to a simple field for now like your event's title, just to get you up and running, then return here and try mapping the summary to something more interesting.
Changed lines 34-35 from:
-> Open SeedCode Calendar and recreate the one "Yes No" value lists in your file.
to:
-> Open SeedCode Calendar and recreate the one "Yes No" value list from our file in yours.
Changed lines 48-49 from:
-> Create a few blank layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them.
to:
-> Create a few blank layouts in your file. (We'll paste in the content for these layouts in a subsequent step.) You'll create one layout in your file for each layout in SeedCode Calendar (even though only some layouts are visible to users, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them.
Changed line 72 from:
-> Layout: Calendar (2 triggers)
to:
-> Layout: Calendar (1 trigger)
Changed lines 28-31 from:
-> Import two tables into your file from SeedCode Calendar: Calendar Rows and Calendar Interface. If you were ever wondering why people bought FileMaker Advanced, this is why. If you don't have Advanced we'd be happy to complete this step for you, just send us your file.
> > screen shot of graph
to:
-> Import two tables into your file from SeedCode Calendar: CalendarRows and CalendarInterface. If you were ever wondering why people bought FileMaker Advanced, this is why. If you don't have Advanced we'd be happy to complete this step for you, just send us your file.
%center% http://www.seedcode.com/rootimages/stikipad/nextcal/graphfree.png
%center% http://www.seedcode.com/rootimages/stikipad/nextcal/graphfree.png
Changed lines 44-45 from:
to:
%center% http://www.seedcode.com/rootimages/stikipad/nextcal/graphfree2.png
Changed lines 54-55 from:
to:
%center% http://www.seedcode.com/rootimages/stikipad/nextcal/layoutlistfree.png
Changed lines 73-74 from:
-> Trigger: OnRecordLoad - "Load Calendar Layout"
-> Trigger: OnLayoutLoad - "Load Calendar Layout"
to:
-> Trigger: OnRecordLoad - "Load Calendar Layout" (browse mode and find mode)
Changed lines 66-67 from:
-> When you get to Event Details feel free to edit this layout as you see fit, adding your own fields and buttons. Just be sure to keep the following 3 objects: the "repeat" button, the "show repts..." button below it, ad the large "close..." button at the bottom of the screen.
to:
-> When you get to Event Details feel free to edit this layout as you see fit, adding your own fields and buttons. Just be sure to keep the large "close..." button at the bottom of the screen.
Changed line 72 from:
-> Layout: Calendar (2 trigger2)
to:
-> Layout: Calendar (2 triggers)
Changed lines 75-77 from:
-> (Do this on each of the two calendar layouts.)
-> Layout: Event Details (2 triggers)
-> Layout: Event Details (
to:
-> (Do this on each of the four calendar layouts.)
-> Layout: Event Details (1 trigger)
-> Layout: Event Details (1 trigger)
Changed lines 79-80 from:
to:
Changed lines 34-37 from:
-> Open SeedCode Calendar and recreate the 5 value lists in your file. Feel free to use your list of statuses and resources. The other values lists need to stay as they are, though you can feel free to change the time formats in "Calendar Times" to suit your tastes. You might want to do that later though, once you have this up and running.
-> Here, and in what follows, you don't need to import anything to do with SampleContacts as you'll likely already have these things in your file.
-> Here, and in what follows, you don't need to import anything to do with SampleContacts as you'll likely already have these things in your file.
to:
-> Open SeedCode Calendar and recreate the one "Yes No" value lists in your file.
Changed lines 42-45 from:
-> On your relationship graph, link "CalendarRows" to "CalendarInterface" to "SampleEvents" as show on the graph in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file. Where you see "id" in our SampleEvents table, use the unique primary key from your events table. Link the Sample Events table to a new instance of your contact's table if you'd like.
-> At this point, if you want to show event colors in list view as we do in the Event List or Event Detail layouts, copy our field "z_ColorCalc" from Sample Events and add it to your events table mapping our field "status" to the equivalent field in your table: this is the field we used to color code events in the calendar.
-> At this point, if you want to show event colors in list view as we do in the Event List or Event Detail layouts, copy our field "z_ColorCalc" from Sample Events and add it to your events table mapping our field "status" to the equivalent field in your table: this is the field we used to color code events in the calendar
to:
-> On your relationship graph, link "CalendarRows" to "CalendarInterface" as show on the graph in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file.
Changed lines 48-51 from:
-> Create a few blank layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Again, you don't need to import the contact layouts unless you don't have any of your own.
-> You may want to create the separator layouts we have as well (these are based on Calendar Events) but that is just cosmetic.
-> You may want to create the separator layouts we have as well (these are based on Calendar Events
to:
-> Create a few blank layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them.
-> You may want to create the separator layouts we have as well (these are based on Calendar Interface) but that is just cosmetic.
-> You may want to create the separator layouts we have as well (these are based on Calendar Interface) but that is just cosmetic.
Changed lines 1-68 from:
'''Swapping Out the Appointments Table.'''
In many cases, it will be easier to simply modify the appointments table that comes with SeedCodeCalendar. However, if you have a complex appointments file that already has a lot of work in it, you may wish to point SeedCodeCalendar at that file instead. To do this you’ll accomplish a couple basic tasks. First, you’ll define a file reference for the file containing your appointments file and add the key calculation fields from our appointments table to the table in your file. Then, you’ll point SeedCodeCalendar at your file by editing the calendar's File References, and Relationships. Lastly, you’ll tidy up a few things by reviewing a few layouts and scripts in SeedCodeCalendar.
Experienced FileMaker developers will be able to do this pretty quickly by simply looking at the Relationship Graph for this file and the field definitions for the appointments table. Even so, the checklist below might be of help.
'''1. Backup your files.''' In addition to making a backup copy of your file, we suggest you print all calendar scripts to a PDF that you can refer back to while you're working. Printing the Relationship Graph and Field Definitions as PDFs is also prudent. While you'll have the original files as backup, it is easier to refer to PDFs while you're working.
'''2. Prepare your Appointments Fields.''' You'll need to make sure that you appointments file has a few basic fields used to relate appointments to the calendar. Note that you're fields don't have to be named the same as ours, but it can helpful to use the same names as all our documentation (and the Q & A on our support forums) refer to these field names. Even if you don't keep these names long term, using them for the duration of this modification seems like a good idea. You'll need at least the following fields in your appointments file:
-> ApptDate - the date of your appointment.
-> ApptTimeStart - The start time of your appointment.
-> ApptTimeEnd - The end time of your appointment.
These last two time fields aren’t actually required for the calendar to function, but the start time is used in some of our sorts (for instance when we sort the portal of appointments on the Daily tab). If your appointments don’t have times and you don’t need a time field, no problem: just remember that when it comes to sorting your appointments you’ll only have one sort criteria (the date) not two (the date and time).
'''3. Create a File Reference for Appointments.''' To point the calendar at your appointments table, you'll add a file reference for your appointments table in our calendar ; to keep it simple, name the file reference “AppointmentsNew” for now. Go to File / Manage / File Reference. Click “New” and then click the “add file“ button to add a line for your appointments file. Note: Do not rename the table occurrences in the calendar. The names of our existing table occurrences are frequently used in scripts.
'''4. Repoint the Daily Relationship on the Graph in SeedCodeCalendar.fp7.''' Select File / Manage / Database from the File menu and select "Relationships" so that you can see the relationships graph. All of the Green table occurrences (TOs) in this graph refer to the Appointments table; currently each of these TOs points to the original appointments table in SeedCodeCalendar. We'll need to change each of these to point to the appointments table in your file. When we do so, the relationships between these TOs will break and we'll need to fix them. Fortunately, this isn't as hard as it sounds.
Lets tackle the first one, the "Appointments" TO in the "Table Listing" section of the graph. This is up towards the top under the label “Data Tables”. Double click on this TO and you'll see the "Specify Table" dialog window. Note that the TO is currently from the "Appointments" table and that it is from the "Current File.." (You can see the file attribute in the pop up list to the right of the word "File:" near the top of this dialog.) It is important that as we repoint these TOs that we don't rename them. This one is currently called "Appointments" and we'll want to paste that name back in there after we point this at another table. From the "File:" pop up, select your appointments file. You'll now see a list of the tables in your file. Select your appointments table and then change the name of the TO so it continues to read "Appointments." Click "OK" to close the dialog. You've just "repointed" a table occurrence (TO).
Do the same thing for the next green TO on the graph, CalDailyAppointments in the Daily View section. Point this at the appointments table from your file, making sure to keep the name CalDailyAppointments. When that’s done you'll notice that your newly repointed TO is now no longer properly related to "CalendarDaily". To fix this, double click on the relationship line connecting these TOs. Edit the right side of this relationship so that...
-> CalFilterDateGlob = ApptDate
...then click OK. At this point you’ve not only re-pointed the TO, you’ve repointed the relationship as well. Lining the fields back up so that they now match the corresponding fields in your table. You're going to follow this procedure for each Green TO on the graph. Each section of the graph has its own flavor and instructions for specific sections follow.
'''5. Re-Point Month & Week Relationships.''' Select File / Manage / Database from the File menu and select "Relationships" so that you can see the relationships graph. You'll want to edit all the relationships between CalendarMonth (in blue) and the Appointments (in Green) TOs to the right of it and below it. There are 8 of these all together and all but one follow the same basic format. Lets look at the first one: check out the relationship between CalendarMonth (in blue) and CalMonthAppointments01 (in Green). This is in the "Month & Week Views" section. Copy the name of the TO (CalMonthAppointments01) so you can keep than name and point the TO at your appointments table just as you did with the Daily occurrence above, renaming the TO “CalMonthAppointments01” when you’re done. Double click on the "=" between these table occurrences to edit the relationship. In each case, you’ll want to make sure that the right hand side of this relationship uses “ApptDate”. The left hand side won’t require any editing.
You'll need to do this for each of the 7 green TOs to the right of CalendarMonth.
The last green TO has a slightly different relationship criteria containing two parameters instead of one. Both of these relationship parameters line up with “ApptDate” on the right so you can repoint this last TO as you’ve done the others.
'''6. Edit Layouts.''' The fields in your appointment table likely don't line up with the fields in our appointments table, so once your new relationships resolve, you'll need to edit the calendar layouts to make sure the correct fields show up in the correct places. Go through each layout in the calendar and double click on each appointment related field to check that it is displaying the correct field.
Just a few notes about some of these layouts:
-> Appointments (Print): Check to make sure the subsummary part here calls ApptDate.
-> Daily View (and others): Whenever you come to a portal of appointments, you'll want to check the portal's sort order in addition to checking the fields it contains. These sort fields get misaligned just as layout fields do during our repointing of the tables.
-> Month View: The month view layout has a number of container fields on top of the appointment fields you'll wish to edit. You'll want to unlock these objects and move them off to the side, making sure you can reposition them in exactly the same location when you're done. Everyone has their own trick for this, but do NOT move these objects backward or forward to accomplish this; it will be very difficult to get the month view to look right again. You might want to try this first on a backup copy of the layout. Once you get the hang of it you'll find you can edit this layout without incident, but take your time the first time out.
'''7. Edit Scripts.''' While you don't need to create any scripts in your appointments file, you do need to edit a few scripts in our calendar that set specific fields in the appointments table. As with layouts, your fields may not line up exactly with the original fields. Check the following scripts in SeedCodeCalendar: these scripts are thoroughly commented to make this process easier. However there are too many references to appointments to reproduce them all here: below you'll see a list of the places to check in each script. Look at your PDFs of the original scripts to make sure you select the correct field:
-> New Appointment: Check the set field statements. They should set your versions of ApptDate. The script should end with a GoToField step going to your appointment’s title field.
-> Edit Appointment - Nudge Date: Check the set fields to make sure we’re manipulating your appointment’s date field.
-> Edit Appointment - Dupe: After we duplicate the record we end the script by going to your ApptTitle field.
-> Print Appointments: You'll just want to check the sort order in this script to make sure it includes ApptDate as we use that in a summary field.
'''8. That's It!'''
to:
!! Adding SeedCode Calendar Free to your File: the Quick Version.
Most folks will paste SeedCode Calendar into their file and use an events table they already have for the events they want to see in the calendar. These instructions are for them. If you want to use the Sample Events table in SeedCode Calendar as your events table, just import it into your file in step 2 below and skip step 5.
'''1. Backup your file.'''
-> Really.
-> And this is '''important''': review a [[YourFile | couple of things]] you may want to change in your file before you get started.
'''2. Fields.'''
-> '''2.1''' Add two new fields to your event's table from SeedCode Calendar's Sample Events table:
--> z_sc_TimestampEndCalc
--> z_sc_TimestampStartCalc
-> Edit the definitions for these calcs, removing any leading / trailing comment tags if you pasted the fields in using FielMaker Advanced (that is, remove the /* and */ from the beginning and end of the calc. Then replace the DateStart, TimeStart, etc. fields in these calculations with the relevant fields from your events table. Make sure both calcs return the form "timestamp" and that both are indexed.
-> '''2.2''' Next, add the following Auto-Enter Calculated Value option to the TimeStart field in your events table:
--> If ( Self = Time ( 24 ; 0 ; 0 ) ; Time ( 24 ; 0 ; 1 ) ; Self )
-> Make sure you uncheck the "Do not replace existing value" checkbox. This Auto-Enter option is needed if you want events to be able to start at midnight.
'''3. Tables.'''
-> Import two tables into your file from SeedCode Calendar: Calendar Rows and Calendar Interface. If you were ever wondering why people bought FileMaker Advanced, this is why. If you don't have Advanced we'd be happy to complete this step for you, just send us your file.
> > screen shot of graph
'''4. Value Lists.'''
-> Open SeedCode Calendar and recreate the 5 value lists in your file. Feel free to use your list of statuses and resources. The other values lists need to stay as they are, though you can feel free to change the time formats in "Calendar Times" to suit your tastes. You might want to do that later though, once you have this up and running.
-> Here, and in what follows, you don't need to import anything to do with SampleContacts as you'll likely already have these things in your file.
'''5. Table Occurrences.'''
-> Create a new occurrence of your events table (the table that has the records you want to see on the calendar) and name it "SampleEvents" (make sure there are no spaces in the table occurrence name). You can change this name later.
'''6. Relationships.'''
-> On your relationship graph, link "CalendarRows" to "CalendarInterface" to "SampleEvents" as show on the graph in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file. Where you see "id" in our SampleEvents table, use the unique primary key from your events table. Link the Sample Events table to a new instance of your contact's table if you'd like.
-> At this point, if you want to show event colors in list view as we do in the Event List or Event Detail layouts, copy our field "z_ColorCalc" from Sample Events and add it to your events table mapping our field "status" to the equivalent field in your table: this is the field we used to color code events in the calendar.
> > screen shot of graph
'''7. Layouts Part 1.'''
-> Create a few blank layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Again, you don't need to import the contact layouts unless you don't have any of your own.
-> You may want to create the separator layouts we have as well (these are based on Calendar Events) but that is just cosmetic.
-> Delete the default layouts created when you imported tables in step 3.
> > screen shot of layout list
-> Now you may already have layouts you want to use for your Event List and Event Details. If so, take a moment to read about that here: using [[your own Event layouts]].
'''8. Scripts.'''
-> Import the scripts from SeedCode Calendar. When importing, just click the check box beside the folder "SeedCode Calendar" and all the scripts within that folder will import. There will be a number of errors reports when you import: this is normal. In "Setup" below we'll remap some of the fields and settings in these scripts to values in your file.
'''9. Layouts Part 2.'''
-> Now copy the layout contents from each layout in SeedCode Calendar and paste them into the layout of the same name in your file. And yes, we do need the contents of "Calendar Records" on that layout. The contents of "Developer" are optional. You'll be warned that you'll be increasing the size of each layout; that's OK.
-> When you get to Event Details feel free to edit this layout as you see fit, adding your own fields and buttons. Just be sure to keep the following 3 objects: the "repeat" button, the "show repts..." button below it, ad the large "close..." button at the bottom of the screen.
'''10. Layout Script Triggers.'''
-> Assign script triggers. Since layout level script triggers don't come over when you copy and paste layout elements, you'll have to recreate these. Fortunately there are only a few.
-> Layout: Calendar (2 trigger2)
-> Trigger: OnRecordLoad - "Load Calendar Layout"
-> Trigger: OnLayoutLoad - "Load Calendar Layout"
-> (Do this on each of the two calendar layouts.)
-> Layout: Event Details (2 triggers)
-> Trigger: OnRecordLoad - "On Event Record Load"
-> Trigger: OnRecordCommit - "Close Window & Refresh Calendar" (we're no longer doing this one as a script trigger. it was pretty annoying).
'''11. Setup.'''
-> '''11.1 Configure the calendar.''' Edit the script "Load Calendar Settings - On Startup..." and follow the comments changing values as necessary.
-> '''11.2 Sort your records.''' Edit the script "Sort FileMaker Records..." and follow the instructions to sort your records by date / time ascending, editing the sort step there to use fields from your events table.
-> '''11.3 Map your data.''' Then go to the layout "Source No 1" and follow the directions on the layout to map the fields there to the fields in your SampleEvents table. Map the "Summary" to a simple field for now like your event's title, just to get you up and running, then return here and try mapping the summary to something more interesting to create a [[MultiLineEvents | multi-line event]] display.
'''12. Clean Up.'''
-> Rename your Sample Events table occurrence to something that makes more sense for you. And add the script "Upon Opening" to your file's opening script, removing the go to layout stuff if you'd like.
'''13. Run a Script.'''
-> That's it. Run the script "Upon Opening" script and you should see your events in the day view.
Enjoy!
Most folks will paste SeedCode Calendar into their file and use an events table they already have for the events they want to see in the calendar. These instructions are for them. If you want to use the Sample Events table in SeedCode Calendar as your events table, just import it into your file in step 2 below and skip step 5.
'''1. Backup your file.'''
-> Really.
-> And this is '''important''': review a [[YourFile | couple of things]] you may want to change in your file before you get started.
'''2. Fields.'''
-> '''2.1''' Add two new fields to your event's table from SeedCode Calendar's Sample Events table:
--> z_sc_TimestampEndCalc
--> z_sc_TimestampStartCalc
-> Edit the definitions for these calcs, removing any leading / trailing comment tags if you pasted the fields in using FielMaker Advanced (that is, remove the /* and */ from the beginning and end of the calc. Then replace the DateStart, TimeStart, etc. fields in these calculations with the relevant fields from your events table. Make sure both calcs return the form "timestamp" and that both are indexed.
-> '''2.2''' Next, add the following Auto-Enter Calculated Value option to the TimeStart field in your events table:
--> If ( Self = Time ( 24 ; 0 ; 0 ) ; Time ( 24 ; 0 ; 1 ) ; Self )
-> Make sure you uncheck the "Do not replace existing value" checkbox. This Auto-Enter option is needed if you want events to be able to start at midnight.
'''3. Tables.'''
-> Import two tables into your file from SeedCode Calendar: Calendar Rows and Calendar Interface. If you were ever wondering why people bought FileMaker Advanced, this is why. If you don't have Advanced we'd be happy to complete this step for you, just send us your file.
> > screen shot of graph
'''4. Value Lists.'''
-> Open SeedCode Calendar and recreate the 5 value lists in your file. Feel free to use your list of statuses and resources. The other values lists need to stay as they are, though you can feel free to change the time formats in "Calendar Times" to suit your tastes. You might want to do that later though, once you have this up and running.
-> Here, and in what follows, you don't need to import anything to do with SampleContacts as you'll likely already have these things in your file.
'''5. Table Occurrences.'''
-> Create a new occurrence of your events table (the table that has the records you want to see on the calendar) and name it "SampleEvents" (make sure there are no spaces in the table occurrence name). You can change this name later.
'''6. Relationships.'''
-> On your relationship graph, link "CalendarRows" to "CalendarInterface" to "SampleEvents" as show on the graph in SeedCode Calendar. Double check that the table occurrence names match what we have in the sample file. Where you see "id" in our SampleEvents table, use the unique primary key from your events table. Link the Sample Events table to a new instance of your contact's table if you'd like.
-> At this point, if you want to show event colors in list view as we do in the Event List or Event Detail layouts, copy our field "z_ColorCalc" from Sample Events and add it to your events table mapping our field "status" to the equivalent field in your table: this is the field we used to color code events in the calendar.
> > screen shot of graph
'''7. Layouts Part 1.'''
-> Create a few blank layouts in your file. You'll create one layout in your file for each layout in SeedCode Calendar (yes, all these layouts are required). Layouts are either based on Calendar Rows, Calendar Interface, or Sample Events. Once you're done, go through and make sure these layouts have exactly the same names as the ones in SeedCode Calendar, and delete the headers and footers from each of them. Again, you don't need to import the contact layouts unless you don't have any of your own.
-> You may want to create the separator layouts we have as well (these are based on Calendar Events) but that is just cosmetic.
-> Delete the default layouts created when you imported tables in step 3.
> > screen shot of layout list
-> Now you may already have layouts you want to use for your Event List and Event Details. If so, take a moment to read about that here: using [[your own Event layouts]].
'''8. Scripts.'''
-> Import the scripts from SeedCode Calendar. When importing, just click the check box beside the folder "SeedCode Calendar" and all the scripts within that folder will import. There will be a number of errors reports when you import: this is normal. In "Setup" below we'll remap some of the fields and settings in these scripts to values in your file.
'''9. Layouts Part 2.'''
-> Now copy the layout contents from each layout in SeedCode Calendar and paste them into the layout of the same name in your file. And yes, we do need the contents of "Calendar Records" on that layout. The contents of "Developer" are optional. You'll be warned that you'll be increasing the size of each layout; that's OK.
-> When you get to Event Details feel free to edit this layout as you see fit, adding your own fields and buttons. Just be sure to keep the following 3 objects: the "repeat" button, the "show repts..." button below it, ad the large "close..." button at the bottom of the screen.
'''10. Layout Script Triggers.'''
-> Assign script triggers. Since layout level script triggers don't come over when you copy and paste layout elements, you'll have to recreate these. Fortunately there are only a few.
-> Layout: Calendar (2 trigger2)
-> Trigger: OnRecordLoad - "Load Calendar Layout"
-> Trigger: OnLayoutLoad - "Load Calendar Layout"
-> (Do this on each of the two calendar layouts.)
-> Layout: Event Details (2 triggers)
-> Trigger: OnRecordLoad - "On Event Record Load"
-> Trigger: OnRecordCommit - "Close Window & Refresh Calendar" (we're no longer doing this one as a script trigger. it was pretty annoying).
'''11. Setup.'''
-> '''11.1 Configure the calendar.''' Edit the script "Load Calendar Settings - On Startup..." and follow the comments changing values as necessary.
-> '''11.2 Sort your records.''' Edit the script "Sort FileMaker Records..." and follow the instructions to sort your records by date / time ascending, editing the sort step there to use fields from your events table.
-> '''11.3 Map your data.''' Then go to the layout "Source No 1" and follow the directions on the layout to map the fields there to the fields in your SampleEvents table. Map the "Summary" to a simple field for now like your event's title, just to get you up and running, then return here and try mapping the summary to something more interesting to create a [[MultiLineEvents | multi-line event]] display.
'''12. Clean Up.'''
-> Rename your Sample Events table occurrence to something that makes more sense for you. And add the script "Upon Opening" to your file's opening script, removing the go to layout stuff if you'd like.
'''13. Run a Script.'''
-> That's it. Run the script "Upon Opening" script and you should see your events in the day view.
Enjoy!
Added lines 1-68:
!! How Can I Use My Own Appointments File in the Calendar?
'''Swapping Out the Appointments Table.'''
In many cases, it will be easier to simply modify the appointments table that comes with SeedCodeCalendar. However, if you have a complex appointments file that already has a lot of work in it, you may wish to point SeedCodeCalendar at that file instead. To do this you’ll accomplish a couple basic tasks. First, you’ll define a file reference for the file containing your appointments file and add the key calculation fields from our appointments table to the table in your file. Then, you’ll point SeedCodeCalendar at your file by editing the calendar's File References, and Relationships. Lastly, you’ll tidy up a few things by reviewing a few layouts and scripts in SeedCodeCalendar.
Experienced FileMaker developers will be able to do this pretty quickly by simply looking at the Relationship Graph for this file and the field definitions for the appointments table. Even so, the checklist below might be of help.
'''1. Backup your files.''' In addition to making a backup copy of your file, we suggest you print all calendar scripts to a PDF that you can refer back to while you're working. Printing the Relationship Graph and Field Definitions as PDFs is also prudent. While you'll have the original files as backup, it is easier to refer to PDFs while you're working.
'''2. Prepare your Appointments Fields.''' You'll need to make sure that you appointments file has a few basic fields used to relate appointments to the calendar. Note that you're fields don't have to be named the same as ours, but it can helpful to use the same names as all our documentation (and the Q & A on our support forums) refer to these field names. Even if you don't keep these names long term, using them for the duration of this modification seems like a good idea. You'll need at least the following fields in your appointments file:
-> ApptDate - the date of your appointment.
-> ApptTimeStart - The start time of your appointment.
-> ApptTimeEnd - The end time of your appointment.
These last two time fields aren’t actually required for the calendar to function, but the start time is used in some of our sorts (for instance when we sort the portal of appointments on the Daily tab). If your appointments don’t have times and you don’t need a time field, no problem: just remember that when it comes to sorting your appointments you’ll only have one sort criteria (the date) not two (the date and time).
'''3. Create a File Reference for Appointments.''' To point the calendar at your appointments table, you'll add a file reference for your appointments table in our calendar ; to keep it simple, name the file reference “AppointmentsNew” for now. Go to File / Manage / File Reference. Click “New” and then click the “add file“ button to add a line for your appointments file. Note: Do not rename the table occurrences in the calendar. The names of our existing table occurrences are frequently used in scripts.
'''4. Repoint the Daily Relationship on the Graph in SeedCodeCalendar.fp7.''' Select File / Manage / Database from the File menu and select "Relationships" so that you can see the relationships graph. All of the Green table occurrences (TOs) in this graph refer to the Appointments table; currently each of these TOs points to the original appointments table in SeedCodeCalendar. We'll need to change each of these to point to the appointments table in your file. When we do so, the relationships between these TOs will break and we'll need to fix them. Fortunately, this isn't as hard as it sounds.
Lets tackle the first one, the "Appointments" TO in the "Table Listing" section of the graph. This is up towards the top under the label “Data Tables”. Double click on this TO and you'll see the "Specify Table" dialog window. Note that the TO is currently from the "Appointments" table and that it is from the "Current File.." (You can see the file attribute in the pop up list to the right of the word "File:" near the top of this dialog.) It is important that as we repoint these TOs that we don't rename them. This one is currently called "Appointments" and we'll want to paste that name back in there after we point this at another table. From the "File:" pop up, select your appointments file. You'll now see a list of the tables in your file. Select your appointments table and then change the name of the TO so it continues to read "Appointments." Click "OK" to close the dialog. You've just "repointed" a table occurrence (TO).
Do the same thing for the next green TO on the graph, CalDailyAppointments in the Daily View section. Point this at the appointments table from your file, making sure to keep the name CalDailyAppointments. When that’s done you'll notice that your newly repointed TO is now no longer properly related to "CalendarDaily". To fix this, double click on the relationship line connecting these TOs. Edit the right side of this relationship so that...
-> CalFilterDateGlob = ApptDate
...then click OK. At this point you’ve not only re-pointed the TO, you’ve repointed the relationship as well. Lining the fields back up so that they now match the corresponding fields in your table. You're going to follow this procedure for each Green TO on the graph. Each section of the graph has its own flavor and instructions for specific sections follow.
'''5. Re-Point Month & Week Relationships.''' Select File / Manage / Database from the File menu and select "Relationships" so that you can see the relationships graph. You'll want to edit all the relationships between CalendarMonth (in blue) and the Appointments (in Green) TOs to the right of it and below it. There are 8 of these all together and all but one follow the same basic format. Lets look at the first one: check out the relationship between CalendarMonth (in blue) and CalMonthAppointments01 (in Green). This is in the "Month & Week Views" section. Copy the name of the TO (CalMonthAppointments01) so you can keep than name and point the TO at your appointments table just as you did with the Daily occurrence above, renaming the TO “CalMonthAppointments01” when you’re done. Double click on the "=" between these table occurrences to edit the relationship. In each case, you’ll want to make sure that the right hand side of this relationship uses “ApptDate”. The left hand side won’t require any editing.
You'll need to do this for each of the 7 green TOs to the right of CalendarMonth.
The last green TO has a slightly different relationship criteria containing two parameters instead of one. Both of these relationship parameters line up with “ApptDate” on the right so you can repoint this last TO as you’ve done the others.
'''6. Edit Layouts.''' The fields in your appointment table likely don't line up with the fields in our appointments table, so once your new relationships resolve, you'll need to edit the calendar layouts to make sure the correct fields show up in the correct places. Go through each layout in the calendar and double click on each appointment related field to check that it is displaying the correct field.
Just a few notes about some of these layouts:
-> Appointments (Print): Check to make sure the subsummary part here calls ApptDate.
-> Daily View (and others): Whenever you come to a portal of appointments, you'll want to check the portal's sort order in addition to checking the fields it contains. These sort fields get misaligned just as layout fields do during our repointing of the tables.
-> Month View: The month view layout has a number of container fields on top of the appointment fields you'll wish to edit. You'll want to unlock these objects and move them off to the side, making sure you can reposition them in exactly the same location when you're done. Everyone has their own trick for this, but do NOT move these objects backward or forward to accomplish this; it will be very difficult to get the month view to look right again. You might want to try this first on a backup copy of the layout. Once you get the hang of it you'll find you can edit this layout without incident, but take your time the first time out.
'''7. Edit Scripts.''' While you don't need to create any scripts in your appointments file, you do need to edit a few scripts in our calendar that set specific fields in the appointments table. As with layouts, your fields may not line up exactly with the original fields. Check the following scripts in SeedCodeCalendar: these scripts are thoroughly commented to make this process easier. However there are too many references to appointments to reproduce them all here: below you'll see a list of the places to check in each script. Look at your PDFs of the original scripts to make sure you select the correct field:
-> New Appointment: Check the set field statements. They should set your versions of ApptDate. The script should end with a GoToField step going to your appointment’s title field.
-> Edit Appointment - Nudge Date: Check the set fields to make sure we’re manipulating your appointment’s date field.
-> Edit Appointment - Dupe: After we duplicate the record we end the script by going to your ApptTitle field.
-> Print Appointments: You'll just want to check the sort order in this script to make sure it includes ApptDate as we use that in a summary field.
'''8. That's It!'''
'''Swapping Out the Appointments Table.'''
In many cases, it will be easier to simply modify the appointments table that comes with SeedCodeCalendar. However, if you have a complex appointments file that already has a lot of work in it, you may wish to point SeedCodeCalendar at that file instead. To do this you’ll accomplish a couple basic tasks. First, you’ll define a file reference for the file containing your appointments file and add the key calculation fields from our appointments table to the table in your file. Then, you’ll point SeedCodeCalendar at your file by editing the calendar's File References, and Relationships. Lastly, you’ll tidy up a few things by reviewing a few layouts and scripts in SeedCodeCalendar.
Experienced FileMaker developers will be able to do this pretty quickly by simply looking at the Relationship Graph for this file and the field definitions for the appointments table. Even so, the checklist below might be of help.
'''1. Backup your files.''' In addition to making a backup copy of your file, we suggest you print all calendar scripts to a PDF that you can refer back to while you're working. Printing the Relationship Graph and Field Definitions as PDFs is also prudent. While you'll have the original files as backup, it is easier to refer to PDFs while you're working.
'''2. Prepare your Appointments Fields.''' You'll need to make sure that you appointments file has a few basic fields used to relate appointments to the calendar. Note that you're fields don't have to be named the same as ours, but it can helpful to use the same names as all our documentation (and the Q & A on our support forums) refer to these field names. Even if you don't keep these names long term, using them for the duration of this modification seems like a good idea. You'll need at least the following fields in your appointments file:
-> ApptDate - the date of your appointment.
-> ApptTimeStart - The start time of your appointment.
-> ApptTimeEnd - The end time of your appointment.
These last two time fields aren’t actually required for the calendar to function, but the start time is used in some of our sorts (for instance when we sort the portal of appointments on the Daily tab). If your appointments don’t have times and you don’t need a time field, no problem: just remember that when it comes to sorting your appointments you’ll only have one sort criteria (the date) not two (the date and time).
'''3. Create a File Reference for Appointments.''' To point the calendar at your appointments table, you'll add a file reference for your appointments table in our calendar ; to keep it simple, name the file reference “AppointmentsNew” for now. Go to File / Manage / File Reference. Click “New” and then click the “add file“ button to add a line for your appointments file. Note: Do not rename the table occurrences in the calendar. The names of our existing table occurrences are frequently used in scripts.
'''4. Repoint the Daily Relationship on the Graph in SeedCodeCalendar.fp7.''' Select File / Manage / Database from the File menu and select "Relationships" so that you can see the relationships graph. All of the Green table occurrences (TOs) in this graph refer to the Appointments table; currently each of these TOs points to the original appointments table in SeedCodeCalendar. We'll need to change each of these to point to the appointments table in your file. When we do so, the relationships between these TOs will break and we'll need to fix them. Fortunately, this isn't as hard as it sounds.
Lets tackle the first one, the "Appointments" TO in the "Table Listing" section of the graph. This is up towards the top under the label “Data Tables”. Double click on this TO and you'll see the "Specify Table" dialog window. Note that the TO is currently from the "Appointments" table and that it is from the "Current File.." (You can see the file attribute in the pop up list to the right of the word "File:" near the top of this dialog.) It is important that as we repoint these TOs that we don't rename them. This one is currently called "Appointments" and we'll want to paste that name back in there after we point this at another table. From the "File:" pop up, select your appointments file. You'll now see a list of the tables in your file. Select your appointments table and then change the name of the TO so it continues to read "Appointments." Click "OK" to close the dialog. You've just "repointed" a table occurrence (TO).
Do the same thing for the next green TO on the graph, CalDailyAppointments in the Daily View section. Point this at the appointments table from your file, making sure to keep the name CalDailyAppointments. When that’s done you'll notice that your newly repointed TO is now no longer properly related to "CalendarDaily". To fix this, double click on the relationship line connecting these TOs. Edit the right side of this relationship so that...
-> CalFilterDateGlob = ApptDate
...then click OK. At this point you’ve not only re-pointed the TO, you’ve repointed the relationship as well. Lining the fields back up so that they now match the corresponding fields in your table. You're going to follow this procedure for each Green TO on the graph. Each section of the graph has its own flavor and instructions for specific sections follow.
'''5. Re-Point Month & Week Relationships.''' Select File / Manage / Database from the File menu and select "Relationships" so that you can see the relationships graph. You'll want to edit all the relationships between CalendarMonth (in blue) and the Appointments (in Green) TOs to the right of it and below it. There are 8 of these all together and all but one follow the same basic format. Lets look at the first one: check out the relationship between CalendarMonth (in blue) and CalMonthAppointments01 (in Green). This is in the "Month & Week Views" section. Copy the name of the TO (CalMonthAppointments01) so you can keep than name and point the TO at your appointments table just as you did with the Daily occurrence above, renaming the TO “CalMonthAppointments01” when you’re done. Double click on the "=" between these table occurrences to edit the relationship. In each case, you’ll want to make sure that the right hand side of this relationship uses “ApptDate”. The left hand side won’t require any editing.
You'll need to do this for each of the 7 green TOs to the right of CalendarMonth.
The last green TO has a slightly different relationship criteria containing two parameters instead of one. Both of these relationship parameters line up with “ApptDate” on the right so you can repoint this last TO as you’ve done the others.
'''6. Edit Layouts.''' The fields in your appointment table likely don't line up with the fields in our appointments table, so once your new relationships resolve, you'll need to edit the calendar layouts to make sure the correct fields show up in the correct places. Go through each layout in the calendar and double click on each appointment related field to check that it is displaying the correct field.
Just a few notes about some of these layouts:
-> Appointments (Print): Check to make sure the subsummary part here calls ApptDate.
-> Daily View (and others): Whenever you come to a portal of appointments, you'll want to check the portal's sort order in addition to checking the fields it contains. These sort fields get misaligned just as layout fields do during our repointing of the tables.
-> Month View: The month view layout has a number of container fields on top of the appointment fields you'll wish to edit. You'll want to unlock these objects and move them off to the side, making sure you can reposition them in exactly the same location when you're done. Everyone has their own trick for this, but do NOT move these objects backward or forward to accomplish this; it will be very difficult to get the month view to look right again. You might want to try this first on a backup copy of the layout. Once you get the hang of it you'll find you can edit this layout without incident, but take your time the first time out.
'''7. Edit Scripts.''' While you don't need to create any scripts in your appointments file, you do need to edit a few scripts in our calendar that set specific fields in the appointments table. As with layouts, your fields may not line up exactly with the original fields. Check the following scripts in SeedCodeCalendar: these scripts are thoroughly commented to make this process easier. However there are too many references to appointments to reproduce them all here: below you'll see a list of the places to check in each script. Look at your PDFs of the original scripts to make sure you select the correct field:
-> New Appointment: Check the set field statements. They should set your versions of ApptDate. The script should end with a GoToField step going to your appointment’s title field.
-> Edit Appointment - Nudge Date: Check the set fields to make sure we’re manipulating your appointment’s date field.
-> Edit Appointment - Dupe: After we duplicate the record we end the script by going to your ApptTitle field.
-> Print Appointments: You'll just want to check the sort order in this script to make sure it includes ApptDate as we use that in a summary field.
'''8. That's It!'''
