Using Zulu's Filters
Multiple Calendars Based on the Same FileMaker Table: Filtering
Using "Filtering" you can have an individual FileMaker table show up as multiple calendars in iCal: or have only a subset of a table show up in iCal.
Each "calendar" in iCal is represented by a record in the ZuluCalendarList table you added to your FileMaker file during integration. By adding a value to the zulu_filterKey and zulu_filterValue fields in this table, you can have that calendar "find" just a subset of FileMaker records to display.
You can see an overview of filtering in action here: Zulu Introduction: Demonstrating Filtering
Adding a Filter to an Existing Calendar
Note: you don't have to re-publish if you're just adding new calendars. You only need to republish if you've changed field mappings.
Remember that this is a "contains" search, so in our example above it will filter for events where the event's status contains "Urgent".
If you want to have a calendar for items where there is no status, enter a value for the filter field in zulu_filterKey, but enter "=" (without quotes) into zulu_filterValue.
Creating Additional Filtered Calendars: Duplicating Calendars
You can duplicate existing calendars by duplicating their ZuluCalendarList records and just changing their filter criteria. Just be aware of a couple things:
Switching an event from Calendar to Calendar in iCal
Learn more about this in Switching Calendars.
Filtering on Different Fields.
Note that you don't have to have all your calendars filtering on the same field. You could have several calendars filtering on Resource (the production studio in which an event is scheduled, for example). Then you could create an additional calendar filtering on "Status" showing you just the events that are marked "Rush".
Additional Calendars from Different FileMaker Tables.
You can also publish more than one table in the same FileMaker file. This is pretty simple...
Additional Calendars from Different FileMaker Files.
Rather than import the Zulu scripts and tables into separate files. Use a single file to hold the Zulu scripts and ZuluCalendarList table: then create new table occurrences in that file for each calendar you wish to publish from another file, following the directions for "Additional Calendars from Different FileMaker Tables" above.
Check out this video demonstrating how you can use auto-enter calcs to preserve values that might otherwise be edited by filters. This technique can also be used to make parts of Zulu calendar records uneditable without throwing errors in iCal.
Note: Zulu's Contact Sync is Back in Beta
Regretfully, we've just never been able to get the contact sync in Zulu to be reliable with Google Contacts. Some of this is that Google Contacts is changing and some if that contacts are inherently more complicated than calendar events (the calendar sync in Zulu is rock solid). So until we can get this rock solid we're demoting the contact sync to Beta and no longer supporting it.
We'll continue playing with this here but won't be able to help customers try and get it working: it just isn't reliable enough. At this point we don't have an ETA as to when this feature may be available again, if ever. Believe me, we wanted this to work as bad as you did. Dec 27, 2012.
Showing only a subset of your contacts.
You can use a filter in Zulu Contacts to show only a subset of your contacts. Filters act like a find request, syncing only the matching records to Google.
Note that you can also segment your contacts using Groups, and restrict which contacts are synced using Access Privileges, so filters are only one tool among many as you're deciding which contacts Zulu should sync to Google.
Navigate to the ZuluContactConfig layout in your file (or in Zulu's sample contacts file) and you'll see the two fields used for filtering:
In zulu_FilterKey, enter the name of the field you'd like to filter by. Don't include the table occurrence name. For example you could enter AddressState1. In zulu_FilterValue, enter the value you'd like to use for this filter. For example: CA. Set up this way in our sample file, Zulu will only sync those records from California. You can use this, for example, to only sync active contacts.
Note. Do not create additional ZuluContactConfig records for the same contacts table, the way you create additional ZuluCalendarList records in calendars. There should be only one ZuluContactConfig record in your file, and only one filter. Segmenting your contacts further should be done using Groups or Access Privileges.