Importing shifts into Ento can be a useful way to work with a large number of shifts
Core HR > Account Data > Import Data
To start a new file import, go to Core HR > Account data > Import data and click Create new.
Open the Type dropdown list and select ‘Shifts’.
The purple bar under the file selection will then update to include a ‘Click here’ link for downloading a CSV template that includes all the fields necessary to get importing.
More general information on preparing import files can be found in Importing data overview.
Shift import requirements
The import will require shift date, label, type, and Role ID, as indicated by the asterisk* in the field header of the CSV template file.
Other data can be included, but is not required:
- Shift ID (if generated in another system, otherwise leave blank)
- Staff ID
- Shift start time
- Shift end time
- Break length
- Break start time
Once you have created your import file, use the File ‘Select’ button to select your file for uploading. Only the ‘Create’ mode is available for shift file imports.
Shifts imported into a date range not covered by an existing roster (featuring the location containing the shifts role) will be ignored.
Shifts imported into date ranges that are covered by existing published rosters will be automatically marked as published and accepted by any allocated staff.
The most common reason for file import failure is not customising the date field format to YYYY-MM-DD.
Double check Role IDs, and ensure the Type is ‘shift’ for regular shifts (may be on call or call out if these shift types are used in your account).
For error troubleshooting and more on file import types and modes, check out the Importing data overview article.
You can export shifts from an existing roster, which uses the Custom shifts CSV format. This will allow you to work with your data in a spreadsheeting program before creating a new Shifts.CSV import file.
Use the tips on creating a Export templates – Custom shifts CSV template, and check you have the fields required for the shifts import:
Shift import requirements
|Column||Field Name||Data Type||Length Limit||Example||Description|
|A||ID||String||SH0001||A unique identifier for the %shift% record. An ID can be comprised of text and/or numbers up to 20 characters in length.|
|B||Date*||Date||2014-11-05||The date the shift starts on.|
|C||Label*||String||09:00-17:00||This is the actual name of the shift, as it will appear on your %roster% and in communication.|
|D||Type*||Reference||shift||The type of shift. A 'shift' shift is the most common and what new shifts default to. An 'on call' shift can be rostered then clocked into any time by the staff - creating a call out which you can add special loadings to.|
|E||Role ID*||String||RO10001||Must match a predefined, non-deleted role ID that belongs to an area that is covered within a roster for the date.|
|F||Staff ID||String||ST10001||Must match a predefined, non-deleted staff ID, or be left blank (unassigned).|
|G||Start time||Time||09:00||The shift's start time, in HH:MM format. Mandatory if a matching shift label is not found, ignored if it is.|
|H||End time||Time||17:00||The shift's end time, in HH:MM format. Mandatory if a matching shift label is not found, ignored if it is.|
|I||Break length||Number||3,0||30||The length of the shift's break (in any), in minutes. Must be shorted than the length of the shift. '0' or an empty field is treated as no break. Ignored if shift label is found.|
|J||Break start||Time||13:00||The start time of the break (if any), in HH:MM format. Must fall between the start and end time of the shift and fit the break. If left blank or break length won't fit before the end of the shift, break start will be put in middle of shift.|
* Mandatory 1 Enterprise Only