DayBackForFileMaker

Quick Integration: Linking the Calendar

DayBackForFileMaker.QuickIntegration History

Hide minor edits - Show changes to output

October 28, 2016, at 02:05 PM by Dan Wheelon - Fields for Contacts and Projects
Added lines 89-100:
-> '''2.3 Fields for Contacts and Projects.'''

-> If your events are linked to contacts and/or projects, there are two new fields you'll need to add to these tables: DBK_WebViewerSource and DBK_WebViewerData. You can copy these from the SampleContacts table that comes with DayBack. Only the first of these needs to be edited, and in it you'll specify which of your fields is the primary key in the table and which field you want to be shown as the name of the contact when you select them from a list. So edit this section of the calc...

--> id = id ;
--> name = NameFull ;

-> ...to look something like this:

--> id = MyContactID ;
--> name = MyNameLastFirst ;

Changed lines 119-122 from:
-> Note, if your events are linked to contacts, you can do the same thing with the SampleContacts table occurrences you see in the calendar, double click on the table occurrence, select your file (which now appears in the list of data sources) and select the contacts table in your file. Create a relationship between SampleEvents and SampleContacts using the same match fields you use for this kind of relationship in your file.

-> If you're using the projects or our [[gantt charts]] you'll want to do the same thing to our SampleProjects table occurrence and our SamplePhases (if you're using Phases, if you're not just leave it alone). Point these at the relevant tables in your file and make sure that they are connected to SampleEvents by the unique ids in each table.
to:
-> Note, if your events are linked to contacts, you can do the same thing with the SampleContacts table occurrences you see in the calendar. Double click on the table occurrence, select your file (which now appears in the list of data sources) and select the contacts table in your file. Create a relationship between SampleEvents and SampleContacts using the same match fields you use for this kind of relationship in your file.

