-
Type:
Bug
-
Status: Closed
-
Priority:
Medium
-
Resolution: Cannot Reproduce
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Environment:Production
-
Bug Severity:Medium
-
Module:BenAdmin - Import
-
Reported by:Client
-
Company:Ashgrove
-
Item State:Development - On Hold
Hi,
Per the client:
Ashgrove is Reinforced Earth
Something still isn’t working in production for this group. I just tried to import employee records using the “Employee Import” template In group Reinforced Earth, but all 733 records are erroring out with “Error(s): Total fields in file does not match total number of fields in template.”, but both the file and the import template have 33 fields in each record. If I look in the “Bad File” viewer, all the fields are there and in the correct order. Can you take a look & see why they’re generating errors?
The original ticket for this issue is WT-11702.
Thank you,
Kira Hamilton
Debbie Kulling
This was not an issue, it has been fixed through customization.
Regards,
Satya Prakash
Cc: Jennifer Reed Samir Rakesh Roy Rakesh Shahane Gaurav Sodani
Hi,
I know that you said the issue has been resolved however, the client is still having issues. Please see attached email with a print screen.
Per client: When I try to delete everyone & reload, it runs for a while & then I get the following error: (see attached email). Despite the error, 728 of the 733 records load (which is expected – 5 of them have bad Class 2’s). They all have an error of “Error(s) : Invalid Record: Person already exists in the database.”, but now I still have the issue we had in Stage where 150 people are not getting core coverages allocated.
Thank you,
Kira Hamilton
Debbie Kulling
FYA.
Hi Kira Hamilton,
The provided screenshot says all 733 records are sent to bad. This was with error "Error(s) : Invalid Record: Person already exists in the database." because "Initial Load" flag is set to Yes.
When the file was loaded first time, 728 employees were loaded successfully, second time all went to bad as they already existed in system.
About Core coverage:
The backend routine (includes Core plan allocation and Eligibility routine) was executed successfully after Import. We tried this on HSPL copy of the company and the backend routine was successful.
It will help us if you provide examples of such employees. We'll investigate if the employee is eligible in plan and still sis not get the Core plan.
Please see Suraj Sokasane's comments
Hi Kira Hamilton,
Any updates on this?
Kira Hamilton: Please let us know in case you have more updates on this.
Regards,
Satya Prakash
Hi Kira Hamilton,
Please find 3C's as below.
Concern: Total fields in file does not match total number of fields in template
Cause: We have checked template Employee Import and found that the field which is mapped to WorkAround is no more present in the system due to which the error is occurring.
Correction: We have removed the mapping of field WorkAround, This will not cause for an issue in future.
Please let us know if you required more details on this.
CC-Suraj Sokasane, Umesh Kadam, Amruta Lohiya, Satya, Samir