One of the event import file formats Trumba supports is the iCalendar or iCal format. iCal files have an .ics extension. For example, an iCal file might be called myevents.ics.
Tip By sending an iCalendar format file to the Trumba server through an HTTP PUT operation, you can modify existing events without duplicating them or altering other event data. Learn more.
Below is a minimal sample iCal file that can be imported to Trumba. It creates an event that occurs on January 1, 2016.
Tip By default, event metadata such as timezone is inherited from the target Trumba calendar. Optionally, you can specify time zone at the event level using the appropriate iCal syntax (e.g DTSTART;TZID).
Each imported event must have a unique ID (UID), which is how Trumba knows whether you're importing a new event or updating an existing event. Each calendar program may use a different UID format. When you import events from other calendars, your Trumba calendar retains the UIDs assigned by the original calendars.
Tip You can also create your own UIDs using any format you choose.
You can update an event by importing a new iCal file that specifies the event's UID. Because the new information overwrites all of the old information, be sure to include all necessary data fields in the new iCal file. You can delete imported events from your Trumba calendar manually or by using an HTTP PUT directive.
The following table lists fields that are required in any iCal file you import. It also lists some commonly used optional fields. In addition, the table maps the iCal fields with corresponding fields in the Trumba add/edit event form.
|Trumba Event Form||ICS File Field|
The events you're importing may include custom fields. For example, in addition to the standard event fields, such as event name, start date, and start time, each event may include custom fields such as Audience, Category, or Event Created By.
When you export events in iCal format, each template and custom field is automatically assigned a numeric identifier. These numbers provide a unique way to identify templates and fields even when template and field names change.
To successfully import custom field data, you must create a matching custom field in Trumba for each custom field in the iCal file. In addition, the numeric identifiers of the custom fields must match.
To find the numeric identifiers of the Trumba fields you create, you must set up an event in Trumba that includes the fields you're importing and export the calendar that contains the event to an iCal file.
For example, you might create a single-line-of-text field called Event Created By that contains a person's name. Or, you might create a list-of-choices field called Audience that contains a list of audience values, such as Seniors, Adults, Teens, and Children.
Tip For the easiest import, make the custom field names in Trumba match the custom field names in the file you're importing.
For example, the following line might appear in the file you exported from Trumba. The numeric identifier for a field called Comments is 10899.
In the iCal file you're importing, change the numeric identifier for each occurrence of the same custom field so it matches the numeric identifier from Trumba.
The corresponding lines in the iCal file you're importing might look like this (the numeric identifier is 5586).
In the iCal file you're importing, search for each occurrence of 5586 and replace it with 10899.
Tip When custom fields are imported, Trumba requires only a numeric identifier and field value. Field type and name are ignored. In the iCal file you're importing, you can simplify the custom field lines so they look like this:
Images are specified by URL. This can be a URL to an external image on the internet or a URL to an image previously copied into the Trumba servers using the "manage images" feature.
The following URL points to an image stored on the Trumba servers.
Tip Images you import are added automatically to the calendar's images table. Learn more about images tables.
Below are two sample iCal files with custom fields. The files each contain a record for a single event (defined by the content between the
The files also include examples of a range of Trumba Connect custom field types and an event image. The NAME and TYPE attributes have been left in the file to provide contextual information.
The second sample file shows a record for a repeating group cycling event that started on Monday, September 10, 2012 and extends until Monday, December 15, 2014. The
RRULE property defines the repeating parameters.
Tip The sample files demonstrate the use of the backslash (\) escape character in the Location, Description, and MultiLine text fields:
For example, the Description field in the first file contains this text: This event starts at 8:00 a.m. PT on Jan 1\, 2010. The backslash guarantees that the comma following Jan 1 will be interpreted as a punctuation mark rather than a delimiter.
For example, to include a backslash in Description field text, you type: Use the backslash (\\) as the escape character.
For example: This is line 1\nThis is line 2.
Different programs output iCalendar files in different ways so it's not unusual for the iCal file you're trying to import to contain content that Trumba can't interpret.
By following these troubleshooting tips, you may be able to resolve the issues and import the file.
Tip Troubleshooting iCal files can be time consuming. If you can't quickly identify the blocking issues with a file you're trying to import, it may well be faster to add events manually in Trumba.
BEGIN:VCALENDARand end with the line
BEGIN:VEVENTand ends with the line
BEGIN:VCALENDARand the first occurrence of
BEGIN:VEVENT, most iCal files contain many lines of information related to time zone and standard and daylight savings time.
For more information about iCal file structure, properties, and parameters, refer to RFC2445, the iCalendar specification.
Going event-by-event, you may be able to isolate the event where the blocking problem originates.
Tip If your file includes a large number of events, you might want to try more of a divide-and-conquer approach. First, try importing half the file. If that fails, divide that section in half, and then try importing again. And so on.
When you finish adding the representative events, export them as an ICS (iCalendar) file. By comparing this exported file to your original, you may be able to determine which aspects of the original file are causing import errors.