The Events tab allows admins to bulk-import event records to Fuse using a CSV file.
This events import functionality allows admins to:
Create new events and occurrences in Fuse and bulk add users to them
Bulk import data for existing events and occurrences in Fuse, such as adding users to existing events
An example CSV template can be downloaded by clicking the Download template button.
Important information
It is recommended that you import a maximum of 500 rows of data per CSV file.
If the information imported from the CSV file does not precisely match the event details, including spelling and capitalisations, a new event occurrence is created.
If there are errors with the headers of the file, such as missing headers or spelling errors in headers, Fuse rejects the whole CSV and an error is shown, as follows:
If any of the rows have incorrect or missing data, those rows in the CSV will not be imported and are shown in red. Only correct and complete data, shown in green, will be imported:
CSV headers
The CSV file must contain all the following header labels, even where the data is optional:
Header | Data |
|---|---|
community_id | The ID of the community in which the event exists. This data is mandatory. You can obtain a community's ID by viewing the URL of the community homepage.
|
owner_id | The user ID of the event owner. This data is mandatory. A user's ID is visible in the URL of their Personal settings page: |
event_name | The name of the event. For example, All employee training day. This data is mandatory. |
event_description | The description of the event. This data is mandatory. |
starts_at | The date and time the event started. This data is mandatory. Date and time must be in following format: DD-MM-YYYY HH:MM For example, 01-01-2019 20:20. |
ends_at | The date and time the event ended. This data is mandatory. Date and time must use the following format: DD-MM-YYYY HH:MM For example, 01-01-2019 20:20. |
location | The location of the event. For example, The City Conference Centre. This data is mandatory. |
advertisement_code | Unique code to identify the event (If one has been specified). This data is optional. |
user_id | ID of the user who participated in the event. This data is mandatory. A user's ID is visible in the URL of their Personal settings page: |
pass_status | Whether or not the user attended the event. The following statuses apply:
Other status options (such as waitlisted) are not displayed. This data is optional. For this status to be displayed, the Enable pass & fail for this course option must be enabled, in the Advanced options section of the New event screen. |
internal_host_id | The ID of the Fuse user hosting the event. You only need to enter this data if your event has an internal host. |
external_host_name | The name of the external user hosting the event. This is someone who does not have a user account in Fuse. For example, David Johns. You only need to enter this data if your event has an external host. |
external_host_email | The email address of the external user hosting the event. This is someone who does not have a user account in Fuse. For example, david.johns@email.com. You only need to enter this data if your event has an external host. |
creator_approval_required | Whether or not creator approval is required when users apply to join the event. This can be TRUE or FALSE. This data is optional. |
manager_approval_required | Whether or not a user must seek approval from their manager before being able to join the event. This can be TRUE or FALSE. This data is optional. |
specified_approval_required | Whether or not a specified Fuse user (who is not the event owner or the user's manager) must give permission for a user to join the event. This can be TRUE or FALSE. This data is optional. |
To view imported events, either:
Under Events import info, click the name of the CSV file.
Under CSV, click the Download button.