Import Errors and Explanations

Placement with ID [X] has existing shifts outside its date range

[shifts: 15/12/2016 to 15/12/2016, placement: 18/12/2016 to 25/12/2016]

Found more than one existing client with frontend ref aaaaaa

Reason 1

The Placement on InTime has Client Ref of aaaaaa but the import file has a Client Ref of bbbbbb i.e. the reference codes are different. The error is caused because the import is trying to move the Manager to a different client which is not allowed. To resolve the issue update the Client in Salesforce to have the same reference as InTime.

Reason 2

Client RefCode generator has been enabled. If it has this would cause an ItrisId to be assigned to the Client on import rather than applying the one from the import file. As the generator does not increment from an import the next Client would be assigned the same ItrisId. This is likely to be a rare occurrence. Request the support team (support@in-time.co.uk) check this.

Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1

Cannot change client from X to Y - changing the client of an existing placement is not allowed

Reason 1

Check the BANK ACCOUNT NAME. If it is more than 30 chs long then amend the account name and re-import. If the account name is 30 chs or less then log a call with support (support@in-time.co.uk) to investigate further.

Reason 2

Case 55361

Please ensure that you always have an email for a worker as it is mandatory for InTime. We suggest that your front-office system should enforce this field, either on entry or before export to InTime.

Check InTime to confirm if the update has occurred or not. If it hasn't then rerun the import. If the issue re-occurs and/or the record has not updated then log a case with Support via support.in-time@rsmuk.com.

This means the CSV file doesn't have the same amount of columns as InTIME is expecting.

Usual reasons:

Reason: There is probably a new-line character in one of the fields in your input file. This is often an address field.
Resolution: You need to check the CSV file which was uploaded to InTime and identify the field with a new line character. Once you have found this then correct your data in your front-office system and re-send the placement. You should raise a request with your front-office system to remove new line characters from any field in file sent to InTime.

Reason: You have added a column to the CSV data and not advised InTIME support to amend the importer configuration to match.
Resolution: Contact support and ask for your import specification to be modified. There may be a charge associated with this.

The Split Consultant either needs to be amended on the import file or set up on InTime

The Consultant must exist on InTime before the split can be imported.

Rejecting because the payroll cannot be found.

Case 55361

Cannot parse 'Rate Period' column [141] - value [Standard] as decimal number (Unknown Rate Period Name: Standard)

Case 62693

Placement with ID [3198] has no default rate [STD]

Case 62693

1. Related to an incorrect configuration for the values -

   import.placement.rate.timesheetFields.tickbox/decimal/hourly.notime/hourly

1. Check the terms type of the Client in Bullhorn. The error indicates this is missing.
2. Potential issue with rates (Case 89840). No pay or charge values when a valid rate exists

Create:Customisation error: For input string: "Umbrella Company Name"

Case 61808

Unable to import: No rates configured for this placement (Custom Object 2)

Error importing placement: not-null property references a null or transient value: com.ipfour.intime.model.Rate.job

The Bullhorn->InTIME integration always needs a manager, whether a PERM placement or not. There are no email communications sent on a PERM placement when it’s imported but most clients add the Sales Manager to the Manager mapping for PERM placements just so that is seen. The manager needs to be from the client as this is where the client for the placement is mapped from the client of the manager.

1. Check the pay element in the Bullhorn config list aligns with what has been defined in InTime

Error: Row (851) Col (3) Column [Job Title] cannot be empty for Placement:

Placement: ID=null RefCode=null Frontend ref=16162

 Worker="Agency Name": 3121 (Worker Name)

Manager="Agency Name": 13170 (Manager Name)

Placed on 2016-04-25 Starting Unknown Finishing Unknown;

Row (852) Missing or invalid preceding placement row for rate row;

Row (853) Missing or invalid preceding placement row for rate row

Placement with ID [X] has existing shifts outside its date range

[shifts: 15/12/2016 to 15/12/2016, placement: 18/12/2016 to 25/12/2016]

Log a support call - support.in-time@rsmuk.com

The Split Consultant either needs to be amended on the import file or set up on InTime

The Consultant must exist on InTime before the split can be imported.

This means the CSV line doesn't have the same amount of columns as InTIME is expecting.

Usual reasons:

