...
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
| Info |
|---|
An example CSV template can be downloaded by clicking the Download template button. |
Important information
You can only upload CSV files when importing data - attempting to import other file formats will cause the import to fail.
It is recommended that you import a maximum of 500 rows of data per CSV file.
If there are errors with the headers of the file, such as a header is missing or incorrectly formatted, Fuse rejects the whole CSV file and an error is shown, as follows:
If any of the rows in the CSV have incorrect or missing mandatory data, those particular rows won’t be imported and are shown in red. Only rows in the CSV with correct and complete data, shown in green, will be imported. For example, if one of the rows is missing some information related to Location, that row will be marked in red and won’t be imported:
You may need to wait a while before the import completes, especially if there is a lot of data being imported. You can check the progress of an import by refreshing the page and then checking the number of rows that have been imported so far in the Progress section. Each time you refresh the page, the number of imported rows will increase. In the example below, the total number of rows being imported is 420 but so far only 153 have been completed.
When importing data for events and occurrences that don’t currently exist in Fuse, please be aware of the following:
If the information in the event_name column differs from
the others in the CSV, a brand new event will be created with that title.
If the information in the starts_at, ends_at, or location column differs to others in the CSV, but the event_name remains the same, a new occurrence for the event will be created.
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.
| ||||
owner_id | The user ID of the event owner.
| ||||
event_name | The name of the event. For example, All employee training day.
| ||||
event_description | The description of the event.
| ||||
starts_at | The date and time the event started.
| ||||
ends_at | The date and time the event ended.
| ||||
location | The location of the event. For example, The City Conference Centre.
| ||||
advertisement_code | Unique code to identify the event (If one has been specified).
| ||||
user_id | ID of the user who participated in the event.
| ||||
pass_status | Whether or not the user attended the event. The following statuses apply:
Other status options (such as waitlisted) are not displayed.
| ||||
internal_host_id | The ID of the Fuse user hosting the event.
| ||||
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.
| ||||
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.
| ||||
creator_approval_required | Whether or not creator approval is required when users apply to join the event. This can be TRUE or FALSE.
| ||||
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.
| ||||
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.
|
...