Zulu 2 Attendees
From 360Works Product Documentation Wiki
(Difference between revisions)
(Created page with "Yes. Zulu 2 introduces the ability to sync attendees between FileMaker Server and Google or Exchange/Office365. Due to the flat nature of an events layout, attendees have to ...") |
|||
| Line 1: | Line 1: | ||
| − | + | Zulu 2 introduces the ability to sync attendees between FileMaker Server and Google or Exchange/Office365. | |
Due to the flat nature of an events layout, attendees have to be stored in a particular fashion. Attendees must be stored in a return separated list of values and they can be formatted one of three ways: | Due to the flat nature of an events layout, attendees have to be stored in a particular fashion. Attendees must be stored in a return separated list of values and they can be formatted one of three ways: | ||
Revision as of 17:49, 28 July 2015
Zulu 2 introduces the ability to sync attendees between FileMaker Server and Google or Exchange/Office365.
Due to the flat nature of an events layout, attendees have to be stored in a particular fashion. Attendees must be stored in a return separated list of values and they can be formatted one of three ways:
- "First Last<email@address.com>"
- "<email@address.com>"
- "email@address.com"
Zulu will write attendees back to FileMaker in the format "First Last<email@address.com>" if a display name is given, otherwise they will appear like this "<email@address.com>"