Reason: There is probably a new-line character in one of the fields in your input file. This is often an address field.
Resolution: You need to check the CSV file which was uploaded to InTime and identify the field with a new line character. Once you have found this then correct your data in your front-office system and re-send the placement. You should raise a request with your front-office system to remove new line characters from any field in file sent to InTime.

Reason: You have added a column to the CSV data and not advised InTIME support to amend the importer configuration to match.
Resolution: Contact support and ask for your import specification to be modified. There may be a charge associated with this.

This means the Payment terms template on the LTD company worker doesn't match one configured in Administration->Payment Terms (Self Bill Invoice Type)

Resolution: Ensure that the name matches between your front-office and InTime.

Placement with ID [X] has existing shifts outside its date range

[shifts: 15/12/2016 to 15/12/2016, placement: 18/12/2016 to 25/12/2016]

Row (1) Unexpected row identifier [PLA_LINE_ID] (all rows should start with 'P' or 'R'

Row (3) Placement X: Col (1) Unexpected row identifier (all rows should start with 'P' or 'R')

Row (4) Placement X: Col (1) Unexpected row identifier [RAT_LINE_ID] (all rows should start with 'P' or 'R')

Potentially multiple reasons for this error:

Reason 1

The import is trying to update a Placement (610728) that does not exist in InTime. This may be preceded by an error detailing why the Placement failed to import.

This means the CSV file doesn't have the same amount of columns as InTIME is expecting.

Usual reasons:

Reason: There is probably a new-line character in one of the fields in your input file. This is often an address field.
Resolution: You need to check the CSV file which was uploaded to InTime and identify the field with a new line character. Once you have found this then correct your data in your front-office system and re-send the placement. You should raise a request with your front-office system to remove new line characters from any field in file sent to InTime.

Reason: You have added a column to the CSV data and not advised InTIME support to amend the importer configuration to match.
Resolution: Contact support and ask for your import specification to be modified. There may be a charge associated with this.

This means the Payment terms template on the LTD company worker doesn't match one configured in Administration->Payment Terms (Self Bill Invoice Type)

Resolution: Ensure that the name matches between your front-office and InTime.

Case 56886

Cannot change client from X to Y - changing the client of an existing placement is not allowed

Failed to read placement with ID AAAAAAAA (BBBBBBB). Error:org.springframework.dao.DataIntegrityViolationException: not-null property references a null or transient value: com.ipfour.intime.model.Rate.job; nested exception is org.hibernate.PropertyValueException: not-null property references a null or transient value: com.ipfour.intime.model.Rate.job

Developer fixed by adding the following placement script:

 placement.rates.eachWithIndex { rate, index ->

    rate.job = placement.agency.jobs.first()

    rate.setTimePattern(placement.agency.findTimePatternByCode("DEFAULT"))

    rate.setPriorityOrder(index)

}

Failed to read placement with ID 116683414345 (1325768)

Error:com.ipfour.intime.imports.ImportException: Cannot import placement: The field com.ipfour.intime.model.Placement.defaultRate cannot be null

The ID (116683414345) cannot be searched for so search for the Ref ID (1325768). Contact Bond support on how to do this.

 This error means that there isn’t a rate on the placement so it cannot set a default.

Placement with ID [X] has existing shifts outside its date range

[shifts: 15/12/2016 to 15/12/2016, placement: 18/12/2016 to 25/12/2016]

This means the Payment terms template on the LTD company worker doesn't match one configured in Administration->Payment Terms (Self Bill Invoice Type)

Resolution: Ensure that the name matches between your front-office and InTime.

A manager with reference MANAGER already exists in InTime but they are associated with a different client to that in your import file. In InTime you cannot have a manager associated with more than one client at a time. For example, your manager may already by associated with Client A but your import file now states that the manager workers at Client B.

Resolution: You can resolve this issue by creating a new manager record in your front-office system

Each row in the import file must begin with a P or R. This line in your import file begins with something else.

Usual reasons:

Reason: There is probably a new-line character in one of the fields in your input file. This is often an address field.
Resolution: You need to check the CSV file which was uploaded to InTime and identify the field with a new line character. Once you have found this then correct your data in your front-office system and re-send the placement. You should raise a request with your front-office system to remove new line characters from any field in file sent to InTime.

Import from Bullhorn

Bullhorn Update Failure: For input string: "ESERVE"

Case 52513

import.placement.rate.timesheetFields.tickbox/decimal/hourly.notime/hourly