Importing Block Events
You can create multiple events for a block by
importing event data using the Block_Events.csv template file available for download. Once the events are imported
regular event management capabilities are available.
Note:
Data transformation is not available using this method; as such the data in the import data files must match the current OPERA Cloud property configuration.-
The Rental Code will always be "CUSTOM" for EVT_Rental_Amount.
-
Master event must be listed before sub events (Available when the Sub Event OPERA Control is active)
-
Alternate space events must be listed after primary event (Available when the Alternate Space OPERA Control is active).
-
Events won't be imported to Out Of Order function space.
-
Return to Inventory status events should not be imported for blocks.
| Column | Description | Max Data Length | Sample Data | Mandatory |
|---|---|---|---|---|
|
EVT_Unique |
Unique ID value for event in the uploaded csv file |
200 |
Ex: (5010, 5011) |
|
|
EVT_Block_ID |
The Business Block ID (not Block Code). |
200 |
Ex: (290873) |
|
|
EVT_Type |
The Event Type of the event. |
8 |
Ex: (MTG) |
|
|
EVT_Name |
The Event Name of the event. |
60 |
Ex: (Meeting) |
|
|
EVT_Status |
The Event Status of the event. If no value is provided, the status is inherited from the block Catering Status or the block Room Status when the Use Single Block Status OPERA Control is active. |
8 |
Ex: (INQ) |
|
|
EVT_Start_Date |
The Event Start Date. The format must be 'YYYYMMDD.' |
DATE |
Ex: (20210121) |
|
|
EVT__End_Date |
The Event End Date. The format must be 'YYYYMMDD.' |
DATE |
Ex: (1500) |
|
|
EVT_Start_Time |
The Event Start Time. The format must be 'HH24MI.' |
TIME |
Ex: (1500) |
|
|
EVT_End_Time |
The Event End Time. The format must be 'HH24MI.' |
TIME |
Ex: (1500) |
|
|
EVT_Expected_Attendees |
The expected number of people attending the event. |
NUMBER |
Ex: (20) |
|
|
EVT_Guaranteed_Attendees |
The guaranteed number of people attending the event. |
NUMBER |
Ex: (15) |
|
|
EVT_Space |
Assigned function space for the event |
8 |
Ex: (CORA) |
|
|
EVT_Shareable (YN) |
This column indicates whether a shareable function space would be booked as Exclusive or Shareable. This field should be populated for a shareable function space only. |
BOOLEAN |
Ex: (Y) |
|
|
EVT_Master_YN |
This column indicates if the event is a master event. This field should be populated if Master/Sub/Alternate events are being imported. |
BOOLEAN |
Ex: (N) |
|
|
EVT_Master_Event_Link_ID |
Linked Master Event ID. This column must be populated if Master/Sub/Alternate events are imported. |
200 |
Ex: (5012) |
|
|
EVT_Link_Type |
Event link type (must be populated if Master/Sub/Alternate events are imported)
|
20 |
Ex: (ALTERNATE) |
|
|
EVT_Setup_Style |
Function Space Setup. This column should be populated when "EVT_Space" is provided. |
8 |
Ex: (CONF) |
|
|
EVT_Setup_Time |
Setup time in minutes. |
NUMBER |
Ex: (15) |
|
|
EVT_Tear_Down_Time |
Teardown time in minutes. |
NUMBER |
Ex: (15) |
|
|
EVT_Rental_Amount |
Rental Amount for the event. |
NUMBER |
Ex: (105) |
|
|
EVT_Display_Doorcard_YN |
Display Doorcard Y/N. |
BOOLEAN |
Ex: (Y) |
|
|
EVT_Doorcard |
Doorcard Signate text |
50 |
Ex: (Adam's and Jill's Reception) |
|
|
EVT_Loud_Event (YN) |
This column indicates if event is a noisy event. |
BOOLEAN |
Ex: (N) |
|
|
EVT_Do_Not_Move (YN) |
This column indicates if the event is Do Not Move status. |
BOOLEAN |
Ex: (N) |
|
|
EVT_NOTE1 |
Event Note 1. |
2000 |
Ex: (Guest book at Entrance) |
|
|
EVT_NOTE2 |
Event Note 2. |
2000 |
Ex: (Guest book at Entrance) |
|
|
EVT_NOTE3 |
Event Note 3. |
2000 |
Ex: (Guest book at Entrance) |
|
|
EVT_Forecast_Revenue_YN |
This column indicates that only the forecasted values will drive reporting revenue (even though resources may be booked). |
BOOLEAN |
Ex: (N) |
|
|
EVT_Forecast_Revenue_Type_1 |
The Forecast Revenue Type 1 of the event. |
8 |
Ex: (BEV) |
|
|
EVT_Forecast_Total_Revenue_1 |
The Forecasted Revenue 1 of the event. |
NUMBER |
Ex: (20) |
|
|
EVT_Forecast_Revenue_Type_2 |
The Forecast Revenue Type 2 of the event. |
8 |
Ex: (FOOD) |
|
|
EVT_Forecast_Total_Revenue_2 |
The Forecasted Revenue 2 of the event. |
NUMBER |
Ex: (30) |
|
|
EVT_Forecast_Revenue_Type_3 |
The Forecast Revenue Type 3 of the event. |
8 |
Ex: (RENTAL) |
|
|
EVT_Forecast_Total_Revenue_3 |
The Forecasted Revenue 3 of the Event. |
NUMBER |
Ex: (100) |
|
|
EVT_Forecast_Revenue_Type_4 |
The Forecast Revenue Type 4 of the Event. |
8 |
Ex: (MISC) |
|
|
EVT_Forecast_Total_Revenue_4 |
The Forecasted Revenue 4 of the Event. |
NUMBER |
Ex: (25) |
Preparing Event Import Data Files
-
From the OPERA Cloud menu, select Bookings, select Blocks, then select Manage Blocks.
-
Enter search criteria, then click Search.
-
Select the block in the search result, then click I Want To . . and select Events from Import.
-
Click Download Templates to download a templates.zip file to your workstation.
-
Extract the Blocks_Events.csv file for update
-
For more information, see Using Data Import
-
Uploading, Validating and Importing Data Files
-
From the OPERA Cloud menu, select Bookings, select Blocks, then select Manage Blocks.
-
Enter search criteria, then click Search.
-
Select the block in the search result, then click I Want To . . and select Events from Import.
-
Upload and validate the data files.
-
Import the validated data .
-
For more information, see Using Data Import
-
Related Topics
Parent topic: Events