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
            ankur.deshpande Ankur Deshpande (Inactive) added a comment -

            Concern : Duplicate fields visible on subtemplate if more than 1 fields are mapped. This caused server error while exporting the file.

            Cause : When more than 1 fields are mapped, 2 different rows are stored in the database. While fetching on to subtemplate page instead of getting displayed as comma separated, 2 separate rows were occurring. This happened due to WT-9259 where Id's of the fields were fetched from Database which was the main reason for displaying 2 separate rows.

            Correction : Fetched the Id's from database same as the text of the fields, which solved the issue and only 1 comma separated row is visible.

            Regards,
            Ankur

            Show
            ankur.deshpande Ankur Deshpande (Inactive) added a comment - Concern : Duplicate fields visible on subtemplate if more than 1 fields are mapped. This caused server error while exporting the file. Cause : When more than 1 fields are mapped, 2 different rows are stored in the database. While fetching on to subtemplate page instead of getting displayed as comma separated, 2 separate rows were occurring. This happened due to WT-9259 where Id's of the fields were fetched from Database which was the main reason for displaying 2 separate rows. Correction : Fetched the Id's from database same as the text of the fields, which solved the issue and only 1 comma separated row is visible. Regards, Ankur
            Hide
            jayshree.nagpure Jayshree Nagpure (Inactive) added a comment -

            Hi Ankur Deshpande,

            Verified on company
            Company - QA ASML
            Login - Partner

            Verified below scenario through import :

            • When 1 sub-template field is mapped to 2 mapping field : It creates single row.and shows in comma separated row - Pass
            • Also verified all the unique scenario mentioned in WT-9259 - Pass
            • When Emp Effective date is mapped with Employee effective date and other field, its creates 2 rows in sub template and position on file is duplicated - This scenario is not working fine

            As last scenario is not working fine, hence re-opening this jira

            Thanks,
            Jayshree

            cc : Rakesh Roy Prasad Pise

            Show
            jayshree.nagpure Jayshree Nagpure (Inactive) added a comment - Hi Ankur Deshpande , Verified on company Company - QA ASML Login - Partner Verified below scenario through import : When 1 sub-template field is mapped to 2 mapping field : It creates single row.and shows in comma separated row - Pass Also verified all the unique scenario mentioned in WT-9259 - Pass When Emp Effective date is mapped with Employee effective date and other field, its creates 2 rows in sub template and position on file is duplicated - This scenario is not working fine As last scenario is not working fine, hence re-opening this jira Thanks, Jayshree cc : Rakesh Roy Prasad Pise
            Hide
            ankur.deshpande Ankur Deshpande (Inactive) added a comment -

            Hi Rajendra Pawar,

            As per discussion can you please look into the issue.

            Regards,
            Ankur

            Show
            ankur.deshpande Ankur Deshpande (Inactive) added a comment - Hi Rajendra Pawar , As per discussion can you please look into the issue. Regards, Ankur
            Hide
            swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment -

            It is giving server error while 2 fields are mapped.

            Error occurred as below:-
            -------------
            *ErrorID : 0
            ErrorSource : ControllerAppTier.Save->WORKTERRAControllerAppTier.Save->ImportExportSettings.Save->ImportExportSettings.AddUpdateMappingFields
            ErrorMessage: Error converting data type varchar to bigint.*
            ------------

            Aniruddha DevHrishikesh DeshpandeRakesh Roy

            Show
            swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment - It is giving server error while 2 fields are mapped. Error occurred as below:- ------------- *ErrorID : 0 ErrorSource : ControllerAppTier.Save->WORKTERRAControllerAppTier.Save->ImportExportSettings.Save->ImportExportSettings.AddUpdateMappingFields ErrorMessage: Error converting data type varchar to bigint.* ------------ Aniruddha Dev Hrishikesh Deshpande Rakesh Roy
            Hide
            rajendra.pawar Rajendra Pawar (Inactive) added a comment -

            Ankur Deshpande, Please see error.

            Show
            rajendra.pawar Rajendra Pawar (Inactive) added a comment - Ankur Deshpande , Please see error.
            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 stage.

            CC-Aniruddha DevRakesh RoyGaurav SodaniRajendra PawarHrishikesh Deshpande

            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 stage. CC- Aniruddha Dev Rakesh Roy Gaurav Sodani Rajendra Pawar Hrishikesh Deshpande
            Hide
            swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment -

            We are blocked to verify this JIRA due to it is related to wt-10294, hence changing status ON HOLD.
            We will verify this JIRA after WT-10294 is deployed on STAGE

            CC-Aniruddha DevHrishikesh DeshpandeGaurav SodaniRakesh Roy

            Show
            swapnil.eksambekar Swapnil Eksambekar (Inactive) added a comment - We are blocked to verify this JIRA due to it is related to wt-10294, hence changing status ON HOLD . We will verify this JIRA after WT-10294 is deployed on STAGE CC- Aniruddha Dev Hrishikesh Deshpande Gaurav Sodani Rakesh Roy
            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