Quick Integration

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

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

Loop
---> Set Variable [$sc_namesVariable; Value:Let ( [ \\

    s = CalendarColors::Name ; \\
    s = Substitute ( Lower ( s ) ; \\

) ]
  Go to Portal Row [Select; Next; Exit after last] \\
--> End Loop \\

Loop \\
  Set Variable [$sc_namesVariable; Value:Let ( [ \\

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

) ] \\

End 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 & " ; \"\" )" )

-> 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).

# \\

-> 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 ]].

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

'''6. That's it'''.

!! Integration Options.

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.

!! Step-by-Step Instructions: Quick Integration.

Before you get to work, you can watch a short video of the entire integration being done: it takes just 5 minutes... %newwin% [[http://www.youtube.com/watch?v=UQAR7MVcicc | '''Quick Integration Video''']].

Before you get to work, you can watch a short video of the entire integration being done: it takes just 5 minutes... %newwin% [[http://www.youtube.com/watch?v=hDbpwg3kAw0 | '''Quick Integration Video''']].

-> ...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 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.

-> '''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:

-> 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.

-> Back up your file. Seriously.

-> 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 SeedCodeCalendar12.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.''

-> Navigate to the Source No 1 layout in SeedCodeCalendar12.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.

-> Move to the Event Details layout in SeedCodeCalendar12.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.

-> Now move SeedCodeCalendar12.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.

-> 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]].

->Open up SeedCodeCalendar12.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

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

-> 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 SeedCodeCalendar12.fp7, but don't do it yet as you'll need it in the next step.

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.

Before you get to work, you can watch a short video of the entire integration being done: it takes just 5 minutes... %newwin% [[http://www.seedcode.com/movies/calpro10/quickintegration.html | '''Quick Integration Video''']].

!! Who is this for?

'''Introduction.'''

!! Step-by-Step Instructions

-> 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]].

-> 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.

-> 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.

-> Move SeedCodeCalendar12.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.

6. The Script: Optional

''3. The Relationship Graph.''

1. Getting ready.

2. Field Definitions.

3. The Relationship Graph.

4. Layouts Part 1: Field Mapping

5. Layouts Part 2: Event Details

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

...and pasting them into your file.