Details

    • Type: Bug
    • Status: Closed
    • Priority: High
    • Resolution: Bug Fixed
    • Labels:
      None
    • Environment:
      Production
    • Categories:
      Import - Scheduled import
    • Company:
      Parkview Medical Center
    • Reported by:
      EDI
    • Caused by UI Refresh:
      Yes

      Description

      The scheduled import for 03/06/2018 failed.

        Attachments

        1. AffectedFiles.txt
          0.1 kB
        2. error.txt
          4 kB
        3. fail imporrt.png
          fail imporrt.png
          48 kB
        4. FieldMapping.png
          FieldMapping.png
          78 kB
        5. FieldMapping2.png
          FieldMapping2.png
          70 kB
        6. parkmc_Changes.zip
          2 kB
        7. WT_Sprint-45_WB_583_Sanjanajadhav.xls
          23 kB
        8. WT_Sprint-46_WB_583_Sanjanajadhav_Updated.xls
          22 kB

          Issue Links

            Activity

            Hide
            Cindy.Wibbing Cindy Wibbing (Inactive) added a comment - - edited

            Password via email
            Template name Employee Data_OnGoing

            Show
            Cindy.Wibbing Cindy Wibbing (Inactive) added a comment - - edited Password via email Template name Employee Data_OnGoing
            Hide
            nidhi.kaul Nidhi Kaul (Inactive) added a comment - - edited

            Vinayak Kulkarni
            I forwarded you the email from Cindy with password.

            Satya
            Nidhi.

            Show
            nidhi.kaul Nidhi Kaul (Inactive) added a comment - - edited Vinayak Kulkarni I forwarded you the email from Cindy with password. Satya Nidhi.
            Hide
            suraj.sokasane Suraj Sokasane (Inactive) added a comment -

            Hi Cindy Wibbing,

            Below are the details of issue:

            Concern: Scheduled Import getting failed for Template "Employee Data_OnGoing".

            Cause : Our primary analysis is Education and PCP fields mapped in the template are causing the issue in file processing.

            We checked the file and there's no data given for those fields. While we look into the issue, we suggest that you un-map the fields and import the file. We tried this on HSPL copy and import was successful.
            If there's data for those fields, you can provide it to us and we'll insert it from back end.

            Below are the fields that are causing the issue and you'll need to unmap:
            Education fields:

            PCP fields:

            Please let us know if you face any issue or have any queries.

            Show
            suraj.sokasane Suraj Sokasane (Inactive) added a comment - Hi Cindy Wibbing , Below are the details of issue: Concern: Scheduled Import getting failed for Template "Employee Data_OnGoing". Cause : Our primary analysis is Education and PCP fields mapped in the template are causing the issue in file processing. We checked the file and there's no data given for those fields. While we look into the issue, we suggest that you un-map the fields and import the file. We tried this on HSPL copy and import was successful. If there's data for those fields, you can provide it to us and we'll insert it from back end. Below are the fields that are causing the issue and you'll need to unmap: Education fields: PCP fields: Please let us know if you face any issue or have any queries.
            Hide
            Ganesh.sadawarte Ganesh Sadawarte (Inactive) added a comment - - edited

            Hi Cindy Wibbing,

            We have made template customization changes so going foreword import will not failed and also loaded changes file. Please refer JIRA WB-671.

            Thanks,
            Ganesh

            Show
            Ganesh.sadawarte Ganesh Sadawarte (Inactive) added a comment - - edited Hi Cindy Wibbing , We have made template customization changes so going foreword import will not failed and also loaded changes file. Please refer JIRA WB-671. Thanks, Ganesh
            Hide
            suraj.sokasane Suraj Sokasane (Inactive) added a comment - - edited

            Hi All,

            Below are the details:

            Concern:
            Scheduled Import getting failed on ParkView

            Cause:
            The Education fields mapped on template can be mapped multiple times and are processed separately. Here if any field does not have value on file, Import fails. It will work if values are given for all Education fields.

            Correction:
            We will need code change for this so that if value is not given, NULL will be inserted.

            Vinayak Kulkarni, Ganesh Sadawarte

            Show
            suraj.sokasane Suraj Sokasane (Inactive) added a comment - - edited Hi All, Below are the details: Concern: Scheduled Import getting failed on ParkView Cause: The Education fields mapped on template can be mapped multiple times and are processed separately. Here if any field does not have value on file, Import fails. It will work if values are given for all Education fields. Correction: We will need code change for this so that if value is not given, NULL will be inserted. Vinayak Kulkarni , Ganesh Sadawarte
            Hide
            suraj.sokasane Suraj Sokasane (Inactive) added a comment - - edited

            Hi All,

            After digging little more we found more details about the issue as mentioned below:

            1. The issue was not present on old UI production and occurred after UI Refresh Build.
            2. There was an unverified code in local environment which was pushed to UI refresh and then to production.
            3. The scheduled import started failing on Park View from march 7th which is after UI refresh build on 4th March.

            CC- Satya, Vinayak Kulkarni, Ganesh Sadawarte

            Show
            suraj.sokasane Suraj Sokasane (Inactive) added a comment - - edited Hi All, After digging little more we found more details about the issue as mentioned below: The issue was not present on old UI production and occurred after UI Refresh Build. There was an unverified code in local environment which was pushed to UI refresh and then to production. The scheduled import started failing on Park View from march 7th which is after UI refresh build on 4th March. CC- Satya , Vinayak Kulkarni , Ganesh Sadawarte
            Hide
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment -

            Hi,

            Please refer attached test cases:
            WT_Sprint-45_WB_583_Sanjanajadhav.xls

            Thanks,
            Sanjana Jadhav

            CC: Prasad Pise Sachin Hingole Rakesh Roy

            Show
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment - Hi, Please refer attached test cases: WT_Sprint-45_WB_583_Sanjanajadhav.xls Thanks, Sanjana Jadhav CC: Prasad Pise Sachin Hingole Rakesh Roy
            Hide
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment -

            Hi Suraj Sokasane,

            As per our discussion, PCP fields not mapped in demographics template,hence removed test cases for PCP fields and added test cases for multiple mapped fields.
            Please refer updated test cases :
            WT_Sprint-46_WB_583_Sanjanajadhav_Updated.xls

            Thanks,
            Sanjana Jadhav

            CC: Prasad Pise Rakesh Roy

            Show
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment - Hi Suraj Sokasane , As per our discussion, PCP fields not mapped in demographics template,hence removed test cases for PCP fields and added test cases for multiple mapped fields. Please refer updated test cases : WT_Sprint-46_WB_583_Sanjanajadhav_Updated.xls Thanks, Sanjana Jadhav CC: Prasad Pise Rakesh Roy
            Hide
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment -

            Hi Suraj Sokasane,

            Verified on LB.
            Company: For QA-CHMC-Azure

            1.Verify demographic template by manaul import-Pass
            2.Verify demographic template by scheduler- Fail
            ============================================================
            Company Level Import : For QA-CHMC-Azure

            Template Name : demograpic_3apr
            DateTime : 4/4/2018 2:06:09 PM
            Status : Error occured while import.
            Error Source : ExecuteImportScheduler
            Error Message : Object reference not set to an instance of an object.
            ============================================================

            Invalid object name 'ExportSchedule_CalendarDates'.
            ============================================================
            3.Verify demographics template by adding education field(college,degree,year)-Manual import-Import getting fail
            PFA
            error.txt

            Thanks,
            Sanjana Jadhav

            CC: Prasad Pise Rakesh Roy Ganesh Sadawarte

            Show
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment - Hi Suraj Sokasane , Verified on LB. Company: For QA-CHMC-Azure 1.Verify demographic template by manaul import-Pass 2.Verify demographic template by scheduler- Fail ============================================================ Company Level Import : For QA-CHMC-Azure Template Name : demograpic_3apr DateTime : 4/4/2018 2:06:09 PM Status : Error occured while import. Error Source : ExecuteImportScheduler Error Message : Object reference not set to an instance of an object. ============================================================ Invalid object name 'ExportSchedule_CalendarDates'. ============================================================ 3.Verify demographics template by adding education field(college,degree,year)-Manual import-Import getting fail PFA error.txt Thanks, Sanjana Jadhav CC: Prasad Pise Rakesh Roy Ganesh Sadawarte
            Hide
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment -

            Hi Suraj Sokasane

            Verified below scenarios on LB:
            1.Import demographic template with education fields-Pass
            2.Again import same template-Pass
            3.Delete one entry of eductaion from UI and again import same template-education info updated-Pass
            4.Pass null character-record not created in education.-Pass
            5.Pass blank values-record not created in education.-Pass
            6.Verify validation shows for year field-Pass
            7.Import multiple employee with same education field value-Value not shown on education page-Fail

            Please look into this issue.

            Thanks,
            Sanjana Jadhav

            CC: Prasad Pise Rakesh Roy Ganesh Sadawarte

            Show
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment - Hi Suraj Sokasane Verified below scenarios on LB: 1.Import demographic template with education fields-Pass 2.Again import same template-Pass 3.Delete one entry of eductaion from UI and again import same template-education info updated-Pass 4.Pass null character-record not created in education.-Pass 5.Pass blank values-record not created in education.-Pass 6.Verify validation shows for year field-Pass 7.Import multiple employee with same education field value-Value not shown on education page-Fail Please look into this issue. Thanks, Sanjana Jadhav CC: Prasad Pise Rakesh Roy Ganesh Sadawarte
            Hide
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment -

            Hi Ganesh Sadawarte

            Verified on LB .
            Verified all below scenarios through manual import.
            1.Import demographic template with education fields-Pass
            2.Again import same template-Pass
            3.Delete one entry of eductaion from UI and again import same template-education info updated-Pass
            4.Pass null character-record not created in education.-Pass
            5.Pass blank values-record not created in education.-Pass
            6.Verify validation shows for year field-Pass
            7.Import multiple employee with same education field value-Value not shown on education page-Pass
            Working as expected.
            Scheduler is not working on LB. Please refer jira WD-197 for same. Once issue resolved assign jira back to me.

            Thanks,
            Sanjana Jadhav

            CC: Prasad Pise Sachin Hingole Rakesh Roy

            Show
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment - Hi Ganesh Sadawarte Verified on LB . Verified all below scenarios through manual import. 1.Import demographic template with education fields-Pass 2.Again import same template-Pass 3.Delete one entry of eductaion from UI and again import same template-education info updated-Pass 4.Pass null character-record not created in education.-Pass 5.Pass blank values-record not created in education.-Pass 6.Verify validation shows for year field-Pass 7.Import multiple employee with same education field value-Value not shown on education page-Pass Working as expected. Scheduler is not working on LB. Please refer jira WD-197 for same. Once issue resolved assign jira back to me. Thanks, Sanjana Jadhav CC: Prasad Pise Sachin Hingole Rakesh Roy
            Hide
            Ganesh.sadawarte Ganesh Sadawarte (Inactive) added a comment -

            Hi Sanjana Jadhav,

            We are not able identified why scheduler is not working on import. We can test this in pre-prod for scheduler

            Thanks,
            Ganesh

            Show
            Ganesh.sadawarte Ganesh Sadawarte (Inactive) added a comment - Hi Sanjana Jadhav , We are not able identified why scheduler is not working on import. We can test this in pre-prod for scheduler Thanks, Ganesh
            Hide
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment -

            As per above comment, scheduler for import is not working on LB due to lack of environment.Hence not able to test scheduler functionality on LB.I will test it on Pre production enviornment.
            Hence marking this jira as Ready for pre production.

            Thanks,
            Sanjana Jadhav

            CC: Prasad Pise Sachin Hingole Rakesh Roy

            Show
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment - As per above comment, scheduler for import is not working on LB due to lack of environment.Hence not able to test scheduler functionality on LB.I will test it on Pre production enviornment. Hence marking this jira as Ready for pre production. Thanks, Sanjana Jadhav CC: Prasad Pise Sachin Hingole Rakesh Roy
            Hide
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment -

            Verified on Pre production.
            Verified all attached test cases.Working as expected.
            Ready for production.

            Thanks,
            Sanjana Jadhav

            CC: Sachin Hingole Prasad Pise Rakesh Roy

            Show
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment - Verified on Pre production. Verified all attached test cases.Working as expected. Ready for production. Thanks, Sanjana Jadhav CC: Sachin Hingole Prasad Pise Rakesh Roy
            Hide
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment -

            Hi Cindy Wibbing

            The issue has been resolved and also tested on Production. Please could you verify at your end and close this ticket.

            Thanks,
            Sanjana Jadhav

            CC: Prasad Pise Sachin Hingole Rakesh Roy

            Show
            sanjana.jadhav Sanjana Jadhav (Inactive) added a comment - Hi Cindy Wibbing The issue has been resolved and also tested on Production. Please could you verify at your end and close this ticket. Thanks, Sanjana Jadhav CC: Prasad Pise Sachin Hingole Rakesh Roy

              People

              Assignee:
              Cindy.Wibbing Cindy Wibbing (Inactive)
              Reporter:
              Cindy.Wibbing Cindy Wibbing (Inactive)
              Developer:
              Suraj Sokasane (Inactive)
              QA:
              Sanjana Jadhav (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Dev Due Date:
                Code Review Date:

                  Time Tracking

                  Estimated:
                  Original Estimate - 1h Original Estimate - 1h
                  1h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 53.1h
                  53.1h