Creating Events via Bulk Import

There are three ways you can create events within the Scheduling system - bulk import, manually and via planning boards.

This article concerns creating events via bulk import.

To access the bulk import first scroll to the events list as shown below and press the "Import Events" button.

You'll then see the Import Events home screen as shown below - to get started you can download a blank template by clicking the "Download Template" link - this will produce a CSV file with the correct column headings for import.

Once the file has been populated you can then import it into the system by browsing using the "Choose file" button then clicking "Import" once the CSV file has been selected.

The events will then be automatically created within the system and you will be redirected to the Events listing page.

A field reference is shown beneath:-

  • label - The Event label;
  • event_type_label - The human name for the event type e.g. RDO or Inspections (NB: the Event Type must exist in the system and not be Archived);
  • planning_board_label - The name for the planning board the event is to be created on;
  • description - Free text description;
  • start_date - the event start date in DD/MM/YYYY format;
  • start_time - the event start time in HH:MM format;
  • end_date - the event end date in DD/MM/YYYY format;
  • enwl_ids - a comma separated list of ENWL employee IDs to assigned multiple staff to an event; 

Note for ENWL Ids 

Before entering values in the enwl_ids column, first set the column type to ‘Text’ – you will then be able to enter multiple id values separated by a comma (eg 111111,222222,333333), without them being converted to a long number.

  1. Generate the template from Ctrl Hub.
  2. Open the template csv file.
  3. If using Excel, before entering any values, select column H.

   4. In the formatting options, select Text.

   5. You can then save this template for future use.

   6. Once set to Text, when you type the comma separated 6-digit ids,         they will remain in the expected format.

  • end_time - the end time of the event in HH:MM format;

The following fields are optional and are for planned events:-

  • work_requestor - (For planned events) - the work requester detail;
  • address - (For planned events) - the address of the job;
  • substation_number - (For planned events) - the substation number;
  • work_instruction_number - (For planned events) - the work instruction number;
  • job_number - (For planned events) - the job number;
  • work_order_number - (For planned events) - the work order number;
  • type_of_switchgear - (For planned events) - the type of switchgear;