SeedCodeCalendar12

Filters

SeedCodeCalendar12.Filters History

Hide minor edits - Show changes to output

July 07, 2013, at 09:14 PM by 50.132.84.245 -
Changed lines 3-4 from:
Filters operate like a find request, letting you see just a subset of the events in the calendar.
to:
Filters operate like a find request, letting you see just a subset of the events in the calendar: that may be "your events", or events for a particular department, or those for a single customer. You can use the filters that come with the calendar, repurpose those, or create your own following the instructions below.
November 09, 2012, at 07:13 PM by 107.2.189.216 -
Changed lines 49-50 from:
-> '''9.''' Enter browse mode and run the Upon Opening script again. That's it!
to:
-> '''9.''' Edit the script "Build Filters ( Source No )" under the comment '''#Short circuit if no filters are filled in''' so the '''If''' calculation contains any new filters you've added.

-> '''10
.''' Enter browse mode and run the Upon Opening script again. That's it!
May 20, 2012, at 02:45 AM by 50.132.84.245 -
Changed lines 45-46 from:
-> '''7.''' Finally, edit the script "Load Calendar Settings - On Startup..." and find the comment "Maps filters to fields". Create a new SetVariable line for your new filter ($$sc_FilterField5 in our example) and, using your new field for the GetFieldName (GetFieldName ( SampleEvents::StaffName) in our example ).
to:
-> '''7.''' Finally, edit the script "Load Calendar Settings - On Startup..." and find the comment "Maps filters to fields". Create a new SetVariable line for your new filter ($$sc_FilterField5 in our example) and, using your new field for the GetFieldName ( SampleEvents::StaffName) in our example.
May 17, 2012, at 10:11 PM by 50.132.84.245 -
Added lines 19-26:
'''More Details'''

-> A generic filter like "Event Title" may need to be mapped to a different field in each source's events table, so we let you map a return delimited list of field names (ideally GetFieldName()s) to each filter. When filtering we then execute on the first mapped field from the same table occurrence as the source in question.

-> This means we can only filter fields local to the source TO, but that is probably a good thing.

-> If no mapped fields match the source's TO we treat the filter as excluding that source. So a source of "Company meetings" might have a filter for "mandatory". That doesn't make sense in any other context. If you're then showing meetings along side your Birthdays source and you filter to see everything "mandatory", we'll hide all Birthdays since none are mandatory.

April 18, 2012, at 08:28 AM by 78.86.120.203 -
Changed lines 47-48 from:
Toward the end of the configuration script "Load Calendar Settings - On Startup --- Edit Configuration Here ---" you'll see a comment called "Pre-Filter the calendar if necessary". The next 4 lines set the two default filters that come with our calendar. The lines are currently disable: enable 2 or 4 of them if you have FileMaker Advanced, or recreate the two or four lines you need if you don't.
to:
Toward the end of the configuration script "Load Calendar Settings - On Startup --- Edit Configuration Here ---" you'll see a comment called "Pre-Filter the calendar if necessary". The next lines set the four default filters that come with our calendar. The lines are currently disabled: enable any pair of them if you have FileMaker Advanced, or recreate the pair of lines you need if you don't.
April 17, 2012, at 06:00 PM by 166.137.11.159 -
Changed lines 11-12 from:
!! Filtering on different fields
to:
!! Filtering on different fields & different sources
Added lines 15-18:
If you're using [[multiple sources]] you can map the same filter to a different field in each of your source tables. For example, our "title" filter may be mapped to the Summary field in your events table (that is, it searched for an event summary containing the text entered in the title filter) and mapped to the Procedure field in your surgeries table.

To do this (to map a filter to more than one field) separate the mapped fields with carriage returns like we've done in our sample integration for filters 1 and 2. (Note that you can only map a filter to one field from each table.)

March 21, 2012, at 10:53 PM by 50.132.84.245 -
Changed lines 25-32 from:
-> '''3.''' Enter layout mode and navigate to the Filters tab of the calendar layout. Read this section on [[calendar tabs]] if you're having trouble getting to the correct tab.

->
'''4.''' Duplicate (copy and paste) one of the existing filter fields on the layout and then switch this field to be FilterGlob_5. Format this field to use the value list you created in 2 above; format it as checkboxes if you'd like to support multiple selections.

