Events Bulk Import
Updated
by Lorena
In this guide, we explain how staff can create events in bulk with the bulk importer tool in Studio
Events Bulk Import
How to access
Under ‘Your Business’ in the left-hand navigation menu, you will see the Importer.
General
By default, the drop-down box will be populated with Events.
The ‘download templates’ button lets you download a copy of the template required for the bulk import.
The ‘upload file’ button allows you to upload a CSV to the importer to import events into JRNI.
The ‘import name’ is used to identify the import and can be anything.
The import data button becomes active once all the steps have been completed. For the file to be accepted, it must be uploaded in CSV format.
Import History List
The import history lists any previous imports uploaded using the bulk importer. The status column will display ‘completed’ or ‘completed with issue.’
The status complete is an import that has been completed with no issues, and the status completed with the issue is an import that has been completed but failed to import all events in the import list.
The import name is the name you added when you started your bulk import.
The started date is the date and time of when your bulk import started. The ended date is the date and time of when your bulk import ended.
The download button exports a list of the original import file including the event id’s of the newly imported events into the JRNI system. It is important to store the event id’s so if you need to make any changes to existing events via the bulk importer, you can do this using the event id’s.
File Format
You can download a copy of the bulk import file from here, which gives additional information about the headers in the file and what they mean. If you upload the template file from this document, remember to remove the first two lines from the template file before importing, or it will fail validation.
The mandatory fields required for the bulk import are:
- companyID (uniquely identifies the company)
- name (this is the name of the event)
Variable | What is it? | Format | Example |
templateId | Uniquely identifies a template | number | 15 |
companyId* | Uniquely identifies a company | number | 37009 |
eventId | Uniquely identifies a company (only required for an update) | number | 1234 |
name* | The name of the event | text | JRNI Event 1 |
description | Short description of the event | text | Short description |
long_description | Long description of the event | text | Long description |
spaces | Spaces available to book | number | 100 |
resource_id | Uniquely identifies a resource | number | 12321 |
detail_group_id | This is the question group ID | number | 56 |
event_group_id | Uniquely identifies an event group (child company) This is to categorize your events" | number | 356 |
global_event_group_id | Uniquely identifies an event group (parent orHQ company) This is to categorize your events" | number | 12765 |
person_id | Assign the event to staff using their id | number | 19876 |
duration | The duration of the event in minutes | number (in minutes) | 60 |
datetime | The date and time of the event | ISO format, example: 2024-01-02T08:16:35.322Z | 2024-05-02T08:00:00.322Z |
time | The time of the event | N/A | 2024-05-02T08:00:00.322Z |
price | The price of the event | number | 10 |
ticket_type | This is the type of ticket | multi_space | multi_space |
address_id | The ID of the address for the event | number | 12321 |
reference | Your unique reference id for the event chain | number | KGF1234 |
max_num_booking | Maximum number of bookings per transaction | number | 100 |
min_advance | Minimum advance time for accepting the event registration | ISO 8601 duration format | P1Y2M3DT1H30M10S represents a duration of 1 year, 2 months, 3 days, 1 hour, 30 minutes, 10 seconds |
max_advance | Maximum advance time for accepting the bookings | ISO 8601 duration format | P1Y2M3DT1H30M10S represents a duration of 1 year, 2 months, 3 days, 1 hour, 30 minutes, 10 seconds |
min_cancel | Minimum duration of time before the registration can be cancelled | ISO 8601 duration format | P1Y2M3DT1H30M10S represents a duration of 1 year, 2 months, 3 days, 1 hour, 30 minutes, 10 seconds |
repeat | How often should the event repeat | number | 0 |
imageUrl | The image of the URL hosted on the web | link to a hostage image | |
disabled | Create the event as disabled | true or false | false |
validate_availability | Validate that the staff member is available | true or false | false |
isDelete | If an event needs to be deleted | true or false | false |
