Zulu 2

From 360Works Product Documentation Wiki
Revision as of 20:58, 4 March 2016 by Caleb (Talk | contribs)

Jump to: navigation, search

Zulu is an extension for FileMaker Server which runs as a standalone server application alongside FileMaker Server and lets Apple Calendar (and compatible clients) see your FileMaker table(s) as native calendars. You can manipulate your records in Calendar and when you do, you’re manipulating the FileMaker records directly: Calendar will even respect FileMaker’s record level access privileges and record locking so you can filter records based on privilege set and if someone else is editing an event when you try to do the same.

Visit the Zulu site to learn, download a demo, or purchase Zulu for your FileMaker Server.


Getting Started

Integrate with FileMaker
Integrate with Apple Calendar
Reporting a Problem
Customizing Zulu 2 behavior using the context descriptor file

Google Calendar Sync

Setting up your first sync with Google Calendar

Exchange Calendar Sync

Setting up your first sync with Exchange/Office365 Calendar

Frequently Asked Questions

If you ever run into a problem that you cannot solve, you can always contact 360Works support either by e-mail at support@360works.com or by calling our office at (770) 234-9293.

As we encounter common issues with Zulu, this section will be updated to help out future users who may encounter similar problems:

Does Zulu 2 support repeating events?
Does Zulu 2 support Google/Exchange attendees?
I don't see any calendars during configuration.
Does Zulu 2 support different time zones?
How can I publish my Zulu 2 calendars on a non-standard (not "/zulu") installation context?
I don't have Zulu 2 installed on the same machine as my FileMaker Server, how can I make it communicate with the proper server?


Events aren't syncing anymore

If you have Zulu set to Auto-Sync, error messages won't show up in the Admin Console. First step is to turn off Auto-Sync and then run a Manual Sync. You will then see the error the sync is encountering displayed. That will give you a bit more to work with when diagnosing the problem.

Common Errors

Requested minimum modification lies too far In the past

This error message occurs when too much time has past since your last sync, the only way to resolve this is to delete your sync data, then perform another initial sync. Instructions to do so can be found here: Reset Sync Data

Still no luck? Report a problem and we will take a look

Report a problem

Advanced Configuration

Filtering Events

Custom formatting data coming from Apple Calendar

Customizing what is logged in your Zulu logfile

Using Zulu with SSL

Important: Hosting Provider Installation

A hosting provider installation customizes the URL startpoint of your installation. On a default installation your local URL will look like "", but a hosting provider installation allows you to customize the start point. For example, you could set it to "". This feature also allows you to run multiple installations side by side. During the install this is set by the "application name" popup.

If you choose to do a hosting provider installation, please keep in mind you will need to customize your publish script in FileMaker to include this new URL startpoint. In Zulu 2.07 and earlier, please follow these instructions. For Zulu 2.08 and later, you can customize the startpoint by modifying the "$ZuluApplicationName" variable in the publish script.

Known Issues

Known Issues

Personal tools

Plug-in Products
Other Products