-> '''5.''' Edit the script trigger for this field, keeping the script the same but changing
the parameter to be the "number" of the field ("5" in our example).

-> '''6.''' Still editing
the Filters tab of the Calendar layout, duplicate the "clear", "include", and "omit" buttons, placing them next to your new filter and change the script's script parameters for each of these buttons to use the "number" of the field ("5" in our example). Edit the conditional formatting for each of these to use the new filter number ("5" in our example).
to:
-> '''3.''' Enter layout mode and navigate to the Filters tab of the calendar layout.

-> '''4.''' Duplicate (copy and paste) one of the existing filter fields (don't use
the resource filter, it's special) on the layout and then switch this field to be FilterGlob_5. Format this field to use the value list you created in 2 above; format it as checkboxes if you'd like to support multiple selections.

->
'''5.''' These filter fields have script triggers on them: you can leave the trigger alone if you've copied one of the existing fields.

-> '''6.''' Still editing
the Filters tab of the Calendar layout, duplicate the "clear", "include", and "omit" buttons, placing them next to your new filter and change the script's script parameters for each of these buttons to use the "number" of the field ("5" in our example). Edit the conditional formatting for each of these to use the new filter number ("5" in our example). If you're not sure how to edit those "include / omit" switches, you can learn how [[Fancy Switches | here]].
Changed lines 35-38 from:
-> '''8.''' Enter browse mode and run the Upon Opening script again and you're done. If you've added more than 5 filters, edit the script "Apply Filter to Found Set" and change the first variable there to be the number of filters you now have.

-> '''9.''' Edit the script "Clear All Filters" (new in v 5.551) and add additional SetField and SetVariable steps for your new filter fields.

to:
-> '''8.''' Edit the script "Clear All Filters" and add additional SetField and SetVariable steps for your new filter fields.

-> '''9.''' Enter browse mode and run the Upon Opening script again. That's it!

March 21, 2012, at 10:19 PM by 50.132.84.245 -
Changed lines 9-10 from:
The title filter works the same way: type in "Call" and you'll see all the events where a work in the Summary begins with "call". These filters works just like the "constrain found set" find request you're already familiar with in FileMaker.
to:
The title filter works the same way: type in "Call" and you'll see all the events where a work in the Summary begins with "Call". These filters work very much like the "constrain found set" find request you're already familiar with in FileMaker except that these filters are case sensitive, so "Some" will find the event "Someone is coming over" but not "Get me some help."
Added lines 37-38:
-> '''9.''' Edit the script "Clear All Filters" (new in v 5.551) and add additional SetField and SetVariable steps for your new filter fields.
September 25, 2010, at 02:59 PM by 99.191.194.227 -
Changed lines 5-6 from:
Filters are available on the Filters tab in the left hand status area. SeedCode Calendar ships with three filters in place already: title, status, and resource. To see how this works, select an item in the status filter and you'll see the calendar change to show just the items of that status. Note that you can select more than one status in the filter.
to:
Filters are available on the Filters tab in the left hand status area. SeedCode Calendar ships with four filters in place already: title, project, status, and resource. To see how this works, select an item in the status filter and you'll see the calendar change to show just the items of that status. Note that you can select more than one status in the filter.
Changed lines 23-24 from:
-> '''2.''' Create a value list for staff names. Then create a global text field in the CalendarInterface table called FilterGlob_4
to:
-> '''2.''' Create a value list for staff names. Then create a global text field in the CalendarInterface table called FilterGlob_5
Changed lines 27-36 from:
-> '''4.''' Duplicate (copy and paste) one of the existing filter fields on the layout and then switch this field to be FilterGlob_4. Format this field to use the value list you created in 2 above; format it as checkboxes if you'd like to support multiple selections.

-> '''5.''' Edit the script trigger for this field, keeping the script the same but changing the parameter to be the "number" of the field ("4" in our example).

-> '''6.''' Still editing the Filters tab of the Calendar layout, duplicate the "clear", "include", and "omit" buttons, placing them next to your new filter and change the script's script parameters for each of these buttons to use the "number" of the field ("4" in our example). Edit the conditional formatting for each of these to use the new filter number ("4" in our example).

-> '''7.''' Finally, edit the script "Load Calendar Settings - On Startup..." and find the comment "Maps filters to fields". Create a new SetVariable line for your new filter ($$sc_FilterField4 in our example) and, using your new field for the GetFieldName (GetFieldName ( SampleEvents::StaffName) in our example ).

-> '''8.''' Enter browse mode and run the Upon Opening script again and you're done. If you've added more than 5 filters, edit the script "Apply Filter to Found Set" and change the first variable there to be the number of filters you now have.
to:
-> '''4.''' Duplicate (copy and paste) one of the existing filter fields on the layout and then switch this field to be FilterGlob_5. Format this field to use the value list you created in 2 above; format it as checkboxes if you'd like to support multiple selections.

-> '''5.''' Edit the script trigger for this field, keeping the script the same but changing the parameter to be the "number" of the field ("5" in our example).

-> '''6.''' Still editing the Filters tab of the Calendar layout, duplicate the "clear", "include", and "omit" buttons, placing them next to your new filter and change the script's script parameters for each of these buttons to use the "number" of the field ("5" in our example). Edit the conditional formatting for each of these to use the new filter number ("5" in our example).

-> '''7.''' Finally, edit the script "Load Calendar Settings - On Startup..." and find the comment "Maps filters to fields". Create a new SetVariable line for your new filter ($$sc_FilterField5 in our example) and, using your new field for the GetFieldName (GetFieldName ( SampleEvents::StaffName) in our example ).

-> '''8.''' Enter browse mode and run the Upon Opening script again and you're done. If you've added more than 5 filters, edit the script "Apply Filter to Found Set" and change the first variable there to be the number of filters you now have. 
June 08, 2010, at 01:03 AM by 166.137.9.179 -
Changed lines 31-32 from:
-> '''6.''' Still editing the Filters tab of the Calendar layout, duplicate the "clear", "include", and "omit" buttons, placing them next to your new filter and change the script parameters for each of these buttons to use the "number" of the field ("4" in our example). Edit the conditional formatting for each of these to use the new filter number ("4" in our example).
to:
-> '''6.''' Still editing the Filters tab of the Calendar layout, duplicate the "clear", "include", and "omit" buttons, placing them next to your new filter and change the script's script parameters for each of these buttons to use the "number" of the field ("4" in our example). Edit the conditional formatting for each of these to use the new filter number ("4" in our example).
June 08, 2010, at 01:00 AM by 166.137.9.179 -
Changed lines 31-32 from:
-> '''6.''' Still editing the Filters tab of the Calendar layout, duplicate the "clear", "include", and "omit" buttons, placing them next to your new filter and change the script parameters for each of these buttons to use he "number" of the field ("4" in our example). Edit the conditional formatting for each of these to use the new filter number ("4" in our example).
to:
-> '''6.''' Still editing the Filters tab of the Calendar layout, duplicate the "clear", "include", and "omit" buttons, placing them next to your new filter and change the script parameters for each of these buttons to use the "number" of the field ("4" in our example). Edit the conditional formatting for each of these to use the new filter number ("4" in our example).
April 06, 2010, at 04:24 PM by 67.171.26.249 -
Changed lines 35-36 from:
-> '''8.''' Enter browse mode and run the Upon Opening script again and you're done.
to:
-> '''8.''' Enter browse mode and run the Upon Opening script again and you're done. If you've added more than 5 filters, edit the script "Apply Filter to Found Set" and change the first variable there to be the number of filters you now have.
February 03, 2010, at 03:56 AM by 76.22.123.157 -
Changed lines 23-24 from:
-> '''2.''' Create a value list for staff names
to:
-> '''2.''' Create a value list for staff names. Then create a global text field in the CalendarInterface table called FilterGlob_4
Changed lines 27-34 from:
-> '''4.''' Duplicate (copy and paste) one of the existing filter fields on the layout and then switch this field to be FilterGlob_3 (if you've already used that field create a global text field in the CalendarInterface table called FilterGlob_4). Format this field to use the value list you created in 2 above; format it as checkboxes if you'd like to support multiple selections.

-> '''5.''' Edit
the script trigger for this field, keeping the script the same but changing the parameter to be the "number" of the field ("3" in our example).

-> '''6.''' Still editing the Filters tab of the Calendar layout, duplicate
the "clear", "include", and "omit" buttons, placing them next to your new filter and change the script parameters for each of these buttons to use he "number" of the field ("3" in our example). Edit the conditional formatting for each of these to use the new filter number ("3" in our example).

-> '''7.''' Finally, edit the script "Load Calendar Settings - On Startup..." and find the comment "Maps filters to fields". Create a new SetVariable line for your new filter ($$sc_FilterField3
in our example) and, using your new field for the GetFieldName (GetFieldName ( SampleEvents::StaffName) in our example ).
to:
-> '''4.''' Duplicate (copy and paste) one of the existing filter fields on the layout and then switch this field to be FilterGlob_4. Format this field to use the value list you created in 2 above; format it as checkboxes if you'd like to support multiple selections.

-> '''5.''' Edit the script trigger for this field, keeping the script the same but changing the parameter to be
the "number" of the field ("4" in our example).

-> '''6.''' Still editing
the Filters tab of the Calendar layout, duplicate the "clear", "include", and "omit" buttons, placing them next to your new filter and change the script parameters for each of these buttons to use he "number" of the field ("4" in our example). Edit the conditional formatting for each of these to use the new filter number ("4" in our example).

-> '''7.''' Finally, edit the script "Load Calendar Settings - On Startup..." and find the comment
"Maps filters to fields". Create a new SetVariable line for your new filter ($$sc_FilterField4 in our example) and, using your new field for the GetFieldName (GetFieldName ( SampleEvents::StaffName) in our example ).
February 03, 2010, at 03:54 AM by 76.22.123.157 -
Added lines 11-14:
!! Filtering on different fields

You can point the existing filters at any fields in your events table that you'd like. Mapping filters to fields is done in the "Load Calendar Settings - On Startup..." script you edited as part of your [[integration]].

February 03, 2010, at 03:53 AM by 76.22.123.157 -
Changed lines 5-6 from:
Filters are available on the Filters tab in the left hand status area. SeedCode Calendar ships with two filters in place already: title and status. To see how this works, select an item in the status filter and you'll see the calendar change to show just the items of that status. Note that you can select more than one status in the filter.
to:
Filters are available on the Filters tab in the left hand status area. SeedCode Calendar ships with three filters in place already: title, status, and resource. To see how this works, select an item in the status filter and you'll see the calendar change to show just the items of that status. Note that you can select more than one status in the filter.
January 28, 2010, at 01:54 AM by 76.22.123.157 -
December 29, 2009, at 06:54 AM by 76.22.123.157 -
Changed lines 23-24 from:
-> '''4.''' Duplicate (copy and paste) one of the existing filter fields on the layout and then switch this field to be FilterGlob_3 (if you've already used that field create a global text field in the CalendarInterface table called FilterGlob_4. Format this field to use the value list you created in 2 above.
to:
-> '''4.''' Duplicate (copy and paste) one of the existing filter fields on the layout and then switch this field to be FilterGlob_3 (if you've already used that field create a global text field in the CalendarInterface table called FilterGlob_4). Format this field to use the value list you created in 2 above; format it as checkboxes if you'd like to support multiple selections.
December 29, 2009, at 06:53 AM by 76.22.123.157 -
Deleted lines 32-33:
> > Continue...
December 29, 2009, at 06:52 AM by 76.22.123.157 -
Changed lines 27-28 from:
-> '''6.''' Still editing the Filters tab of the Calendar layout, duplicate the "clear", "include", and "omit" buttons, placing them next to your new filter and change the script parameters for each of these buttons to use he "number" of the field ("3" in our example).
to:
-> '''6.''' Still editing the Filters tab of the Calendar layout, duplicate the "clear", "include", and "omit" buttons, placing them next to your new filter and change the script parameters for each of these buttons to use he "number" of the field ("3" in our example). Edit the conditional formatting for each of these to use the new filter number ("3" in our example).
December 29, 2009, at 06:50 AM by 76.22.123.157 -
Changed lines 29-30 from:
-> '''7.''' That' it.
to:
-> '''7.''' Finally, edit the script "Load Calendar Settings - On Startup..." and find the comment "Maps filters to fields". Create a new SetVariable line for your new filter ($$sc_FilterField3 in our example) and, using your new field for the GetFieldName (GetFieldName ( SampleEvents::StaffName) in our example ).

-> '''8.''' Enter browse mode and run the Upon Opening script again and you're done
.
December 29, 2009, at 06:44 AM by 76.22.123.157 -
Changed lines 29-30 from:
- '''7.''' That' it.
to:
-> '''7.''' That' it.
December 29, 2009, at 06:44 AM by 76.22.123.157 -
December 29, 2009, at 06:44 AM by 76.22.123.157 -
December 29, 2009, at 06:44 AM by 76.22.123.157 -
Changed lines 21-22 from:
-> '''3.''' > > Continue...
to:
-> '''3.''' Enter layout mode and navigate to the Filters tab of the calendar layout. Read this section on [[calendar tabs]] if you're having trouble getting to the correct tab.

-> '''4.''' Duplicate (copy and paste) one of the existing filter fields on the layout and then switch this field to be FilterGlob_3 (if you've already used that field create a global text field in the CalendarInterface table called FilterGlob_4. Format this field to use the value list you created in 2 above.

-> '''5.''' Edit the script trigger for this field, keeping the script the same but changing the parameter to be the "number" of the field ("3" in our example).

-> '''6.''' Still editing the Filters tab of the Calendar layout, duplicate the "clear", "include", and "omit" buttons, placing them next to your new filter and change the script parameters for each of these buttons to use he "number" of the field ("3" in our example).

- '''7.''' That' it.

> > Continue...
December 24, 2009, at 06:18 PM by 76.22.123.157 -
Changed lines 21-29 from:
-> '''3.''' > > Continue...
to:
-> '''3.''' > > Continue...

!! Can I pre-filter the calendar so it starts up already filtered?

Yes, and this can be a great way to speed up the calendar if you have tons of events, but many are already "complete" or irrelevant.

Toward the end of the configuration script "Load Calendar Settings - On Startup --- Edit Configuration Here ---" you'll see a comment called "Pre-Filter the calendar if necessary". The next 4 lines set the two default filters that come with our calendar. The lines are currently disable: enable 2 or 4 of them if you have FileMaker Advanced, or recreate the two or four lines you need if you don't.

The first line (the Set Field) in each pair sets the value to be filtered ("Something" in our example), and the second line (the Set Variable) passes that filter into the calendar engine. Both lines in the pair need to be enabled, but you only need to edit the value in the first line of the pair ("Something" in our example)
.
December 20, 2009, at 04:56 AM by 76.22.123.157 -
Changed lines 21-23 from:
-> '''3.''' Create a Staff field.

-> If y
to:
-> '''3.''' > > Continue...
December 06, 2009, at 02:03 AM by 76.22.123.157 -
Changed lines 7-8 from:
Now click "Omit" beside the filter and you'll see everything ''except'' events of the status you've selected.
to:
Now click "Omit" beside the filter and you'll see everything ''except'' events of the status you've selected.

The title filter works the same way: type in "Call" and you'll see all the events where a work in the Summary begins with "call". These filters works just like the "constrain found set" find request you're already familiar with in FileMaker
.
Changed lines 13-23 from:
Sure...
to:
Sure. Let's say you wanted to add a filter called "Staff" so you could see just the events for one or more staff members (for just you, or for the members of your team). Here's how you'd do it...

-> '''1.''' Create a staff name field in the events table.

-> If you don't already have a field in your events table for the staff member's name, create one. For the sake of this example we'll use the staff member's name as the filter, but you could use their ID, etc.

-> '''2.''' Create a value list for staff names

-> '''3.''' Create a Staff field.

-> If y
December 06, 2009, at 01:54 AM by 76.22.123.157 -
Added lines 1-11:
!! How can I filter the calendar?

Filters operate like a find request, letting you see just a subset of the events in the calendar.

Filters are available on the Filters tab in the left hand status area. SeedCode Calendar ships with two filters in place already: title and status. To see how this works, select an item in the status filter and you'll see the calendar change to show just the items of that status. Note that you can select more than one status in the filter.

Now click "Omit" beside the filter and you'll see everything ''except'' events of the status you've selected.

!! Can I add new filters?

Sure...
(855) SEEDCODE
support@seedcode.com
Follow us: