What are the contents of the different CSV Templates?
Each of the Templates has it's own unique set of attributes and associated validation rules. These are explained by CSV Template name. They can be viewed
The first row of the CSV file must contain the column headings.
When the import process runs, the following validation will be applied:
-
Pay Code - Must be valid and the correct length (one of either Pay Code or PIN must be used as the identifier)
-
PIN - Must be valid and the correct length (one of either Pay Code or PIN must be used as the identifier)
-
Holiday Start - In format DD-mmm i.e. 01-Jan
-
Unit of Measure - Must be DAYS or HOURS (can be mixed within the same import file)
-
Entitlement - Numeric value to one decimal place
The first row of the CSV file must contain the column headings.
When the import process runs, a large amount of validation will take place before any data is imported.
This is detailed below.
-
SIN – Must be valid and correct length
-
EffectiveDate – Must be greater than the latest contract effective date that already exists for the site
-
DayNumber – Must be between 1 and 7 (1 = Sunday and 7 = Saturday)
-
SlotNumber – Must not be greater than the maximum number of slots as defined in the system settings
-
StartTime – Must be a valid time in the format “HH:mm”
-
FinishTime – Must be a valid time in the format “HH:mm”
-
HourType – Must match to the hour type code of an existing hour type
-
PayLevel – Can be left empty, but if used, must match to the pay level code of an existing pay level
-
PIN – Can be left empty, but if used, must match to an existing valid PIN and be the correct length
-
UnPaidMB – Can be left empty, but if used, must be a valid time in the format “HH:mm”
-
UnBilledMB – Can be left empty, but if used, must be a valid time in the format “HH:mm”
-
FlexibleShift – Must be “ ”, “Y” or “N” (“ ” will be interpreted as “N”)
-
CompleteBy – Can be left empty, but if the previous column is “Y”, then a valid time must be supplied in the format “HH:mm”
Any blank lines in the CSV file will be ignored
The first row of the CSV file must contain the column headings.
When the import process runs, the same validation as the standard Contract Times Import is run.
In addition; Post Name, Slot Identity and Area must each be 25 characters or less.
Only one entry of the Slot Names is allowed per Slot Number. Empty or Duplicate Slot Names are ignored. for example For Site A, Slot 1 is Guarding Posts, Day Slots. The Area will be defaulted to Area 1 and there may not be any different entries for Site A, Slot 1 for the same effective date. There may be blank entries, or entries that read identical
The first row of the CSV file must contain the column headings.
When the import process runs, the following validation will be applied:
-
SIN – Must be valid and correct length
-
Enable Bank Holiday Contract - Must be “ ”, “Y” or “N” (“” will be interpreted as “N”)
-
Default Stand-down – Must be “None”, “Scheduled” or “All Staff”
-
Holiday Date – Must be a valid date matching either a Site Group Holiday or Branch Holiday, depending on how the Site Group is configured. Must not be a date in the past. The current date and any date in the future is valid.
-
Enable - Must be “ ”, “Y” or “N” (“ ” will be interpreted as “N”)
-
Stand-down – Must be “Default”, “None”, “Scheduled” or “All Staff”
For a single site, the Enable Bank Holiday Contract and Default Stand-down must be the same. Holiday Dates must not be repeated for the same site
The first row of the CSV file must contain the column headings.
When the import process runs, the following validation will be applied:
-
Site Identification (Site Code. This is used to identify the site the budget is for) - Text format, one of SIN, Site Code, External Reference, Source ID (Public Table) - set based on company needs. By default it is set to SIN.
-
Budget Date (Day on the budget) - Date format, check to see valid The specified date will be the date for the budget import. There must not be duplicate lines for the same site and same date within the CSV.
-
Hours (Sum of Total Hours. This is the budget hours for the Day) - Numeric format, check to see valid
-
Amount (Sum of Total Budget. This the total momentary value of the budget for the Day) - Numeric format, check to see valid
The first row of the CSV file must contain the column headings.
When the import process runs, the following validation will be applied:
-
Site Identification (Site Code. This is used to identify the site the budget is for) - Text format, one of SIN, Site Code, External Reference, Source ID (Public Table) - set based on company needs. By default it is set to SIN.
-
Budget Date (Week Commencing Date on the budget) - Date format, check to see valid. The specified date must be the start date of the week for that site card. It will import the budget for that whole week. The individual days will have the budget evenly spread throughout the 7 days, with any extra going towards the first day. There must not be duplicate lines for the same site and same week within the CSV
-
Hours (Sum of Total Hours. This is the budget hours for the week) - Numeric format, check to see valid
-
Amount (Sum of Total Budget. This the total momentary value of the budget for the week) - Numeric format, check to see valid
CSV Standards for Imports
New Import CSVs should follow this format:
-
Each record is located on a separate line
-
The first record should be the header record
-
Each record contains the same number of comma-separated fields
-
Any field may be quoted with double quotes
-
Fields containing a line-break, double-quote or commas should be quoted
-
A double quote character in a field must be represented by two double quotes
Examples:
-
“Post for Guards L1, 2 and 3”
-
“Post for Guards
-
L1, 2 and 3”
-
“Post for ““extra”” Guards” (will be interpreted as: Post for “extra” Guards)
Note: These standards do not apply to the standard Contract Times Import (available in V15.1 onwards) as it is not designed to parse such documents.
When saving from a spreadsheet (such as Microsoft Excel), saving as a CSV file should automatically apply this formatting.
TIP: See also: https://www.ietf.org/rfc/rfc4180.txt for further information about CSV files.