-> If you're using the projects or our [[gantt charts]] you'll want to do the same thing to our SampleProjects table occurrence and our SamplePhases (if you're not using Phases, you can just leave it alone). Point these at the relevant tables in your file and make sure that they are connected to SampleEvents by the unique ids in each table.
Deleted lines 135-136:

May 06, 2015, at 10:32 PM by 142.4.217.188 -
Changed line 57 from:
--> ''Resource:''' If you copied our resource field you're good to go. If you're using your own you ''may'' want to copy the auto-enter calc from our field as it adds "none" to the resource field if no resource is specified. This means that when you go the resources tab you can see all the events you haven't yet assigned a resource, and then drag then to open resources to schedule them.
to:
--> '''Resource:''' If you copied our resource field you're good to go. If you're using your own you ''may'' want to copy the auto-enter calc from our field as it adds "none" to the resource field if no resource is specified. This means that when you go the resources tab you can see all the events you haven't yet assigned a resource, and then drag then to open resources to schedule them.
May 06, 2015, at 10:31 PM by 142.4.217.188 -
Added lines 56-57:

--> ''Resource:''' If you copied our resource field you're good to go. If you're using your own you ''may'' want to copy the auto-enter calc from our field as it adds "none" to the resource field if no resource is specified. This means that when you go the resources tab you can see all the events you haven't yet assigned a resource, and then drag then to open resources to schedule them.
May 06, 2015, at 10:24 PM by 142.4.217.187 -
Changed lines 33-34 from:
->Open up DayBack.fmp12 and select File / Manage / Database, selecting the "Fields" tab of the "Manage Database" window and select the "SampleEvents" table. You'll copy a few fields from here and add them to your file. If you have FileMaker Advanced this is as simple as copying all the fields prefaced with "DBk_" (for "DayBack")...
to:
->Open up DayBack.fmp12 and select File / Manage / Database, selecting the "Fields" tab of the "Manage Database" window and select the "SampleEvents" table. You'll copy a few fields from here and add them to your file. If you have FileMaker Advanced this is as simple as copying all the fields you don't have and those prefaced with "DBk_" (for "DayBack"). I generally copy these, though you might already have fields to use for status and resource...

--> Status
--> Resource
March 02, 2015, at 08:26 PM by 142.4.217.188 -
Changed line 65 from:
--> '''DBk_WebViewerSource:''' This is the field we use to populate the event details popover when you click on an item in the calendar. If you don't have some of these fields, like "contactID" use can use "DBk_Unused" for now. The date and time fields are required, so are the summary and the "id" which should be the primary key of your table.
to:
--> '''DBk_WebViewerSource:''' This is the field we use to populate the event details popover when you click on an item in the calendar. If you don't have some of these fields, like "contactID" use can use "DBk_Unused" for now. The date and time fields are required, so are the summary and the "id" which should be the primary key of your table. Be sure this field (and none of these newly created fields) is "commented out"--that is, it shouldn't begin with /* and end with */. If it does, delete those characters.
Changed line 3 from:
!! Linking the Calendar to Your Own File
to:
!! Linking DayBack to Your Own File
Changed lines 11-14 from:
Before you get to work, you can watch a short video of the entire integration being done: it takes just 10 minutes...

[[https://www.seedcode.com/contact/ | Watch Video]]
to:
Before you get to work, you can watch a short video of the entire integration being done: it takes just about 10 minutes...

(:youtube WR5fon-M8QU width=500:)
December 05, 2014, at 02:36 AM by 98.203.211.206 -
Deleted lines 55-56:
--> '''DBk_ColorCalc:''' (you can come back to this one later). This field isn't used *in* the calendar but is here in case you want to show the same calendar colors in your FileMaker Layouts. Read more about editing this field later in "[[Event Colors]]".
Added lines 66-67:
--> '''DBk_WebViewerSource:''' This is the field we use to populate the event details popover when you click on an item in the calendar. If you don't have some of these fields, like "contactID" use can use "DBk_Unused" for now. The date and time fields are required, so are the summary and the "id" which should be the primary key of your table.
Changed lines 70-71 from:
--> '''DBk_WebViewerSource:''' This is the field we use to populate the event details popover when you click on an item in the calendar. If you don't have some of these fields, like "contactID" use can use "DBk_Unused" for now. The date and time fields are required, so are the summary and the "id" which should be the primary key of your table.
to:
--> '''DBk_ColorCalc:''' (you can come back to this one later). This field isn't used *in* the calendar but is here in case you want to show the same calendar colors in your FileMaker Layouts. Read more about editing this field later in "[[Event Colors]]".
Deleted line 120:
December 05, 2014, at 02:05 AM by 98.203.211.206 -
Changed lines 13-15 from:
%color=red% >> Need a new video

to:
[[https://www.seedcode.com/contact/ | Watch Video]]

Deleted line 120:
Changed lines 30-88 from:
(:include IntegrationFields:)
to:
'''2. Adding New Fields'''

->You'll copy and paste some fields from our SampleEvents table into your events table: fields the calendar needs in order to run. Some of these are SeedCode's calc fields, and some are just date and time fields calendars expect. If you don't have time fields for your events, or a DateEnd field, for example, you may want to copy and paste those in at the same time. You don't need to use these fields, but the calendar expects them and having them there now makes the integration simpler and lets you take advantage of multi-day events should the scope of your events change. (Note that if you want to enforce that events never have times or never span more than 1 day you can use auto-enter calcs in these newly created fields to force them to be blank.)

->Open up DayBack.fmp12 and select File / Manage / Database, selecting the "Fields" tab of the "Manage Database" window and select the "SampleEvents" table. You'll copy a few fields from here and add them to your file. If you have FileMaker Advanced this is as simple as copying all the fields prefaced with "DBk_" (for "DayBack")...

--> DBk_ColorCalc
--> DBk_EventSummaryCalc
--> DBk_LinkedWithinProject
--> DBk_MilestoneSort
--> DBk_Notified
--> DBk_Repeating_id
--> DBk_TimestampEndCalcNum
--> DBk_TimestampStartCalcNum
--> DBk_Unused
--> DBk_WebViewerEventData
--> DBk_WebViewerSource

-> ...and pasting them into your file. If you don't have FileMaker Advanced, please [[https://www.seedcode.com/contact/ | get in touch]] and we'd be happy to get a copy of your files and perform this step for you.

-> '''2.1 Field Definitions'''

-> You'll now edit the definition for some of the fields you pasted in, selecting ''your'' fields for the DateStart, TimeStart etc. fields used in the calculation's let statements.

-> Here are some notes on each of the fields you'll need to edit. Some of these fields you can come back to later after you see the calendar working with your own data. Remember, for each field you'll edit you need to remove the leading and trailing "comment" tags (the /* and */) from the calc.

--> '''DBk_ColorCalc:''' (you can come back to this one later). This field isn't used *in* the calendar but is here in case you want to show the same calendar colors in your FileMaker Layouts. Read more about editing this field later in "[[Event Colors]]".

--> '''DBk_EventSummaryCalc:''' This field is used to calculate which information about your event shows on the calendar in Day, Week, and Month views. For most users this is a combination of the event title and some other fields about the event. Begin by just replacing "Summary" with the field you'd like to see in the calendar, you can use our DBk_Unused field for the rest of the items for now and then come back to fine tune this once you have the calendar working. So a quick edit of this field might leave the editable part looking like this:

---> s = Summary ; // the title of your event \\
    desc = DBk_Unused ;  // your event's description or notes field \\
    cont = DBk_Unused ; // your contact's name (optional) \\
    ph = DBk_Unused ; // your contact's phone number (optional) \\
    em = DBk_Unused ; // your contact's email (optional)

--> Having done a simple mapping like this, you can come back here later and flesh this out to include all the information you'd like to see in the calendar.

--> '''DBk_TimestampEndCalcNum and DBk_TimestampStartCalcNum:''' Edit this calc to use your own date and time fields. You may not have an end date field in your solution; You may also lack the time fields mentioned in this calc. The simplest thing is to add these fields to your events table: that makes the integration simpler and lets you take advantage of multi-day events should the scope of your events change. (Note that if you want to enforce that events never have times or never span more than 1 day you can use auto-enter calcs in these newly created fields to force them to be blank.)

--> '''DBk_WebViewerSource:''' This is the field we use to populate the event details popover when you click on an item in the calendar. If you don't have some of these fields, like "contactID" use can use "DBk_Unused" for now. The date and time fields are required, so are the summary and the "id" which should be the primary key of your table.

-> '''2.2 Auto-Enter Calcs for Times'''

->Next, add the following Auto-Enter Calculated Value option to the TimeStart field in your events table (you can copy this here or from the definition in SampleEvents):

--> Case ( \\
Self = Time ( 24 ; 0 ; 0 ) ; Time ( 24 ; 0 ; 1 ) ; \\
Self = Time ( 0 ; 0 ; 0 ) ; Time ( 0 ; 0 ; 1 ) ; \\
Self > Time ( 24 ; 0 ; 0 ) ; Self - Time ( 24 ; 0 ; 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.

-> Now add the same Auto-Enter Calculated Value option to the TimeEnd field in your events table. Again, 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 end at midnight.

-> '''2.4 Pause and Save Your Work. '''

-> Really. It's a good habit to get into. =)
Changed lines 34-52 from:
(:include RelationshipGraph:)
to:
-> Return to DayBack.fmp12 and again select File / Manage / Database, selecting the "Relationships" tab of the Manage Database window.

-> Double click on the "SampleEvents" table occurrence in the graph and click in the pop-up list next to "Data Source
:"-- select "Add FileMaker Data Source" from the list of options and, in the next window, select your file.

-> You'll now see all the tables in your file: select the one which has the records you'd like to see in the calendar. Change the name at the bottom of the "Specify Table" window back to "SampleEvents" (you can change it back later
) and click "OK". You've now "pointed" the calendar's events table at the events table in your file: eventually you'll be able to delete the SampleEvents table in DayBack.fmp12, but don't do it yet as you'll need it in the next step.

-> Note that you'll get an error if you try to view the calendar at this point. That's normal. It will throw errors until we're done with step 4.

-> (I'd move on to step 4 now: once the calendar is showing your events you can come back here and wire up information about the contacts and projects related to your events.)

->  '''3.1 Contacts and Projects'''

-> Note, if your events are linked to contacts, you can do the same thing with the SampleContacts table occurrences you see in the calendar, double click on the table occurrence, select your file (which now appears in the list of data sources) and select the contacts table in your file. Create a relationship between SampleEvents and SampleContacts using the same match fields you use for this kind of relationship in your file.

-> If you're using the projects or our [[gantt charts]] you'll want to do the same thing to our SampleProjects table occurrence and our SamplePhases (if you're using Phases, if you're not just leave it alone). Point these at the relevant tables in your file and make sure that they are connected to SampleEvents by the unique ids in each table.

-> ''If you don't have a contacts or projects table, and wish you did, you may want to pause this integration and take a look at %newwin% [[https://www.seedcode.com/complete | SeedCode Complete]], which already has our calendar linked to a rich contacts and project management system.''

-> If you deleted the sample Contact, Project, or Phase table occurrences from your graph as we do in our video, be sure to visit the script "Load Source Settings at Startup --- Describe Your Sources Here ---". There you'll see two variables declared with the name of these tables. Replace those table names with "" (blank) or the calendar will ask where they are when you run the calendar's upon opening script.
Changed line 26 from:
-> Using our SampleEvents table is also a great strategy if you have a record in your file (like a job or workorder) with lots of dates associated with with it (start date, due date, inspection date, etc.). In that case our SampleEvents table can be a "child" of your job or workorder and these dates become records in SampleEvents instead of fields in your parent record. This means you can have as many dates as you'd like related to that parent record and reporting on those dates gets much simpler: "find me everything Jim is doing in May" is a simple find in this kind of related events table, whereas it's quite hard to do if you have five different date fields in your parent record. If you have questions about this approach, please [[https://www.seedcode.com/contact/ | get in touch]], we can help you decide if relating our SampleEvents table to your parent record is a good approach. It's certainly one of the simplest integrations you can do.
to:
-> Using our SampleEvents table is also a great strategy if you have a record in your file (like a job or workorder) with lots of dates associated with it (start date, due date, inspection date, etc.). In that case our SampleEvents table can be a "child" of your job or workorder and these dates become records in SampleEvents instead of fields in your parent record. This means you can have as many dates as you'd like related to that parent record and reporting on those dates gets much simpler: "find me everything Jim is doing in May" is a simple find in this kind of related events table, whereas it's quite hard to do if you have five different date fields in your parent record. If you have questions about this approach, please [[https://www.seedcode.com/contact/ | get in touch]], we can help you decide if relating our SampleEvents table to your parent record is a good approach. It's certainly one of the simplest integrations you can do.
November 21, 2014, at 06:24 AM by 98.203.211.206 -
Changed lines 34-53 from:
-> Return to DayBack.fmp12 and again select File / Manage / Database, selecting the "Relationships" tab of the Manage Database window.

-> Double click on the "SampleEvents" table occurrence in the graph and click in the pop-up list next to "Data Source
:"-- select "Add FileMaker Data Source" from the list of options and, in the next window, select your file.

-> You'll now see all the tables in your file: select the one which has the records you'd like to see in the calendar. Change the name at the bottom of the "Specify Table" window back to "SampleEvents" (you can change it back later
) and click "OK". You've now "pointed" the calendar's events table at the events table in your file: eventually you'll be able to delete the SampleEvents table in DayBack.fmp12, but don't do it yet as you'll need it in the next step.

-> Note that you'll get an error if you try to view the calendar at this point. That's normal. It will throw errors until we're done with step 4.

-> (I'd move on to step 4 now: once the calendar is showing your events you can come back here and wire up information about the contacts and projects related to your events.)

->  '''3.1 Contacts and Projects'''

-> Note, if your events are linked to contacts, you can do the same thing with the SampleContacts table occurrences you see in the calendar, double click on the table occurrence, select your file (which now appears in the list of data sources) and select the contacts table in your file. Create a relationship between SampleEvents and SampleContacts using the same match fields you use for this kind of relationship in your file.

-> If you're using the projects or our [[gantt charts]] you'll want to do the same thing to our SampleProjects table occurrence and our SamplePhases (if you're using Phases, if you're not just leave it alone). Point these at the relevant tables in your file and make sure that they are connected to SampleEvents by the unique ids in each table.

-> ''If you don't have a contacts or projects table, and wish you did, you may want to pause this integration and take a look at %newwin% [[https://www.seedcode.com/complete | SeedCode Complete]], which already has our calendar linked to a rich contacts and project management system.''

-> If you deleted the sample Contact, Project, or Phase table occurrences from your graph as we do in our video, be sure to visit the script "Load Source Settings at Startup --- Describe Your Sources Here ---". There you'll see two variables declared with the name of these tables. Replace those table names with "" (blank) or the calendar will ask where they are when you run the calendar's upon opening script.

to:
(:include RelationshipGraph:)
Deleted line 44:
Added lines 11-12:
Before you get to work, you can watch a short video of the entire integration being done: it takes just 10 minutes...
Deleted line 14:
Before you get to work, you can watch a short video of the entire integration being done: it takes just 10 minutes... %newwin% [[https://www.youtube.com/watch?v=UQAR7MVcicc | '''Quick Integration Video''']].
Changed line 47 from:
-> If you're using the projects or our [[gantt chart]] you'll want to do the same thing to our SampleProjects table occurrence and our SamplePhases (if you're using Phases, if you're not just leave it alone). Point these at the relevant tables in your file and make sure that they are connected to SampleEvents by the unique ids in each table.
to:
-> If you're using the projects or our [[gantt charts]] you'll want to do the same thing to our SampleProjects table occurrence and our SamplePhases (if you're using Phases, if you're not just leave it alone). Point these at the relevant tables in your file and make sure that they are connected to SampleEvents by the unique ids in each table.
Changed lines 23-25 from:
-> These instructions assume you already have a table whose records you want to see in the calendar. If you don't, you can just paste our SampleEvents table into your file and skip step 2 below.
to:
-> These instructions assume you already have a table whose records you want to see in the calendar. If you don't, you can just paste our SampleEvents table into your file and skip to step 3 below.

-> Using our SampleEvents table is also a great strategy if you have a record in your file (like a job or workorder) with lots of dates associated with with it (start date, due date, inspection date, etc.). In that case our SampleEvents table can be a "child" of your job or workorder and these dates become records in SampleEvents instead of fields in your parent record. This means you can have as many dates as you'd like related to that parent record and reporting on those dates gets much simpler: "find me everything Jim is doing in May" is a simple find in this kind of related events table, whereas it's quite hard to do if you have five different date fields in your parent record. If you have questions about this approach, please [[https://www.seedcode.com/contact/ | get in touch]], we can help you decide if relating our SampleEvents table to your parent record is a good approach. It's certainly one of the simplest integrations you can do.
November 14, 2014, at 04:33 PM by 98.203.211.206 -
Changed lines 53-62 from:
-> Navigate to the Source No 1 layout in DayBack.fmp12 and follow the instructions on the layout to map the fields there to the relevant fields in your events table.

-> A couple tips on field mapping
:

--> Events with just a single date should have a start date: if your event has just an end date the calendar will fail. The same goes for times: if there is only one time, make it the start time.

--> Don't use calcs for things like the dates, times, or resources. The calendar wants to edit these values when you drag items around, and it can't edit calcs. Use auto-enter calculations instead if you must.

-> Once you've mapped these fields you can run the script "Upon Opening" in DayBack.fmp12 and if you haven't made any mistakes you should see your events in the calendar! If you're seeing errors you might skim through the steps above again to see if you missed anything, or checkout our [[troubleshooting]] tips. And you can always [[https://www.seedcode.com/contact/ | get in touch]] if those troubleshooting steps don't work for you: we're here to help.

to:
(:include FieldMapping:)
Deleted line 59:
Added lines 1-2:
(:title Quick Integration: Linking the Calendar:)
Changed lines 63-85 from:
'''Going Further'''

%color=red% >> The following us uncorrected from FM12. Consider... Color Coding, adding Actions, Linking Contacts and Projects, List View, Popover-in-FileMaker, in addition to what follows.

Now that you've got the calendar showing your own records (congratulations!
) you may want to come back and flesh out a few of the things we glossed over when setting this up.

Eventually you'll want to come back to the Event Detail layout from step 5 and get that just right, and consider [[ Event Colors | color-coding events]] if that makes sense in your file. You'll also want to read through the script "Load Calendar Settings - On Startup --- Edit Configuration Here ---" making changes as necessary as this lets you change a number of the calendar's default settings.

-> '''� Color Coding.''' Click on the filters tab of the calendar and edit the statuses listed there to match the values in the field you mapped to "status" on your Source No 1 layout. This is the field we'll use for color coding. Click on the gear icon beside a status to change it's name or color. Click on the "+" icon to add new ones. Read more about colors [[event colors | here]].

-> '''� Filtering the Calendar''' If you need to set up more filters or point the existing ones at your own fields, then check out our notes on [[filters]].

-> '''� Showing Additional Fields''' - going back to the summary calc

-> '''� Linking Contacts & Projects to Events''' - new page on contacts and projects

-> '''� Resources.''' Take a look at the field you mapped to Resource and edit the Resources value list in the calendar so it matches the contents of that field: we used "location" as the resource in our video and changed the "Resources" value list in the calendar to point to an existing value list in the Meetings file. You may want to do something similar. More on [[resources]].

-> '''� Renaming Sample Events.''' If you'd like to change the name of "sample events" in the relationships tab, you can do that now, just read about this script you'll need to edit afterwards: [[renaming tables]].

-> '''� General Settings.''' You'll also want to read through the script "Load Calendar Settings - On Startup --- Edit Configuration Here ---" making changes as necessary: this lets you change a number of the calendar's default settings and is a good read as it lets you know what's already set up for you to change.

-> '''� Additional Tables (Sources).'' And don't forget you can show records from additional tables, not just the one your named Sample Events. We call each of these events tables "sources" and any table that has dates in it can be a source. Learn more by reading about [[multiple sources]].
to:
!! Going Further

(:include GoingFurther:
)
Changed lines 75-76 from:
-> '''� Reaming Sample Events.''' If you'd like to change the name of "sample events" in the relationships tab, you can do that now, just read about this script you'll need to edit afterwards: [[renaming tables]].
to:
-> '''� Showing Additional Fields''' - going back to the summary calc

-> '''� Linking Contacts & Projects to Events''' - new page on contacts and projects

Added lines 81-82:
-> '''� Renaming Sample Events.''' If you'd like to change the name of "sample events" in the relationships tab, you can do that now, just read about this script you'll need to edit afterwards: [[renaming tables]].
Changed lines 85-87 from:
In any event, think about the kind of records you've mapped to Source No 1 and Event Detail, and if you think you might need an action or events table, you hopefully now have the confidence to begin adding one.

And don't forget you can have more than one calendar at a time--more than one "source"--and have some from fields in a contact's record and other calendars from events tables
. Learn more by reading about [[multiple sources]].
to:
-> '''� Additional Tables (Sources).'' And don't forget you can show records from additional tables, not just the one your named Sample Events. We call each of these events tables "sources" and any table that has dates in it can be a source. Learn more by reading about [[multiple sources]].
Changed lines 73-74 from:
-> '''� Filtering the Calendar''' If you need to set up filters on your own fields, then check out our section on [[filters]].
to:
-> '''� Filtering the Calendar''' If you need to set up more filters or point the existing ones at your own fields, then check out our notes on [[filters]].
Changed lines 77-83 from:
-> '''� Resources''' Take a look at the field you mapped to Resource and edit the Resources value list in the calendar so it matches the contents of that field: we used "location" as the resource in our video and changed the "Resources" value list in the calendar to point to an existing value list in the Meetings file. You may want to do something similar. More on [[resources]].





The "new" button on the calendar might not make sense in some cases: for example you may link to the "next contact date
" of a contact record. In that case "new" would make a new contact. Maybe that is what you want, but likely you'd want to create a new "action" for a contact and so the contacts file in such example would have been better served by adding an actions or events table to it and linking that table to our contact: pasting in the Sample Events table from SeedCode Calendar would have been a way to start that. 
to:
-> '''� Resources.''' Take a look at the field you mapped to Resource and edit the Resources value list in the calendar so it matches the contents of that field: we used "location" as the resource in our video and changed the "Resources" value list in the calendar to point to an existing value list in the Meetings file. You may want to do something similar. More on [[resources]].

-> '''� General Settings.''' You'll also want to read through the script "Load Calendar Settings - On Startup --- Edit Configuration Here ---" making changes as necessary: this lets you change a number of the calendar's default settings and is a good read as it lets you know what's already set up for you to change.
Added lines 71-74:
-> '''� Color Coding.''' Click on the filters tab of the calendar and edit the statuses listed there to match the values in the field you mapped to "status" on your Source No 1 layout. This is the field we'll use for color coding. Click on the gear icon beside a status to change it's name or color. Click on the "+" icon to add new ones. Read more about colors [[event colors | here]].

-> '''� Filtering the Calendar''' If you need to set up filters on your own fields, then check out our section on [[filters]].

Changed lines 79-81 from:
-> '''� Filtering the Calendar''' If you need to set up filters on your own fields, then check out our section on [[filters]].

Similarly, we changed some of the event colors to match the values in the field we mapped on the "Color" tab of Source No 1. Read more about colors [[event colors | here]].
to:


Changed lines 71-76 from:
* If you'd like to change the name of "sample events" in the relationships tab, you can do that now, just read about this script you'll need to edit afterwards: [[renaming tables]].

* Take a look at the field you mapped to Resource and edit
the Resources value list in the calendar so it matches the contents of that field: we used "location" as the resource in our video and changed the "Resources" value list in the calendar to point to an existing value list in the Meetings file. You may want to do something similar. More on [[resources]].

If
you need to set up filters on your own fields, then check out our section on [[filters]].
to:
-> '''� Reaming Sample Events.''' If you'd like to change the name of "sample events" in the relationships tab, you can do that now, just read about this script you'll need to edit afterwards: [[renaming tables]].

-> '''� Resources''' Take a look at
the field you mapped to Resource and edit the Resources value list in the calendar so it matches the contents of that field: we used "location" as the resource in our video and changed the "Resources" value list in the calendar to point to an existing value list in the Meetings file. You may want to do something similar. More on [[resources]].

-> '''� Filtering the Calendar'''
If you need to set up filters on your own fields, then check out our section on [[filters]].
Deleted line 83:
Added lines 67-68:
Now that you've got the calendar showing your own records (congratulations!) you may want to come back and flesh out a few of the things we glossed over when setting this up.
Changed lines 71-73 from:
If you'd like to change the name of "sample events" in the relationships tab, you can do that now, just read about this script you'll need to edit afterwards: [[renaming tables]].

Take a look at the field you mapped to Resource and edit the Resources value list in the calendar so it matches the contents of that field: we used "location" as the resource in our video and changed the "Resources" value list in the calendar to point to an existing value list in the Meetings file. You may want to do something similar. More on [[resources]].
to:
* If you'd like to change the name of "sample events" in the relationships tab, you can do that now, just read about this script you'll need to edit afterwards: [[renaming tables]].

* Take a look at the field you mapped to Resource and edit the Resources value list in the calendar so it matches the contents of that field: we used "location" as the resource in our video and changed the "Resources" value list in the calendar to point to an existing value list in the Meetings file. You may want to do something similar. More on [[resources]].
Deleted lines 0-1:
(:title Foo Or Longer thnknasfnsad sgsfsa:)
Added lines 1-2:
(:title Foo Or Longer thnknasfnsad sgsfsa:)
Changed lines 25-83 from:
'''2. Adding New Fields'''

->You'll copy and paste some fields from our SampleEvents table into your events table: fields the calendar needs in order to run. Some of these are SeedCode's calc fields, and some are just date and time fields calendars expect. If you don't have time fields for your events, or a DateEnd field, for example, you may want to copy and paste those in at the same time. You don't need to use these fields, but the calendar expects them and having them there now makes the integration simpler and lets you take advantage of multi-day events should the scope of your events change. (Note that if you want to enforce that events never have times or never span more than 1 day you can use auto-enter calcs in these newly created fields to force them to be blank.)

->Open up DayBack.fmp12 and select File / Manage / Database, selecting the "Fields" tab of the "Manage Database" window and select the "SampleEvents" table. You'll copy a few fields from here and add them to your file. If you have FileMaker Advanced this is as simple as copying all the fields prefaced with "DBk_" (for "DayBack")...

--> DBk_ColorCalc
--> DBk_EventSummaryCalc
--> DBk_LinkedWithinProject
--> DBk_MilestoneSort
--> DBk_Notified
--> DBk_Repeating_id
--> DBk_TimestampEndCalcNum
--> DBk_TimestampStartCalcNum
--> DBk_Unused
--> DBk_WebViewerEventData
--> DBk_WebViewerSource

-> ...and pasting them into your file. If you don't have FileMaker Advanced, please [[https://www.seedcode.com/contact/ | get in touch]] and we'd be happy to get a copy of your files and perform this step for you.

-> '''2.1 Field Definitions'''

-> You'll now edit the definition for some of the fields you pasted in, selecting ''your'' fields for the DateStart, TimeStart etc. fields used in the calculation's let statements.

-> Here are some notes on each of the fields you'll need to edit. Some of these fields you can come back to later after you see the calendar working with your own data. Remember, for each field you'll edit you need to remove the leading and trailing "comment" tags (the /* and */) from the calc.

--> '''DBk_ColorCalc:''' (you can come back to this one later). This field isn't used *in* the calendar but is here in case you want to show the same calendar colors in your FileMaker Layouts. Read more about editing this field later in "[[Event Colors]]".

--> '''DBk_EventSummaryCalc:''' This field is used to calculate which information about your event shows on the calendar in Day, Week, and Month views. For most users this is a combination of the event title and some other fields about the event. Begin by just replacing "Summary" with the field you'd like to see in the calendar, you can use our DBk_Unused field for the rest of the items for now and then come back to fine tune this once you have the calendar working. So a quick edit of this field might leave the editable part looking like this:

---> s = Summary ; // the title of your event \\
    desc = DBk_Unused ;  // your event's description or notes field \\
    cont = DBk_Unused ; // your contact's name (optional) \\
    ph = DBk_Unused ; // your contact's phone number (optional) \\
    em = DBk_Unused ; // your contact's email (optional)

--> Having done a simple mapping like this, you can come back here later and try mapping the summary to something more interesting to create a [[MultiLineEvents | multi-line]] event display.

--> '''DBk_TimestampEndCalcNum and DBk_TimestampStartCalcNum:''' Edit this calc to use your own date and time fields. You may not have an end date field in your solution; You may also lack the time fields mentioned in this calc. The simplest thing is to add these fields to your events table: that makes the integration simpler and lets you take advantage of multi-day events should the scope of your events change. (Note that if you want to enforce that events never have times or never span more than 1 day you can use auto-enter calcs in these newly created fields to force them to be blank.)

--> '''DBk_WebViewerSource:''' This is the filed we use to populate the event details popover when you click on an item in the calendar. If you don't have some of these fields, like "contactID" use can use "DBk_NotUsed" for now. The date and time fields are required, so are the summary and the "id" which should be the primary key of your table.

-> '''2.2 Auto-Enter Calcs for Times'''

->Next, add the following Auto-Enter Calculated Value option to the TimeStart field in your events table (you can copy this here or from the definition in SampleEvents):

--> Case ( \\
Self = Time ( 24 ; 0 ; 0 ) ; Time ( 24 ; 0 ; 1 ) ; \\
Self = Time ( 0 ; 0 ; 0 ) ; Time ( 0 ; 0 ; 1 ) ; \\
Self > Time ( 24 ; 0 ; 0 ) ; Self - Time ( 24 ; 0 ; 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.

-> Now add the same Auto-Enter Calculated Value option to the TimeEnd field in your events table. Again, 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 end at midnight.

-> '''2.4 Pause and Save Your Work. '''

-> Really. It's a good habit to get into. =)
to:
(:include IntegrationFields:)
Changed line 83 from:
--> =)
to:
-> Really. It's a good habit to get into. =)
Changed lines 107-108 from:
'''4. Layouts Part 1: Field Mapping'''
to:
'''4. Field Mapping Layout'''
Changed lines 117-134 from:
-> Once you've mapped these fields you can run the script "Upon Opening" in DayBack.fmp12 and if you haven't made any mistakes you should see your events in the calendar! If you're seeing errors you might skim through the steps above again to see if you missed anything, or checkout our [[troubleshooting]] tips.

'''5. Layouts Part 2: Event Details'''

-> Move to the Event Details layout in SeedCodeCalendar.fmp12 and edit this layout as
you see fit, pointing the current fields to ''your'' own fields. Just be sure to keep the following 3 objects: the "repeat" button, the "show repts..." button below it, and the large "close..." button at the bottom of the screen. You can come back and edit this layout later, for now, just get the Summary, Date, and Time fields lined up with the relevant fields in your events table.

-> Down the road you can come back to this and add buttons to [[ JumpToMyEvent | jump to the related record in your file ]], or event to your event's [[ JumpToMyContact | related contact ]].

-> If you're going to be using Web Direct you'll want to edit that version of Event Details: in Web Direct we show the event details in a popover. Learn how to point these popovers at your fields here: [[Event Popovers | Formatting Event Popovers]].

'''6. Event colors in list view and mini windows'''.

-> This step is optional, but if you want to show an event's color "on" the event record in list view and in the Event Details mini window, follow these [[ SeparationColors | instructions ]].

'''7. That's it'''.

-> Refresh the calendar and you'll see your events. Pretty simple
.
to:
-> Once you've mapped these fields you can run the script "Upon Opening" in DayBack.fmp12 and if you haven't made any mistakes you should see your events in the calendar! If you're seeing errors you might skim through the steps above again to see if you missed anything, or checkout our [[troubleshooting]] tips. And you can always [[https://www.seedcode.com/contact/ | get in touch]] if those troubleshooting steps don't work for you: we're here to help.
Added lines 122-123:

%color=red% >> The following us uncorrected from FM12. Consider... Color Coding, adding Actions, Linking Contacts and Projects, List View, Popover-in-FileMaker, in addition to what follows.
Changed line 117 from:
-> Once you've mapped these fields you can run the script "Upon Opening" in DayBack.fmp12 and if you haven't made any mistakes you should see your events in the calendar!
to:
-> Once you've mapped these fields you can run the script "Upon Opening" in DayBack.fmp12 and if you haven't made any mistakes you should see your events in the calendar! If you're seeing errors you might skim through the steps above again to see if you missed anything, or checkout our [[troubleshooting]] tips.
Added lines 93-94:
-> Note that you'll get an error if you try to view the calendar at this point. That's normal. It will throw errors until we're done with step 4.
Added lines 116-117:

-> Once you've mapped these fields you can run the script "Upon Opening" in DayBack.fmp12 and if you haven't made any mistakes you should see your events in the calendar!
Added lines 61-62:
--> Having done a simple mapping like this, you can come back here later and try mapping the summary to something more interesting to create a [[MultiLineEvents | multi-line]] event display.
Changed lines 67-68 from:
-> '''2.2''' Next, add the following Auto-Enter Calculated Value option to the TimeStart field in your events table (you can copy this here or from the definition in SampleEvents):
to:
-> '''2.2 Auto-Enter Calcs for Times'''

->
Next, add the following Auto-Enter Calculated Value option to the TimeStart field in your events table (you can copy this here or from the definition in SampleEvents):
Changed lines 79-82 from:
-> '''2.3''' Now add the same Auto-Enter Calculated Value option to the TimeEnd field in your events table. Again, 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 end at midnight.

-> '''2.4''' Pause and save your work.
to:
-> Now add the same Auto-Enter Calculated Value option to the TimeEnd field in your events table. Again, 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 end at midnight.

-> '''2.4 Pause and Save Your Work. '''

--> =)

Changed lines 91-92 from:
-> You'll now see all the tables in your file: select the one which has the records you'd like to see in the calendar. Change the name at the bottom of the "Specify Table" window back to "SampleEvents" (you can change it back later) and click "OK". You've now "pointed" the calendar's events table at the events table in your file: eventually you'll be able to delete the SampleEvents table in SeedCodeCalendar.fmp12, but don't do it yet as you'll need it in the next step.
to:
-> You'll now see all the tables in your file: select the one which has the records you'd like to see in the calendar. Change the name at the bottom of the "Specify Table" window back to "SampleEvents" (you can change it back later) and click "OK". You've now "pointed" the calendar's events table at the events table in your file: eventually you'll be able to delete the SampleEvents table in DayBack.fmp12, but don't do it yet as you'll need it in the next step.

-> (I'd move on to step 4 now: once the calendar is showing your events you can come back here and wire up information about the contacts and projects related to your events.)

->  '''3.1 Contacts and Projects'''

Changed lines 99-100 from:
-> If you're using the [[gantt chart]] you'll want to do the same thing to our SampleProjects table occurrence and our SamplePhases (if you're using Phases, if you're not just leave it alone). Point these at the relevant tables in your file and make sure that they are connected to SampleEvents by the unique ids in each table.
to:
-> If you're using the projects or our [[gantt chart]] you'll want to do the same thing to our SampleProjects table occurrence and our SamplePhases (if you're using Phases, if you're not just leave it alone). Point these at the relevant tables in your file and make sure that they are connected to SampleEvents by the unique ids in each table.
Changed line 107 from:
-> Navigate to the Source No 1 layout in SeedCodeCalendar.fmp12 and follow the instructions on the layout to map the fields there to the relevant fields in your events 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:
-> Navigate to the Source No 1 layout in DayBack.fmp12 and follow the instructions on the layout to map the fields there to the relevant fields in your events table.
Added lines 27-28:
->You'll copy and paste some fields from our SampleEvents table into your events table: fields the calendar needs in order to run. Some of these are SeedCode's calc fields, and some are just date and time fields calendars expect. If you don't have time fields for your events, or a DateEnd field, for example, you may want to copy and paste those in at the same time. You don't need to use these fields, but the calendar expects them and having them there now makes the integration simpler and lets you take advantage of multi-day events should the scope of your events change. (Note that if you want to enforce that events never have times or never span more than 1 day you can use auto-enter calcs in these newly created fields to force them to be blank.)
Deleted line 35:
--> DBk_NotUsed
Added line 39:
--> DBk_Unused
Deleted lines 48-49:
-> If you create new fields, make sure the date fields are of the type "date" and the time fields are "time".
Changed lines 53-54 from:
--> '''DBk_EventSummaryCalc:''' This field is used to calculate which information about your event shows on the calendar in Day, Week, and Month views. For most users this is a combination of the event title and some other fields about the event. Begin by just replacing "Summary" with the field you'd like to see in the calendar, you can use our DBk_NotUsed field for the rest of the items for now and then come back to fine tune this once you have the calendar working. So a quick edit of this field might leave the editable part looking like this:
to:
--> '''DBk_EventSummaryCalc:''' This field is used to calculate which information about your event shows on the calendar in Day, Week, and Month views. For most users this is a combination of the event title and some other fields about the event. Begin by just replacing "Summary" with the field you'd like to see in the calendar, you can use our DBk_Unused field for the rest of the items for now and then come back to fine tune this once you have the calendar working. So a quick edit of this field might leave the editable part looking like this:
Changed lines 56-60 from:
   desc = DBk_NotUsed ;  // your event's description or notes field \\
    cont = DBk_NotUsed ; // your contact's name (optional) \\
    ph = DBk_NotUsed ; // your contact's phone number (optional) \\
    em = DBk_NotUsed ; // your contact's email (optional)
to:
   desc = DBk_Unused ;  // your event's description or notes field \\
    cont = DBk_Unused ; // your contact's name (optional) \\
    ph = DBk_Unused ; // your contact's phone number (optional) \\
    em = DBk_Unused ; // your contact's email (optional)
Changed lines 63-64 from:
--> '''DBk_WebViewerSource:''' this
to:
--> '''DBk_WebViewerSource:''' This is the filed we use to populate the event details popover when you click on an item in the calendar. If you don't have some of these fields, like "contactID" use can use "DBk_NotUsed" for now. The date and time fields are required, so are the summary and the "id" which should be the primary key of your table.
Added lines 77-78:
-> '''2.4''' Pause and save your work.
Changed line 81 from:
-> Return to SeedCodeCalendar.fmp12 and again select File / Manage / Database, selecting the "Relationships" tab of the Manage Database window.
to:
-> Return to DayBack.fmp12 and again select File / Manage / Database, selecting the "Relationships" tab of the Manage Database window.
Added lines 62-63:

--> '''DBk_WebViewerSource:''' this
Deleted lines 46-47:
-> It may be that you don't have an end date field in your solution. You may also lack the time fields mentioned in the next steps (start and end times). The simplest thing is to add these fields to your events table: that makes the integration simpler and lets you take advantage of multi-day events should the scope of your events change. (Note that if you want to enforce that events never have times or never span more than 1 day you can use auto-enter calcs in these newly created fields to force them to be blank.)
Changed lines 51-54 from:
--> DBk_ColorCalc: (you can come back to this one later). This field isn't used *in* the calendar but is here in case you want to show the same calendar colors in your FileMaker Layouts. Read more about editing this field later in "[[Event Colors]]".

--> DBk_EventSummaryCalc: This field is used to calculate which information about your event shows on the calendar in Day, Week, and Month views. For most users this is a combination of the event title and some other fields about the event. Begin by just replacing "Summary" with the field you'd like to see in the calendar, you can use our DBk_NotUsed field for the rest of the items for now and then come back to fine tune this once you have the calendar working. So a quick edit of this field might leave the editable part looking like this:
to:
--> '''DBk_ColorCalc:''' (you can come back to this one later). This field isn't used *in* the calendar but is here in case you want to show the same calendar colors in your FileMaker Layouts. Read more about editing this field later in "[[Event Colors]]".

--> '''DBk_EventSummaryCalc:''' This field is used to calculate which information about your event shows on the calendar in Day, Week, and Month views. For most users this is a combination of the event title and some other fields about the event. Begin by just replacing "Summary" with the field you'd like to see in the calendar, you can use our DBk_NotUsed field for the rest of the items for now and then come back to fine tune this once you have the calendar working. So a quick edit of this field might leave the editable part looking like this:
Added lines 60-61:

--> '''DBk_TimestampEndCalcNum and DBk_TimestampStartCalcNum:''' Edit this calc to use your own date and time fields. You may not have an end date field in your solution; You may also lack the time fields mentioned in this calc. The simplest thing is to add these fields to your events table: that makes the integration simpler and lets you take advantage of multi-day events should the scope of your events change. (Note that if you want to enforce that events never have times or never span more than 1 day you can use auto-enter calcs in these newly created fields to force them to be blank.)
Changed lines 57-63 from:
---> s = Summary ; // the title of your event\
    desc = DBk_NotUsed ;  // your event's description or notes field\
    cont = DBk_NotUsed ; // your contact's name (optional)\
    ph = DBk_NotUsed ; // your contact's phone number (optional)\
    em = DBk_NotUsed ; // your contact's email (optional)\

to:
---> s = Summary ; // the title of your event \\
    desc = DBk_NotUsed ;  // your event's description or notes field \\
    cont = DBk_NotUsed ; // your contact's name (optional) \\
    ph = DBk_NotUsed ; // your contact's phone number (optional) \\
    em = DBk_NotUsed ; // your contact's email (optional)
Changed lines 45-46 from:
-> You'll now edit the definition for some of the fields you pasted in, removing the leading and trailing "comment" tags (the /* and */), and selecting ''your'' fields for the DateStart, TimeStart etc. fields used in the calculation's let statements.
to:
-> You'll now edit the definition for some of the fields you pasted in, selecting ''your'' fields for the DateStart, TimeStart etc. fields used in the calculation's let statements.
Changed lines 51-53 from:
-> Here are some notes on each of the fields you'll need to edit...

--> Field Name:
to:
-> Here are some notes on each of the fields you'll need to edit. Some of these fields you can come back to later after you see the calendar working with your own data. Remember, for each field you'll edit you need to remove the leading and trailing "comment" tags (the /* and */) from the calc.

--> DBk_ColorCalc: (you can come back to this one later). This field isn't used *in* the calendar but is here in case you want to show the same calendar colors in your FileMaker Layouts. Read more about editing this field later in "[[Event Colors]]".

--> DBk_EventSummaryCalc: This field is used to calculate which information about your event shows on the calendar in Day, Week, and Month views. For most users this is a combination of the event title and some other fields about the event. Begin by just replacing "Summary" with the field you'd like to see in the calendar, you can use our DBk_NotUsed field for the rest of the items for now and then come back to fine tune this once you have the calendar working. So a quick edit of this field might leave the editable part looking like this:

---> s = Summary ; // the title of your event\
    desc = DBk_NotUsed ;  // your event's description or notes field\
    cont = DBk_NotUsed ; // your contact's name (optional)\
    ph = DBk_NotUsed ; // your contact's phone number (optional)\
    em = DBk_NotUsed ; // your contact's email (optional)\

Changed lines 29-39 from:
--> z_LinkedWithinProject
--> z_MilestoneSort
--> z_Notified
--> z_Repeating_id
--> z_sc_ColorCalc
--> zscEventSummaryCalc
--> zscNotUsed
--> zscTimestampEndCalcNum
--> zscTimestampStartCalcNum
--> zscWebViewerEventData
--> zscWebViewerSource
to:
--> DBk_ColorCalc
--> DBk_EventSummaryCalc
--> DBk_LinkedWithinProject
--> DBk_MilestoneSort
--> DBk_Notified
--> DBk_NotUsed
--> DBk_Repeating_id
--> DBk_TimestampEndCalcNum
--> DBk_TimestampStartCalcNum
--> DBk_WebViewerEventData
--> DBk_WebViewerSource
Changed lines 15-16 from:
'''1. Getting ready.'''
to:
'''1. Getting Ready'''
Changed lines 19-20 from:
-> Now move SeedCodeCalendar.fmp12 into the same folder as the file you'll be working with. If you'd like to rename the calendar file, do that now as well.
to:
-> Now move DayBack.fmp12 into the same folder as the file you'll be working with. If you'd like to rename the calendar file, do that now as well.
Changed lines 23-28 from:
-> You may also have more than one table (or more than one date field in a table) that you want to see in the calendar. Don't worry about that for now: get one table/field up and running and then you can come back and configure [[MultipleSources | additional event sources]].

'''2. Field Definitions.'''

->Open up SeedCodeCalendar.fmp12 and select File / Manage / Database, selecting the "Fields" tab of the "Manage Database" window and select the "SampleEvents" table. You'll copy a couple fields from here and add them to your file. If you have FileMaker Advanced this is as simple as copying these two fields...
to:
-> You may also have more than one table (or more than one date field in a table) that you want to see in the calendar. Don't worry about that for now: get one table/field up and running and then you can come back and configure [[MultipleSources | additional data sources]].

'''2. Adding New Fields'''

->Open up DayBack.fmp12 and select File / Manage / Database, selecting the "Fields" tab of the "Manage Database" window and select the "SampleEvents" table. You'll copy a few fields from here and add them to your file. If you have FileMaker Advanced this is as simple as copying all the fields prefaced with "DBk_" (for "DayBack")...

--> z_LinkedWithinProject
--> z_MilestoneSort
--> z_Notified
--> z_Repeating_id
--> z_sc_ColorCalc
--> zscEventSummaryCalc
--> zscNotUsed
--> zscTimestampEndCalcNum
Changed lines 38-41 from:
--> zscTimestampEndCalcNum

-> ...and pasting them into your file. Once they are there, edit the definition for each, removing the leading and trailing "comment" tags (the /* and */), and selecting ''your'' fields for the DateStart, TimeStart etc. fields used in the calculation's let statements.
to:
--> zscWebViewerEventData
--> zscWebViewerSource

->
...and pasting them into your file. If you don't have FileMaker Advanced, please [[https://www.seedcode.com/contact/ | get in touch]] and we'd be happy to get a copy of your files and perform this step for you.

-> '''2.1 Field Definitions'''

-> You'll now edit the definition for some of the fields you pasted in
, removing the leading and trailing "comment" tags (the /* and */), and selecting ''your'' fields for the DateStart, TimeStart etc. fields used in the calculation's let statements.
Changed lines 51-52 from:
-> If you don't have FileMaker advanced, copy the definitions of these fields, carefully recreating them in your file. Make sure both calcs are of the type "number".
to:
-> Here are some notes on each of the fields you'll need to edit...

--> Field Name:

Deleted lines 65-71:

-> '''2.4''' If you plan to use the calendar's gantt charts, repeating events, or email notifications add a few more fields from our SampleEvents to yours:

--> z_LinkedWithinProject
--> z_MilestoneSort
--> z_Notified
--> z_Repeating_id
Changed line 9 from:
>> %color=red% Need a new video %
to:
%color=red% >> Need a new video
Changed line 9 from:
>> Need a new video
to:
>> %color=red% Need a new video %
Added lines 8-9:

>> Need a new video
May 20, 2014, at 08:00 PM by 65.102.176.83 -
Added lines 88-89:

-> If you're going to be using Web Direct you'll want to edit that version of Event Details: in Web Direct we show the event details in a popover. Learn how to point these popovers at your fields here: [[Event Popovers | Formatting Event Popovers]].
April 17, 2013, at 02:10 PM by 67.190.87.90 -
Changed lines 91-141 from:
[[ SeparationColors | instructions ]]

-> This step is optional, but if you want to show an event's color "on" the event record in list view and in the Event Details mini window, you'll need a table occurrence for the "CalendarRows" table in your data file (it doesn't need to be related to any other T.O.), and you'll need to add the "z_sc_ColorCalc" field from our SampleEvents table into the Events table in your data file (just copy/paste it if you have FileMaker Advanced).

-> The "z_sc_ColorCalc" field looks for global variables that are now scoped to your interface file, so you need to create these variables in your data file as well. Here's how:

-> Create a Cartesian (the "x" operator) relationship in your data file to the "CalendarColors" table from any other table (your "Events" T.O. perhaps?). Then make a new layout called "Assign Colors", based on that same T.O. (e.g., "Events"), and copy/paste the Calendar Colors portal from the "Assign Colors" layout in the interface file.

-> Then create a new script in your data file called "Apply Color Settings in Data File" by copy/pasting only the steps shown below from the Calendar file's "Apply Color Settings { Close ; DontRefresh }" script.

--> # \\
Go to Layout ["Assign Colors" (Events)] \\
# \\
Loop \\
#
---> Set Variable [$sc_namesVariable; Value:Let ( [ \\
s = CalendarColors::Name ; \\
s = Substitute ( Lower ( s ) ; \\
["\"" ; "" ] ; \\
["(" ; "" ] ; \\
[")" ; "" ] ; \\
["+" ; "" ] ; \\
["-" ; "" ] ; \\
[">" ; "" ] ; \\
["<" ; "" ] ; \\
["=" ; "" ] ; \\
["&#8800;" ; "" ] ; \\
["&#8804;" ; "" ] ; \\
["&#8805;" ; "" ] ; \\
["&" ; "" ] ; \\
["^" ; "" ] ; \\
["/" ; "" ] ; \\
["*" ; "" ] ; \\
[" or " ; "" ] ; \\
[" and " ; "" ] ; \\
[" not " ; "" ] ; \\
[" xor " ; "" ] ; \\
[" if " ; "" ] ; \\
[";" ; "" ] \\
) ] ; \\
Evaluate ( "Let ( $$sc_Color" & s &" = " & CalendarColors::ColorRBGValue & " ; \"\" )" ) ) ] \\
# \\
Go to Portal Row [Select; Next; Exit after last]
--> # \\
End Loop \\
# \\
Go to Layout [original layout] \\
#

-> Make sure this script runs when your data file opens (note that if this script is set up to be triggered by "OnFirstWindowOpen" and your data file never actually opens in a window, these color settings won't be propagated).

to:
-> This step is optional, but if you want to show an event's color "on" the event record in list view and in the Event Details mini window, follow these [[ SeparationColors | instructions ]].
April 17, 2013, at 02:04 PM by 67.190.87.90 -
Added lines 91-92:
[[ SeparationColors | instructions ]]
April 17, 2013, at 02:01 PM by 67.190.87.90 -
Changed lines 129-131 from:
Evaluate ( "Let ( $$sc_Color" & s &" = " & CalendarColors::ColorRBGValue & " ; \"\" )" ) ) ]
to:
Evaluate ( "Let ( $$sc_Color" & s &" = " & CalendarColors::ColorRBGValue & " ; \"\" )" ) ) ] \\
# \\
Go to Portal Row [Select; Next; Exit after last
]
Deleted lines 132-133:
Go to Portal Row [Select; Next; Exit after last] \\
# \\
April 17, 2013, at 01:59 PM by 67.190.87.90 -
Added lines 103-131:
#
---> Set Variable [$sc_namesVariable; Value:Let ( [ \\
s = CalendarColors::Name ; \\
s = Substitute ( Lower ( s ) ; \\
["\"" ; "" ] ; \\
["(" ; "" ] ; \\
[")" ; "" ] ; \\
["+" ; "" ] ; \\
["-" ; "" ] ; \\
[">" ; "" ] ; \\
["<" ; "" ] ; \\
["=" ; "" ] ; \\
["&#8800;" ; "" ] ; \\
["&#8804;" ; "" ] ; \\
["&#8805;" ; "" ] ; \\
["&" ; "" ] ; \\
["^" ; "" ] ; \\
["/" ; "" ] ; \\
["*" ; "" ] ; \\
[" or " ; "" ] ; \\
[" and " ; "" ] ; \\
[" not " ; "" ] ; \\
[" xor " ; "" ] ; \\
[" if " ; "" ] ; \\
[";" ; "" ] \\
) ] ; \\
Evaluate ( "Let ( $$sc_Color" & s &" = " & CalendarColors::ColorRBGValue & " ; \"\" )" ) ) ]
--> # \\
Go to Portal Row [Select; Next; Exit after last] \\
Changed lines 133-160 from:
Set Variable [$sc_namesVariable; Value:Let ( [ \\
  s = CalendarColors::Name ; \\
  s = Substitute ( Lower ( s ) ; \\
  ["\"" ; "" ] ; \\
  ["(" ; "" ] ; \\
  [")" ; "" ] ; \\
  ["+" ; "" ] ; \\
  ["-" ; "" ] ; \\
  [">" ; "" ] ; \\
  ["<" ; "" ] ; \\
  ["=" ; "" ] ; \\
  ["&#8800;" ; "" ] ; \\
  ["&#8804;" ; "" ] ; \\
  ["&#8805;" ; "" ] ; \\
  ["&" ; "" ] ; \\
  ["^" ; "" ] ; \\
  ["/" ; "" ] ; \\
  ["*" ; "" ] ; \\
  [" or " ; "" ] ; \\
  [" and " ; "" ] ; \\
  [" not " ; "" ] ; \\
  [" xor " ; "" ] ; \\
  [" if " ; "" ] ; \\
  [";" ; "" ] \\
  ) \\
  ] ; \\
  Evaluate ( "Let ( $$sc_Color" & s &" = " & CalendarColors::ColorRBGValue & " ; \"\" )" ) \\
  ) ] \\
to:
End Loop \\
Deleted lines 134-137:
Go to Portal Row [Select; Next; Exit after last] \\
# \\
End Loop \\
# \\
April 17, 2013, at 01:55 PM by 67.190.87.90 -
Added line 103:
# \\
Changed lines 105-131 from:
s = CalendarColors::Name ; \\
s = Substitute ( Lower ( s ) ; \\
["\"" ; "" ] ; \\
["(" ; "" ] ; \\
[")" ; "" ] ; \\
["+" ; "" ] ; \\
["-" ; "" ] ; \\
[">" ; "" ] ; \\
["<" ; "" ] ; \\
["=" ; "" ] ; \\
["&#8800;" ; "" ] ; \\
["&#8804;" ; "" ] ; \\
["&#8805;" ; "" ] ; \\
["&" ; "" ] ; \\
["^" ; "" ] ; \\
["/" ; "" ] ; \\
["*" ; "" ] ; \\
[" or " ; "" ] ; \\
[
" and " ; "" ] ; \\
[" not
" ; "" ] ; \\
[" xor " ; "" ] ; \\
[
" if " ; "" ] ; \\
[
";" ; "" ] \\
) \\
] ; \\
Evaluate (
"Let ( $$sc_Color" & s &" = " & CalendarColors::ColorRBGValue & " ; \"\" )" ) \\
) ] \\
to:
  s = CalendarColors::Name ; \\
  s = Substitute ( Lower ( s ) ; \\
  ["\"" ; "" ] ; \\
  ["(" ; "" ] ; \\
  [")" ; "" ] ; \\
  ["+" ; "" ] ; \\
  ["-" ; "" ] ; \\
  [">" ; "" ] ; \\
  ["<" ; "" ] ; \\
  ["=" ; "" ] ; \\
  ["&#8800;" ; "" ] ; \\
  ["&#8804;" ; "" ] ; \\
  ["&#8805;" ; "" ] ; \\
  ["&" ; "" ] ; \\
  ["^" ; "" ] ; \\
  ["/" ; "" ] ; \\
  ["*" ; "" ] ; \\
  [" or " ; "" ] ; \\
  [" and " ; "" ] ; \\
  [" not " ; "" ] ; \\
  [" xor " ; "" ] ; \\
  [" if " ; "" ] ; \\
  [";" ; "" ] \\
  ) \\
  ] ; \\
  Evaluate ( "Let ( $$sc_Color" & s &" = " & CalendarColors::ColorRBGValue & " ; \"\" )" ) \\
  ) ] \\
#
\\
Added line 134:
# \\
April 17, 2013, at 01:52 PM by 67.190.87.90 -
Changed lines 102-106 from:
Loop
---> Set Variable [$sc_namesVariable; Value:Let ( [ \\

    s = CalendarColors::Name ; \\
   
s = Substitute ( Lower ( s ) ; \\
to:
Loop \\
Set Variable [$sc_namesVariable; Value:Let ( [ \\
s = CalendarColors::Name ; \\
s
= Substitute ( Lower ( s ) ; \\
Deleted line 127:
Changed lines 130-133 from:

) ]
  Go to Portal Row [Select; Next; Exit after last] \\
--> End Loop \\
to:
) ] \\
Go
to Portal Row [Select; Next; Exit after last] \\
End Loop \\
April 17, 2013, at 01:48 PM by 67.190.87.90 -
Changed lines 102-104 from:
Loop \\
 
Set Variable [$sc_namesVariable; Value:Let ( [ \\
to:
Loop
---> Set Variable [$sc_namesVariable; Value:Let ( [ \\
Changed lines 131-134 from:

  Evaluate ( "Let ( $$sc_Color" & s &" = " & CalendarColors::ColorRBGValue & " ; \"\" )" ) \\

) ] \\
to:
Evaluate ( "Let ( $$sc_Color" & s &" = " & CalendarColors::ColorRBGValue & " ; \"\" )" ) \\

) ]
Changed line 135 from:
End Loop \\
to:
--> End Loop \\
April 17, 2013, at 01:46 PM by 67.190.87.90 -
Changed lines 103-133 from:
  Set Variable [$sc_namesVariable; Value:Let ( [

    s = CalendarColors::Name ;
    s = Substitute ( Lower ( s ) ;
["\"" ; "" ] ;
["(" ; "" ] ;
[")" ; "" ] ;
["+" ; "" ] ;
["-" ; "" ] ;
[">" ; "" ] ;
["<" ; "" ] ;
["=" ; "" ] ;
["&#8800;" ; "" ] ;
["&#8804;" ; "" ] ;
["&#8805;" ; "" ] ;
["&" ; "" ] ;
["^" ; "" ] ;
["/" ; "" ] ;
["*" ; "" ] ;
[" or " ; "" ] ;
[" and " ; "" ] ;
[" not " ; "" ] ;
[" xor " ; "" ] ;
[" if " ; "" ] ;
[";" ; "" ]
)

]
;

  Evaluate ( "Let ( $$sc_Color" & s &" = " & CalendarColors::ColorRBGValue & " ; \"\" )" )
to:
  Set Variable [$sc_namesVariable; Value:Let ( [ \\

    s = CalendarColors::Name ; \\
   s = Substitute ( Lower ( s ) ; \\
[
"\"" ; "" ] ; \\
["(" ; "" ] ; \\
[")" ; "" ] ; \\
["+" ; "" ] ; \\
["-" ; "" ] ; \\
[">" ; "" ] ; \\
["<" ; "" ] ; \\
["=" ; "" ] ; \\
["&#8800;" ; "" ] ; \\
["&#8804;" ; "" ] ; \\
["&#8805;" ; "" ] ; \\
["&" ; "" ] ; \\
["^" ; "" ] ; \\
["/" ; "" ] ; \\
["*" ; "" ] ; \\
["
or " ; "" ] ; \\
["
and " ; "" ] ; \\
["
not " ; "" ] ; \\
["
xor " ; "" ] ; \\
["
if " ; "" ] ; \\
[";" ; "" ] \\
) \\

]
; \\

   Evaluate ( "Let ( $$sc_Color" & s &" = " & CalendarColors::ColorRBGValue & " ; \"\" )" ) \\
April 17, 2013, at 01:41 PM by 67.190.87.90 -
Changed lines 103-134 from:
  Set Variable [$sc_namesVariable; Value:Let ( [ s = CalendarColors::Name ; ... ] \\
to:
  Set Variable [$sc_namesVariable; Value:Let ( [

    s = CalendarColors::Name ;
    s = Substitute ( Lower ( s ) ;
["\"" ; "" ] ;
["(" ; "" ] ;
[")" ; "" ] ;
["+" ; "" ] ;
["-" ; "" ] ;
[">" ; "" ] ;
["<" ; "" ] ;
["=" ; "" ] ;
["&#8800;" ; "" ] ;
["&#8804;" ; "" ] ;
["&#8805;" ; "" ] ;
["&" ; "" ] ;
["^" ; "" ] ;
["/" ; "" ] ;
["*" ; "" ] ;
[" or " ; "" ] ;
[" and " ; "" ] ;
[" not " ; "" ] ;
[" xor " ; "" ] ;
[" if " ; "" ] ;
[";" ; "" ]
)

] ;

  Evaluate ( "Let ( $$sc_Color" & s &" = " & CalendarColors::ColorRBGValue & " ; \"\" )" )

) ] \\
April 16, 2013, at 12:40 AM by 98.245.113.231 -
Changed lines 91-92 from:
-> If you want to show an event's color "on" the event record in list view and in the Event Details mini window, you'll need a table occurrence for the "CalendarRows" table in your data file (it doesn't need to be related to any other T.O.), and you'll need to add the "z_sc_ColorCalc" field from our SampleEvents table into the Events table in your data file (just copy/paste it if you have FileMaker Advanced).
to:
-> This step is optional, but if you want to show an event's color "on" the event record in list view and in the Event Details mini window, you'll need a table occurrence for the "CalendarRows" table in your data file (it doesn't need to be related to any other T.O.), and you'll need to add the "z_sc_ColorCalc" field from our SampleEvents table into the Events table in your data file (just copy/paste it if you have FileMaker Advanced).
April 16, 2013, at 12:35 AM by 98.245.113.231 -
Changed lines 108-109 from:
# \\
to:
#
April 16, 2013, at 12:34 AM by 98.245.113.231 -
Changed lines 91-92 from:
-> This step is optional. If you want to show an event's color "on" the event record in list view and in the Event Details mini window, follow the instructions on this [[ SeparationModel | page ]].
to:
-> If you want to show an event's color "on" the event record in list view and in the Event Details mini window, you'll need a table occurrence for the "CalendarRows" table in your data file (it doesn't need to be related to any other T.O.), and you'll need to add the "z_sc_ColorCalc" field from our SampleEvents table into the Events table in your data file (just copy/paste it if you have FileMaker Advanced).

-> The "z_sc_ColorCalc" field looks for global variables that are now scoped to your interface file, so you need to create these variables in your data file as well. Here's how:

-> Create a Cartesian (the "x" operator) relationship in your data file to the "CalendarColors" table from any other table (your "Events" T.O. perhaps?). Then make a new layout called "Assign Colors", based on that same T.O. (e.g., "Events"), and copy/paste the Calendar Colors portal from the "Assign Colors" layout in the interface file.

-> Then create a new script in your data file called "Apply Color Settings in Data File" by copy/pasting only the steps shown below from the Calendar file's "Apply Color Settings { Close ; DontRefresh }" script.

--> # \\
Go to Layout ["Assign Colors" (Events)] \\
# \\
Loop \\
  Set Variable [$sc_namesVariable; Value:Let ( [ s = CalendarColors::Name ; ... ] \\
  Go to Portal Row [Select; Next; Exit after last] \\
End Loop \\
# \\
Go to Layout [original layout] \\
# \\

-> Make sure this script runs when your data file opens (note that if this script is set up to be triggered by "OnFirstWindowOpen" and your data file never actually opens in a window, these color settings won't be propagated)
.
April 16, 2013, at 12:28 AM by 98.245.113.231 -
Changed lines 91-92 from:
-> This step is optional. Instructions are [[ SeparationModel | here ]].
to:
-> This step is optional. If you want to show an event's color "on" the event record in list view and in the Event Details mini window, follow the instructions on this [[ SeparationModel | page ]].
April 16, 2013, at 12:22 AM by 98.245.113.231 -
Changed lines 89-90 from:
'''6. That's it'''.
to:
'''6. Event colors in list view and mini windows'''.

-> This step is optional. Instructions are [[ SeparationModel | here ]].

'''7
. That's it'''.
April 15, 2013, at 03:03 PM by 83.218.158.166 -
Changed lines 1-2 from:
!! Integration Options.
to:
!! Linking the Calendar to Your Own File
Changed lines 5-8 from:
This quick version is for folks who want to keep the calendar as a separate file-- as a second .fmp12 in their solution. This can be a great option if you need to get up and running right away, or if you don't intend to really change the look and feel of the calendar layouts.

If
you want to more throughly integrate the calendar with your solution, follow [[integration | these instructions]] for pasting the calendar layouts and scripts into your file.
to:
This quick version is for folks who want to keep the calendar as a separate file-- as a second .fmp12 in their solution. This can be a great option if you need to get up and running right away, are newer to FileMaker, or want to see the calendar in a new window anyway.

If
you want to embed the calendar within your solution, follow [[Embedding the Calendar | these instructions]] for pasting the calendar layouts and scripts into your file.
Changed lines 11-12 from:
!! Step-by-Step Instructions: Quick Integration.
to:
!! Step-by-Step Instructions: Linking the Calendar.
January 02, 2013, at 07:14 PM by 206.124.30.34 -
Added lines 103-104:
If you need to set up filters on your own fields, then check out our section on [[filters]].
Deleted line 118:
November 18, 2012, at 04:23 PM by 50.132.84.245 -
Added lines 99-100:
If you'd like to change the name of "sample events" in the relationships tab, you can do that now, just read about this script you'll need to edit afterwards: [[renaming tables]].
August 09, 2012, at 02:02 AM by 50.132.84.245 -
Changed lines 9-10 from:
Before you get to work, you can watch a short video of the entire integration being done: it takes just 5 minutes... %newwin% [[https://www.youtube.com/watch?v=UQAR7MVcicc | '''Quick Integration Video''']].
to:
Before you get to work, you can watch a short video of the entire integration being done: it takes just 10 minutes... %newwin% [[https://www.youtube.com/watch?v=UQAR7MVcicc | '''Quick Integration Video''']].
August 09, 2012, at 02:02 AM by 50.132.84.245 -
Changed lines 9-10 from:
Before you get to work, you can watch a short video of the entire integration being done: it takes just 5 minutes... %newwin% [[https://www.youtube.com/watch?v=hDbpwg3kAw0 | '''Quick Integration Video''']].
to:
Before you get to work, you can watch a short video of the entire integration being done: it takes just 5 minutes... %newwin% [[https://www.youtube.com/watch?v=UQAR7MVcicc | '''Quick Integration Video''']].
August 07, 2012, at 05:10 PM by 71.212.48.84 -
Changed lines 30-31 from:
-> ...and pasting them into your file. Once they are there, edit the definition for each, removing the leading and trailing "comment" tags (the /* and */), and selecting ''your'' fields for the DateStart, TimeStart etc. fields used in the calculation's let statements. If you don't have end date or end time fields in your file, just map these to the same fields as the start fields or create new fields for this purpose. (If you create new fields, make sure the date fields are of the type "date" and the time fields are "time".)
to:
-> ...and pasting them into your file. Once they are there, edit the definition for each, removing the leading and trailing "comment" tags (the /* and */), and selecting ''your'' fields for the DateStart, TimeStart etc. fields used in the calculation's let statements.

-> It may be that you don't have an
end date field in your solution. You may also lack the time fields mentioned in the next steps (start and end times). The simplest thing is to add these fields to your events table: that makes the integration simpler and lets you take advantage of multi-day events should the scope of your events change. (Note that if you want to enforce that events never have times or never span more than 1 day you can use auto-enter calcs in these newly created fields to force them to be blank.)

-> If you create new fields, make sure the date fields are of the type "date" and the time fields are "time".

August 07, 2012, at 02:57 PM by 50.132.84.245 -
Added lines 67-68:
-> If you deleted the sample Contact, Project, or Phase table occurrences from your graph as we do in our video, be sure to visit the script "Load Source Settings at Startup --- Describe Your Sources Here ---". There you'll see two variables declared with the name of these tables. Replace those table names with "" (blank) or the calendar will ask where they are when you run the calendar's upon opening script.
Changed lines 95-96 from:
If you watched our integration video, you saw that we integrated with a table of Contact records, each of which had a "next contact date" as a field in the contact's record. When integrated with a table like this, the "new" button on the calendar doesn't make much sense: as in this case it would create a new contact record. Maybe that is what you want, but likely you'd want to create a new "action" for a contact and so the contacts file in our example would have been better served by adding an actions or events table to it and linking that table to our contact: pasting in the Sample Events table from SeedCode Calendar would have been a way to start that.
to:
Take a look at the field you mapped to Resource and edit the Resources value list in the calendar so it matches the contents of that field: we used "location" as the resource in our video and changed the "Resources" value list in the calendar to point to an existing value list in the Meetings file. You may want to do something similar. More on [[resources]].

Similarly
, we changed some of the event colors to match the values in the field we mapped on the "Color" tab of Source No 1. Read more about colors [[event colors | here]].

The "new" button on the calendar might not make sense in some cases: for example you may link to the "next contact date" of a contact record. In that case "new" would make a new contact. Maybe that is what you want, but likely you'd want to create a new "action" for a contact and so the contacts file in such
example would have been better served by adding an actions or events table to it and linking that table to our contact: pasting in the Sample Events table from SeedCode Calendar would have been a way to start that.
August 07, 2012, at 02:50 PM by 50.132.84.245 -
Changed lines 44-53 from:
-> '''2.3''' Now add the following Auto-Enter Calculated Value option to the TimeEnd field in your events table:

--> Case ( //
Self = Time ( 24 ; 0 ; 0 ) ; Time ( 24 ; 0 ; 1 ) ; //
Self = Time ( 0 ; 0 ; 0 ) ; Time ( 0 ; 0 ; 1 ) ; //
Self > Time ( 24 ; 0 ; 0 ) ; Self - Time ( 24 ; 0 ; 0 ) + 1 ; //
Self )

->
Again, 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 end at midnight.
to:
-> '''2.3''' Now add the same Auto-Enter Calculated Value option to the TimeEnd field in your events table. Again, 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 end at midnight.
August 06, 2012, at 03:22 AM by 50.132.84.245 -
Changed lines 54-55 from:
-> '''2.4''' If you plan to use the calendar's gantt charts or email notifications add a few more fields from our SampleEvents to yours:
to:
-> '''2.4''' If you plan to use the calendar's gantt charts, repeating events, or email notifications add a few more fields from our SampleEvents to yours:
Changed lines 59-60 from:
to:
--> z_Repeating_id
August 06, 2012, at 02:25 AM by 50.132.84.245 -
Changed lines 19-20 from:
-> These instructions assume you already have a table whose records you want to see in the calendar. If you don't, you can just paste our SampleEvents table into your file and skip step 2 below.
to:
-> These instructions assume you already have a table whose records you want to see in the calendar. If you don't, you can just paste our SampleEvents table into your file and skip step 2 below. 
August 06, 2012, at 02:24 AM by 50.132.84.245 -
Changed lines 15-16 from:
-> Back up your file. Seriously.
to:
-> Back up your file. Really.
Changed lines 66-71 from:
-> You'll now see all the tables in your file: select the one which has the records you'd like to see in the calendar. Change the name at the bottom of the "Specify Table" window back to "SampleEvents" (you can change it back later) and click "OK". You've now "pointed" the calendar's events table at the events table in your file: eventually you'll be able to delete the SampleEvents table in DayBackForFileMaker.fp7, but don't do it yet as you'll need it in the next step.

-> ''Note, if your events are linked to contacts, you can do the same thing with the SampleContacts table occurrence you see in the calendar, double click on the table occurrence, select your file (which now appears in the list of data sources) and select the contacts table in your file. Create a relationship between SampleEvents and SampleContacts using the same match fields you use for this kind of relationship in your file.''

-> ''And if you're using the [[gantt chart]] you'll want to do the same thing to our SampleProjects table occurrence and our SamplePhases (if you're using Phases, if you're not just leave it alone). Point these at the relevant tables in your file and make sure that they are connected to SampleEvents by the unique ids in each table.''
to:
-> You'll now see all the tables in your file: select the one which has the records you'd like to see in the calendar. Change the name at the bottom of the "Specify Table" window back to "SampleEvents" (you can change it back later) and click "OK". You've now "pointed" the calendar's events table at the events table in your file: eventually you'll be able to delete the SampleEvents table in SeedCodeCalendar.fmp12, but don't do it yet as you'll need it in the next step.

-> Note, if your events are linked to contacts, you can do the same thing with the SampleContacts table occurrences you see in the calendar, double click on the table occurrence, select your file (which now appears in the list of data sources) and select the contacts table in your file. Create a relationship between SampleEvents and SampleContacts using the same match fields you use for this kind of relationship in your file.

-> If you're using the [[gantt chart]] you'll want to do the same thing to our SampleProjects table occurrence and our SamplePhases (if you're using Phases, if you're not just leave it alone). Point these at the relevant tables in your file and make sure that they are connected to SampleEvents by the unique ids in each table.

-> ''If you don't have a contacts or projects table, and wish you did, you may want to pause this integration and take a look at %newwin% [[https://www.seedcode.com/complete | SeedCode Complete]], which already has our calendar linked to a rich contacts and project management system
.''
Changed lines 76-77 from:
-> Navigate to the Source No 1 layout in DayBackForFileMaker.fp7 and follow the instructions on the layout to map the fields there to the relevant fields in your events 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:
-> Navigate to the Source No 1 layout in SeedCodeCalendar.fmp12 and follow the instructions on the layout to map the fields there to the relevant fields in your events 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.

-> A couple tips on field mapping:

--> Events with just a single date should have a start date: if your event has just an end date the calendar will fail. The same goes for times: if there is only one time, make it the start time.

--> Don't use calcs for things like the dates, times, or resources. The calendar wants to edit these values when you drag items around, and it can't edit calcs. Use auto-enter calculations instead if you must
.
Changed lines 86-87 from:
-> Move to the Event Details layout in DayBackForFileMaker.fp7 and edit this layout as you see fit, pointing the current fields to ''your'' own fields. Just be sure to keep the following 3 objects: the "repeat" button, the "show repts..." button below it, and the large "close..." button at the bottom of the screen. You can come back and edit this layout later, for now, just get the Summary, Date, and Time fields lined up with the relevant fields in your events table.
to:
-> Move to the Event Details layout in SeedCodeCalendar.fmp12 and edit this layout as you see fit, pointing the current fields to ''your'' own fields. Just be sure to keep the following 3 objects: the "repeat" button, the "show repts..." button below it, and the large "close..." button at the bottom of the screen. You can come back and edit this layout later, for now, just get the Summary, Date, and Time fields lined up with the relevant fields in your events table.
August 06, 2012, at 02:18 AM by 50.132.84.245 -
Changed lines 17-18 from:
-> Now move DayBackForFileMaker.fp7 into the same folder as the file you'll be working with. If you'd like to rename the calendar file, do that now as well.
to:
-> Now move SeedCodeCalendar.fmp12 into the same folder as the file you'll be working with. If you'd like to rename the calendar file, do that now as well.
Changed lines 21-22 from:
-> You may also have more than one table (more more than one date field in a table) that you want to see in the calendar. Don't worry about that for now: get one table/field up and running and then you can come back and configure [[MultipleSources | additional event sources]].
to:
-> You may also have more than one table (or more than one date field in a table) that you want to see in the calendar. Don't worry about that for now: get one table/field up and running and then you can come back and configure [[MultipleSources | additional event sources]].
Changed lines 25-29 from:
->Open up DayBackForFileMaker.fp7 and select File / Manage / Database, selecting the "Fields" tab of the "Manage Database" window and select the "SampleEvents" table. You'll copy a couple fields from here and add them to your file. If you have FileMaker Advanced this is as simple as copying the last two fields...

--> z_sc_TimestampEndCalc
--> z_sc_TimestampStartCalc
to:
->Open up SeedCodeCalendar.fmp12 and select File / Manage / Database, selecting the "Fields" tab of the "Manage Database" window and select the "SampleEvents" table. You'll copy a couple fields from here and add them to your file. If you have FileMaker Advanced this is as simple as copying these two fields...

--> zscTimestampStartCalcNum
--> zscTimestampEndCalcNum
Changed lines 32-33 from:
-> If you don't have FileMaker advanced, copy the definitions of these fields, carefully recreating them in your file. Make sure both are of the type "timestamp".
to:
-> If you don't have FileMaker advanced, copy the definitions of these fields, carefully recreating them in your file. Make sure both calcs are of the type "number".

-> '''2.2''' Next, add the following Auto-Enter Calculated Value option to the TimeStart field in your events table (you can copy this here or from the definition in SampleEvents):

--> Case ( \\
Self = Time ( 24 ; 0 ; 0 ) ; Time ( 24 ; 0 ; 1 ) ; \\
Self = Time ( 0 ; 0 ; 0 ) ; Time ( 0 ; 0 ; 1 ) ; \\
Self > Time ( 24 ; 0 ; 0 ) ; Self - Time ( 24 ; 0 ; 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.

-> '''2.3''' Now add the following Auto-Enter Calculated Value option to the TimeEnd field in your events table:

--> Case ( //
Self = Time ( 24 ; 0 ; 0 ) ; Time ( 24 ; 0 ; 1 ) ; //
Self = Time ( 0 ; 0 ; 0 ) ; Time ( 0 ; 0 ; 1 ) ; //
Self > Time ( 24 ; 0 ; 0 ) ; Self - Time ( 24 ; 0 ; 0 ) + 1 ; //
Self )

-> Again, 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 end at midnight.

-> '''2.4''' If you plan to use the calendar's gantt charts or email notifications add a few more fields from our SampleEvents to yours:

--> z_LinkedWithinProject
--> z_MilestoneSort
--> z_Notified

Changed lines 62-63 from:
-> Return to DayBackForFileMaker.fp7 and again select File / Manage / Database, selecting the "Relationships" tab of the Manage Database window.
to:
-> Return to SeedCodeCalendar.fmp12 and again select File / Manage / Database, selecting the "Relationships" tab of the Manage Database window.
Changed lines 66-67 from:
-> You'll now see all the table in your file: select the one which has the records you'd like to see in the calendar. Change the name at the bottom of the "Specify Table" window back to "SampleEvents" (you can change it back later) and click "OK". You've now "pointed" the calendar's events table at the events table in your file: eventually you'll be able to delete the SampleEvents table in DayBackForFileMaker.fp7, but don't do it yet as you'll need it in the next step.
to:
-> You'll now see all the tables in your file: select the one which has the records you'd like to see in the calendar. Change the name at the bottom of the "Specify Table" window back to "SampleEvents" (you can change it back later) and click "OK". You've now "pointed" the calendar's events table at the events table in your file: eventually you'll be able to delete the SampleEvents table in DayBackForFileMaker.fp7, but don't do it yet as you'll need it in the next step.
May 22, 2012, at 01:43 PM by 50.132.84.245 -
Changed lines 5-6 from:
This quick version is for folks who want to keep the calendar as a separate file-- as a second .fp7 in their solution. This can be a great option if you need to get up and running right away, or if you don't intend to really change the look and feel of the calendar layouts.
to:
This quick version is for folks who want to keep the calendar as a separate file-- as a second .fmp12 in their solution. This can be a great option if you need to get up and running right away, or if you don't intend to really change the look and feel of the calendar layouts.
Added lines 44-45:
-> ''And if you're using the [[gantt chart]] you'll want to do the same thing to our SampleProjects table occurrence and our SamplePhases (if you're using Phases, if you're not just leave it alone). Point these at the relevant tables in your file and make sure that they are connected to SampleEvents by the unique ids in each table.''
July 16, 2010, at 07:09 PM by 71.227.154.194 -
Changed lines 9-10 from:
Before you get to work, you can watch a short video of the entire integration being done: it takes just 5 minutes... %newwin% [[https://www.seedcode.com/movies/calpro10/quickintegration.html | '''Quick Integration Video''']].
to:
Before you get to work, you can watch a short video of the entire integration being done: it takes just 5 minutes... %newwin% [[https://www.youtube.com/watch?v=hDbpwg3kAw0 | '''Quick Integration Video''']].
May 09, 2010, at 10:09 PM by 76.22.123.157 -
Deleted lines 57-58:
-> Eventually you'll want to come back to the Event Detail layout from step 5 and get that just right, and consider [[ Event Colors | color-coding events]] if that makes sense in your file. You'll also want to read through the script "Load Calendar Settings - On Startup --- Edit Configuration Here ---" making changes as necessary as this lets you change a number of the calendar's default settings.
Changed lines 60-62 from:


to:
'''Going Further'''

Eventually you'll want to come back to the Event Detail layout from step 5 and get that just right, and consider [[ Event Colors | color-coding events]] if that makes sense in your file. You'll also want to read through the script "Load Calendar Settings - On Startup --- Edit Configuration Here ---" making changes as necessary as this lets you change a number of the calendar's default settings.

If you watched our integration video, you saw that we integrated with a table of Contact records, each of which had a "next contact date" as a field in the contact's record. When integrated with a table like this, the "new" button on the calendar doesn't make much sense: as in this case it would create a new contact record. Maybe that is what you want, but likely you'd want to create a new "action" for a contact and so the contacts file in our example would have been better served by adding an actions or events table to it and linking that table to our contact: pasting in the Sample Events table from SeedCode Calendar would have been a way to start that.

In any event, think about the kind of records you've mapped to Source No 1 and Event Detail, and if you think you might need an action or events table, you hopefully now have the confidence to begin adding one.

And don't forget you can have more than one calendar at a time--more than one "source"--and have some from fields in a contact's record and other calendars from events tables. Learn more by reading about [[multiple sources]].







May 09, 2010, at 10:04 PM by 76.22.123.157 -
Changed lines 1-4 from:
!! Who is this for?

'''Introduction
.'''
to:
!! Integration Options.

'''Who
is this Quick Integration designed for.'''
Changed lines 11-12 from:
!! Step-by-Step Instructions
to:
!! Step-by-Step Instructions: Quick Integration.
May 09, 2010, at 09:56 PM by 76.22.123.157 -
Added line 10:
May 09, 2010, at 09:56 PM by 76.22.123.157 -
Added line 9:
Before you get to work, you can watch a short video of the entire integration being done: it takes just 5 minutes... %newwin% [[https://www.seedcode.com/movies/calpro10/quickintegration.html | '''Quick Integration Video''']].
May 08, 2010, at 11:31 PM by 76.22.123.157 -
Changed lines 19-20 from:
-> You may also have more than one table (more more than one date field in a table) that you want to see in the calendar. Don't worry about that for now: get one table/field up and running and then you can come back and configure [[MultipleSouces | additional event sources]].
to:
-> You may also have more than one table (more more than one date field in a table) that you want to see in the calendar. Don't worry about that for now: get one table/field up and running and then you can come back and configure [[MultipleSources | additional event sources]].
May 08, 2010, at 11:30 PM by 76.22.123.157 -
Changed lines 5-8 from:
-> This quick version is for folks who want to keep the calendar as a separate file-- as a second .fp7 in their solution. This can be a great option if you need to get up and running right away, or if you don't intend to really change the look and feel of the calendar layouts.

-> If you want to more throughly integrate the calendar with your solution, follow [[integration | these instructions]] for pasting the calendar layouts and scripts into your file.
to:
This quick version is for folks who want to keep the calendar as a separate file-- as a second .fp7 in their solution. This can be a great option if you need to get up and running right away, or if you don't intend to really change the look and feel of the calendar layouts.

If you want to more throughly integrate the calendar with your solution, follow [[integration | these instructions]] for pasting the calendar layouts and scripts into your file.
May 08, 2010, at 11:30 PM by 76.22.123.157 -
Changed lines 5-6 from:
-> This quick version is for folks who want to keep the calendar as a separate .fp7-- as a second file in their solution. This can be a great option if you need to get up and running right away, or if you don't intend to really change the look and feel of the calendar layouts.
to:
-> This quick version is for folks who want to keep the calendar as a separate file-- as a second .fp7 in their solution. This can be a great option if you need to get up and running right away, or if you don't intend to really change the look and feel of the calendar layouts.
May 08, 2010, at 11:29 PM by 76.22.123.157 -
Added lines 19-20:
-> You may also have more than one table (more more than one date field in a table) that you want to see in the calendar. Don't worry about that for now: get one table/field up and running and then you can come back and configure [[MultipleSouces | additional event sources]].
May 08, 2010, at 11:18 PM by 76.22.123.157 -
Changed lines 15-16 from:
-> Move DayBackForFileMaker.fp7 into the same folder as the file you'll be working with. If you'd like to rename the calendar file, do that now as well.
to:
-> Now move DayBackForFileMaker.fp7 into the same folder as the file you'll be working with. If you'd like to rename the calendar file, do that now as well.
May 08, 2010, at 11:17 PM by 76.22.123.157 -
Added lines 13-14:
-> Back up your file. Seriously.
May 08, 2010, at 11:12 PM by 76.22.123.157 -
Added lines 15-16:
-> These instructions assume you already have a table whose records you want to see in the calendar. If you don't, you can just paste our SampleEvents table into your file and skip step 2 below.
May 08, 2010, at 11:09 PM by 76.22.123.157 -
Added lines 1-2:
!! Who is this for?
Added lines 9-10:
!! Step-by-Step Instructions
May 08, 2010, at 11:09 PM by 76.22.123.157 -
Deleted lines 0-1:
''This is something we're still working on, so stay tuned. - John''
May 08, 2010, at 11:09 PM by 76.22.123.157 -
Added lines 3-8:
'''Introduction.'''

-> This quick version is for folks who want to keep the calendar as a separate .fp7-- as a second file in their solution. This can be a great option if you need to get up and running right away, or if you don't intend to really change the look and feel of the calendar layouts.

-> If you want to more throughly integrate the calendar with your solution, follow [[integration | these instructions]] for pasting the calendar layouts and scripts into your file.

Changed lines 44-46 from:
6. The Script: Optional

to:
'''6. That's it'''.

-> Refresh the calendar and you'll see your events. Pretty simple.

-> Eventually you'll want to come back to the Event Detail layout from step 5 and get that just right, and consider [[ Event Colors | color-coding events]] if that makes sense in your file. You'll also want to read through the script "Load Calendar Settings - On Startup --- Edit Configuration Here ---" making changes as necessary as this lets you change a number of the calendar's default settings.

-> Enjoy!



May 08, 2010, at 10:48 PM by 76.22.123.157 -
Changed lines 18-19 from:
''3. The Relationship Graph.''
to:
'''3. The Relationship Graph.'''
May 08, 2010, at 10:48 PM by 76.22.123.157 -
Changed lines 1-2 from:
1. Getting ready.
to:
''This is something we're still working on, so stay tuned. - John''

'''1. Getting ready.'''

Changed lines 7-8 from:
2. Field Definitions.
to:
'''2. Field Definitions.'''
Changed lines 18-19 from:
3. The Relationship Graph.
to:
''3. The Relationship Graph.''
Changed lines 28-29 from:
4. Layouts Part 1: Field Mapping
to:
'''4. Layouts Part 1: Field Mapping'''
Changed lines 32-33 from:
5. Layouts Part 2: Event Details
to:
'''5. Layouts Part 2: Event Details'''
May 08, 2010, at 10:45 PM by 76.22.123.157 -
May 08, 2010, at 10:45 PM by 76.22.123.157 -
May 08, 2010, at 10:45 PM by 76.22.123.157 -
Added lines 32-35:
-> Move to the Event Details layout in DayBackForFileMaker.fp7 and edit this layout as you see fit, pointing the current fields to ''your'' own fields. Just be sure to keep the following 3 objects: the "repeat" button, the "show repts..." button below it, and the large "close..." button at the bottom of the screen. You can come back and edit this layout later, for now, just get the Summary, Date, and Time fields lined up with the relevant fields in your events table.

-> Down the road you can come back to this and add buttons to [[ JumpToMyEvent | jump to the related record in your file ]], or event to your event's [[ JumpToMyContact | related contact ]].

May 08, 2010, at 10:40 PM by 76.22.123.157 -
Changed lines 28-30 from:
-> Navigate to the Source No 1 layout in DayBackForFileMaker.fp7 and follow the instructions on the layout to map the fields there to the relevant fields in your events table.

to:
-> Navigate to the Source No 1 layout in DayBackForFileMaker.fp7 and follow the instructions on the layout to map the fields there to the relevant fields in your events 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.
May 08, 2010, at 10:38 PM by 76.22.123.157 -
Changed lines 26-27 from:

to:
4. Layouts Part 1: Field Mapping

-> Navigate to the Source No 1 layout in DayBackForFileMaker.fp7 and follow the instructions on the layout to map the fields there to the relevant fields in your events table.


5. Layouts Part 2: Event Details

6. The Script: Optional


May 08, 2010, at 10:36 PM by 76.22.123.157 -
Changed lines 12-15 from:
...and pasting them into your file.
to:
-> ...and pasting them into your file. Once they are there, edit the definition for each, removing the leading and trailing "comment" tags (the /* and */), and selecting ''your'' fields for the DateStart, TimeStart etc. fields used in the calculation's let statements. If you don't have end date or end time fields in your file, just map these to the same fields as the start fields or create new fields for this purpose. (If you create new fields, make sure the date fields are of the type "date" and the time fields are "time".)

-> If you don't have FileMaker advanced, copy the definitions of these fields, carefully recreating them in your file. Make sure both are of the type "timestamp".

May 08, 2010, at 10:30 PM by 76.22.123.157 -
Added lines 1-24:
1. Getting ready.

-> Move DayBackForFileMaker.fp7 into the same folder as the file you'll be working with. If you'd like to rename the calendar file, do that now as well.

2. Field Definitions.

->Open up DayBackForFileMaker.fp7 and select File / Manage / Database, selecting the "Fields" tab of the "Manage Database" window and select the "SampleEvents" table. You'll copy a couple fields from here and add them to your file. If you have FileMaker Advanced this is as simple as copying the last two fields...

--> z_sc_TimestampEndCalc
--> z_sc_TimestampStartCalc

...and pasting them into your file.
3. The Relationship Graph.

-> Return to DayBackForFileMaker.fp7 and again select File / Manage / Database, selecting the "Relationships" tab of the Manage Database window.

-> Double click on the "SampleEvents" table occurrence in the graph and click in the pop-up list next to "Data Source:"-- select "Add FileMaker Data Source" from the list of options and, in the next window, select your file.

-> You'll now see all the table in your file: select the one which has the records you'd like to see in the calendar. Change the name at the bottom of the "Specify Table" window back to "SampleEvents" (you can change it back later) and click "OK". You've now "pointed" the calendar's events table at the events table in your file: eventually you'll be able to delete the SampleEvents table in DayBackForFileMaker.fp7, but don't do it yet as you'll need it in the next step.

-> ''Note, if your events are linked to contacts, you can do the same thing with the SampleContacts table occurrence you see in the calendar, double click on the table occurrence, select your file (which now appears in the list of data sources) and select the contacts table in your file. Create a relationship between SampleEvents and SampleContacts using the same match fields you use for this kind of relationship in your file.''


(855) SEEDCODE
[email protected]
Follow us: