Uploaded image for project: 'WORKTERRA'
  1. WORKTERRA
  2. WT-10240

Duplicate fields displayed on subtemplate with same sequence number.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: High
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin
    • Labels:
      None
    • Bug Type:
      Functional
    • Bug Severity:
      Medium
    • Module:
      BenAdmin - Export
    • Reported by:
      Harbinger
    • Item State:
      Production Complete - Closed
    • Issue Importance:
      Must Have
    • Sprint:
      WT Sprint 33-Bugs

      Description

      Due to the implementation of WT-9259, there was an issue on sub template if 2 Database fields are mapped to 1 field. Due to this on subtemplate 2 fields were visible with same sequence number. This was creating error while exporting the file.

        Attachments

          Issue Links

            Activity

            Hide
            jayshree.nagpure Jayshree Nagpure (Inactive) added a comment -

            Hi Swapnil Eksambekar,

            I have verified this issue for import on stage

            • When 1 sub-template field is mapped to 2 mapping field : It creates single row.and shows in comma separated row - Pass
            • When Emp Effective date is mapped with Employee effective date and other field, its creates 1 rows and shows comma separated row - Pass

            CC :Prasad Pise Rakesh Roy

            Show
            jayshree.nagpure Jayshree Nagpure (Inactive) added a comment - Hi Swapnil Eksambekar , I have verified this issue for import on stage When 1 sub-template field is mapped to 2 mapping field : It creates single row.and shows in comma separated row - Pass When Emp Effective date is mapped with Employee effective date and other field, its creates 1 rows and shows comma separated row - Pass CC : Prasad Pise Rakesh Roy
            Hide
            jaideep.vinchurkar Jaideep Vinchurkar (Inactive) added a comment -

            What is final status of this? ready for stage?

            Show
            jaideep.vinchurkar Jaideep Vinchurkar (Inactive) added a comment - What is final status of this? ready for stage?
            Hide
            jayshree.nagpure Jayshree Nagpure (Inactive) added a comment -

            Hi Swapnil Eksambekar,

            Check this issue for export and update the jira accordingly

            Thanks,
            Jayshree

            cc :Prasad Pise Rakesh Roy Jaideep Vinchurkar

            Show
            jayshree.nagpure Jayshree Nagpure (Inactive) added a comment - Hi Swapnil Eksambekar , Check this issue for export and update the jira accordingly Thanks, Jayshree cc : Prasad Pise Rakesh Roy Jaideep Vinchurkar
            Hide
            swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment -

            Verified this issue by Mapping Emp Effective date and Emp Cost,
            It is working as expected.
            Ready for Production.

            CC-Aniruddha DevHrishikesh DeshpandeRakesh RoyGaurav Sodani

            Show
            swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment - Verified this issue by Mapping Emp Effective date and Emp Cost, It is working as expected. Ready for Production. CC- Aniruddha Dev Hrishikesh Deshpande Rakesh Roy Gaurav Sodani
            Hide
            swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment -

            Verified this Issue on Production it is working as expected.

            CC-Aniruddha DevRakesh RoyHrishikesh Deshpande

            Show
            swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment - Verified this Issue on Production it is working as expected. CC- Aniruddha Dev Rakesh Roy Hrishikesh Deshpande

              People

              Assignee:
              swapnil.eksambekar Swapnil Eksambekar (Inactive)
              Reporter:
              ankur.deshpande Ankur Deshpande (Inactive)
              Developer:
              Rajendra Pawar (Inactive)
              QA:
              Aniruddha Dev (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 - 16h Original Estimate - 16h
                  16h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 23.75h
                  23.75h