-
Type:
Bug
-
Status: Closed
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Module:BenAdmin - Import
-
Reported by:Harbinger
-
Item State:LB QA
1)Login with Partner on Lb
2)Select and Search for company
3)Go to import/Export
4)Create spouse template->Browse the file for spouse template->Import getting fail
5)create emergency template->Browse the file for emergency contact->Import getting fail
6)create beneficiary template->Browse the file for beneficiary import->File went to bad with "plan design does not exists"
Expected Result:Import should be done successfully and beneficiary import should be done successfully
Actual Result:Import getting fail for salary and spouse import and issue with Plan design identifier for beneficiary import.
Emergency contact:
ErrorID : 0
ErrorSource : ControllerAppTier.SaveAndGetData->WORKTERRAControllerAppTier.SaveAndGetData->ExecuteImportDTS.ImportData_Isolated->WTIsolatedRoutines.Main->ExecuteImportDTS.ImportData->ImportValidation.ImportData->ImportValidation.ProcessImportDataFile->ImportValidation.ValidateAndInsertData->ImportValidation.ExecuteAllQueries
ErrorMessage: Violation of UNIQUE KEY constraint 'IX_Employee_Emergency_EmployeeID'. Cannot insert duplicate key in object 'dbo.Employee_Emergency'. The duplicate key value is (979).
The statement has been terminated. INSERT INTO Employee_Emergency(EmployeeID,SecondaryPostalCode,SecondaryStateID,SecondaryCountryID,SecondaryWorkPhone,SecondaryHomePhone,EffectiveDate,UserID) Values( 979,'98562', 5 , 1 ,'9874561232','7894561235','2/14/2017',1); IF NOT EXISTS( SELECT * FROM ImportEmployeeInfoForBackendRoutine WHERE ImportExportBadFileID = 1560 AND EmployeeID = 979 AND DATEDIFF(DAY, EffectiveDate, '2/14/2017') = 0 AND InsertORUpdate = 1 AND MemberTypeID = 1 ) BEGIN INSERT INTO ImportEmployeeInfoForBackendRoutine (ImportExportBadFileID, EmployeeID, EffectiveDate, InsertORUpdate, MemberTypeID, MemberID, CorePlanStatus, EligibilityStatus) VALUES( 1560, 979, '2/14/2017' , 1, 1, 979 , 0, 0 ) END
Spouse: ErrorID : 0
ErrorSource : ControllerAppTier.SaveAndGetData->WORKTERRAControllerAppTier.SaveAndGetData->ExecuteImportDTS.ImportData_Isolated->WTIsolatedRoutines.Main->ExecuteImportDTS.ImportData->ImportValidation.ImportData->ImportValidation.ProcessImportDataFile->ImportValidation.ProcessLineForBadRecord->ImportValidation.ValidateData->ImportValidation.ValidatePhoneNumber
ErrorMessage: Object reference not set to an instance of an object.
- blocks
-
NF-53 UK Benefits:Implement Phone Number like Zip/Postal code based on Country selection on Import
-
- Reopen in Production
-
Hi Suraj Sokasane,
Company : Caiso
For spouse: NF_53 Spouse
For beneficiary : NF-53 Beneficiary
For Emergency contact: Emergency contact NF_53
Jayshree Nagpure (Inactive)
added a comment - Hi Suraj Sokasane ,
Company : Caiso
For spouse: NF_53 Spouse
For beneficiary : NF-53 Beneficiary
For Emergency contact: Emergency contact NF_53 Hi Jayshree Nagpure,
- Spouse Import issue needs a code fix and will be deployed on LB today.
- In Emergency Contact issue, Phone numbers are marked as unique, which is causing the failure. Remove the uniqueness and it will be successful.
- For Beneficiary, we have two other issues. It can not be mentioned in this Ticket.
Hi Suraj Sokasane,
Environment:Lb
Company: Caiso
Tested spouse import its working as expected
Verified emergency contact import: Imported file goes go bad with validation message as "Invalid state"
For this issue Please refer NF-196
For beneficiary import:working fine
import is done successfully but on UI could not check the phone number is updated or not for spouse and child.we have created new jira for this issue WT-8542.
As discussed with Prasad Pise,for emergency contact import, when state is mapped its impacting and file goes to bad.
Hence re-opening this jira.
Thanks,
Jayshree
Jayshree Nagpure (Inactive)
added a comment - - edited Hi Suraj Sokasane ,
Environment:Lb
Company: Caiso
Tested spouse import its working as expected
Verified emergency contact import: Imported file goes go bad with validation message as "Invalid state"
For this issue Please refer NF-196
For beneficiary import:working fine
import is done successfully but on UI could not check the phone number is updated or not for spouse and child.we have created new jira for this issue WT-8542 .
As discussed with Prasad Pise ,for emergency contact import, when state is mapped its impacting and file goes to bad.
Hence re-opening this jira.
Thanks,
Jayshree
CC: Prasad Pise Rakesh Roy Jaideep Vinchurkar
Verified on LB
Jayshree Nagpure (Inactive)
added a comment - Verified on LB
CC: Prasad Pise Suraj Sokasane Rakesh Roy 
Jayshree Nagpure
As Discussed, please mention Template and Company Name.