Common import errors

Application Scope: CORE

Problem

Nightly data import has failed, generating an error log.

Cause

Multiple possible issues - error describes the problem.

Solution

Errors can occur from a discrepancy between the Payroll system you are importing from and the state of the data in ClientSpace. Some of the most common errors are as follows.

• Most commonly occurs when the Client record is terminated in the Payroll system prior to being terminated in ClientSpace. A best practice is to begin the termination process in ClientSpace to utilize the workflow within the application.

Error on data row ###: ClientSpace.PEO.Import.ClientMaster.GetOtherData(): No record found for ClientNumber ####.

• After the initial Company import, the process merely updates records and will not insert new records. This error means a Client Number exists in the payroll system that does not exist in ClientSpace.  Set up a stub Org/Workspace record for this Client Number and the next import will synch up the data.

Error on data row ###:  ProjectID #### is associated with a workspace that does not allow imports.

• During pricing when the Contract Status changes to "Client" as part of the normal workflow, many things are updated behind the scenes by business logic. One of these is a flag on the Projects table to "AllowImport". This error occurs because the Client has been moved to Client Status in Summit/APEX but still has not been completely processed through Pricing in ClientSpace.  It is recommended that you move each of these workspaces through Pricing to allow the AllowImport flag to be properly set. If due to the sheer number of records in this state this solution is not practical, log an Extranet case to see if a scripted solution can be created to place the records in a state where the import can be processed.**
  

CAUTION:  Repercussions ** There will be repercussions if Workspaces are not allowed to proceed through the normal pricing process. When a workspace is in "Client" Status, the system assumes that any pricing generated is a Re-price and not an RFP. This means that workflow and functionality associated with RFP pricing such as Underwriting Approval workflow and other pricing functionality such as comparison batches are likely affected. To discuss the downstream effects of making scripted changes, log an Extranet case before requesting such changes. 

Location Import

Business Logic Errors for data row ###:   - There is already a Primary location for this client

• Two Location records on the import file for the same Client Workspace are being set as the Primary location. This normally happens if the Primary flag is set on more than one record, or multiple locations share the same address as the main Client Address. Update the payroll system to correct this issue and re-run the import.

Employee/Employment Import

The value (##-#######) in the "EmployeeID" column did not produce a valid lookup for data row #. The value (##-#) in the "ClientLocationID" column did not produce a valid lookup for data row #.

• Both these errors are commonly caused by a failure in the Company Import, as the ClientNumber doesn't exist, causing a snowball effect on the downstream imports such as Contact, Location, Employee, Employment and Voucher.

The following error(s) were found in your submission: An active Employee record already exists for this Identifier.(PrismHR API)

• This error only occurs with employees who work in multiple client companies. The PrismHR system stores the Employee ID at the person level, so an employee can have the same Employee Identifier associated with multiple Client IDs. ClientSpace handles this by concatenating the Client Number and EmployeeID on the ImportID for the employee record - so 00395-Y14526. If this ImportID was not properly set for some reason the system will be unable to find a unique match and will throw this error.

Unable to include Queue Record in Import file, Employee 'R40816-000386' cannot be located in HRP /PrismHR (HRP error - Employee import PrismHR error - Employment import) (PrismHR API)

• This error commonly occurs due to bad data in the PrismHR system - often the data does not appear bad, but when viewed by PrismHR directly in the database there are bad values stored in one of the fields - this most often occurs with date fields or specialty fields such as SSN. Contact PrismHR and create a support case. Make sure to include the record information such as Client ID and employee ID when logging your case with PrismHR.

Invalid Lookup Error logging

When ClientSpace encounters a lookup error during import, the system displays a message that indicates whether the import was successful (allowed) or if the import failed (not allowed).

• If the Allow Invalid Lookup Values option is selected and the import encounters an error with a lookup value, the error message indicates that the import was successful (was allowed). For example:

  [01/13/21 15:49:16][509] No lookup mapping: Group:YesNo Code:T Column:YN2 Row:1. Import will continue for this Row.

• If the Allow Invalid Lookup Values option is NOT selected and the import encounters an error with a lookup value, the error message indicates that the import failed (was NOT allowed). For example:

  [01/13/21 15:48:22][509] Error on data row 1: No lookup mapping: Group:YesNo Code:T Column:YN2 Row:1. Import has failed for this Row.

Errors common to all imports

The value (####) in the "ClientNumb" column did not produce a valid lookup for data row ###.

• This error means a Client Number exists in the payroll system that does not exist in ClientSpace.  Set up a stub Org/Workspace record for this Client Number and the next import will synch up the data.

Error on data row #: Row #: ProjectID #### is associated with a workspace that does not allow imports. 

• 'AllowImport' flag is set to 'No'. By default, after workspace creation the 'AllowImport' flag is set to 'No' until the Workspace achieves 'Client' status at which time it flips to 'Yes'.  The Client exists in the payroll system, but the Client Workspace is not yet a Client.  Update the Client workspace to 'Client' status and re-run the import to synch up the data.

ERROR: Row column count is not equal to the expected count for data row ####

• The report that produces the import file is not properly quote wrapping empty values, resulting in less columns in the data row than are expected from the header column count. Fix the report to properly quote warp and comma separate the NULL data.

 ERROR:  Object reference not set to an instance of an object. For any other questions regarding Import configuration and errors, log an Extranet case.

• One of the key data values used to match the record in ClientSpace such as ImportID does not match the expected value - the system found a workspace, but not the ImportID that your file has associated hence the invalid object reference.  Fix the report to properly match the key data value to the expected value.

- Rows Skipped - Dataform Insert or Update not Allowed:  ####

• The number or rows (####) were skipped because they did not meet the Insert/Update/Both criteria - for example you have 2000 records in the file, but 1800 of them exist in ClientSpace and the import is configured as Insert Only - the error message would read - Rows Skipped - Dataform Insert or Update not Allowed:  1800

Note:  ** There is a known issue with the Error logging on Contact Imports. This error log reports '0 Records updated' even though updates are occurring. Records with errors are reported correctly in this log. This issue is scheduled to be fixed in an upcoming sprint. Until this time, you should spot-check the Contact records after import to ensure records that do not show as having import errors are being updated correctly.