Event CSV File Examples

When importing events, you can use multiple-file or single-file upload techniques.

Multiple Files Import

With the multiple-file approach, you use a separate file to import values for each of the following:

• The Event Body Fields

• The Attendees sublist

• The Resources sublist

• The Time Tracking sublist

The first file should include a unique identifier for the event, the event’s title, and any other needed body field values, as shown below.

You should create an additional file for each sublist you want to import. Each file should include a unique identifier that can link each sublist record to the appropriate body field values.

For example, the file representing the Attendees sublist might include columns for External ID, Attendee, Attendance Status, and Response Status.

The Resources sublist has only one field (Resource). Therefore, this file requires only two columns — one for the Resource field, and one for the unique identifier linking the sublist records to the relevant body field values.

Single File Import

With a single-file import, all data for a single event record must exist on a single row. For this reason, if the sublist data for any event must include more than one record, you must create a discrete set of columns for mapping each sublist record. For example, the following sample would create two event records. The first has four attendees (four records in the Attendees sublist), and the second has three.

If you name your columns as shown in this example, the mapping should happen automatically. If you choose column headings that do not match what the system expects, you must map the fields manually.

General Notices