WORKTERRAProject Type: software

WORKTERRA

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

Import Fail when Dependent effective date is marked as "Unique"

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Low
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin
    • Labels:
      None
    • Environment:
      QA
    • Bug Type:
      Functional
    • Bug Severity:
      Medium
    • Module:
      BenAdmin - Import
    • Reported by:
      Harbinger
    • Item State:
      Production Complete - Closed

      Description

      Replication steps:
      1)Login with Partner
      2)Search and select company
      3)Go to import/Export -> Template management
      4)Create template for dependent
      5)Selected Dependent effective date as unique -> Import fail

      Please refer attached screen shot and error log :

        Attachments

        1. ChildImport.jpg
          177 kB
          Jayshree Nagpure
        2. SpouseImport.jpg
          182 kB
          Jayshree Nagpure

          Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. WT-10240 Duplicate fields displayed on subtemplate with same sequence number.

          • High - Serious problem that could block progress.
          • Closed
          relates to

          Enhancement - An improvement or enhancement to an existing feature or task. WT-7755 Dependent Import - Validation For unique fields

          • Low - Minor problem or easily worked around.
          • Production Complete

          Bug - A problem which impairs or prevents the functions of the product. WT-10294 IsUnique flag is undefined for export template

          • Medium - Has the potential to affect progress.
          • Closed

            Activity

            Ascending order - Click to sort in descending order
            6 older comments
            Hide
            Permalink
            jayshree.nagpure Jayshree Nagpure (Inactive) added a comment -

            Hi Ankur Deshpande,

            Verified this issue on LB.
            Company - City of Durham

            Verified for scenario

            1) Added a new user defined field, effective date for spouse and marked it as unique. On the mapping screen tried to map the field to Spouse Information Effective date. the field is mapped and save
            Verified spouse import - import Fail

            Error log :
            ErrorID : 0
            ErrorSource : ControllerAppTier.SaveAndGetData->WORKTERRAControllerAppTier.SaveAndGetData->ExecuteImportDTS.ImportData_Isolated->WTIsolatedRoutines.Main->ExecuteImportDTS.ImportData->ImportValidation.ImportData->ImportValidation.ListOutDuplicates
            ErrorMessage: No column name was specified for column 2 of 'Temp'.

            For another scenario :
            2) Added a new user defiled field, effective date for spouse and did not mark it as unique. Now, mapped this field to Spouse Information Effective date. Again coming back to Sub Template screen tried to mark the spouse effective date field as unique.system shows proper validation message "Spouse effective date cannot be unique"

            As first scenario is not working hence re-opening this jira

            Thanks,
            Jayshree

            CC : Rakesh Roy Prasad Pise Suraj Sokasane

            Show
            jayshree.nagpure Jayshree Nagpure (Inactive) added a comment - Hi Ankur Deshpande , Verified this issue on LB. Company - City of Durham Verified for scenario 1) Added a new user defined field, effective date for spouse and marked it as unique. On the mapping screen tried to map the field to Spouse Information Effective date. the field is mapped and save Verified spouse import - import Fail Error log : ErrorID : 0 ErrorSource : ControllerAppTier.SaveAndGetData->WORKTERRAControllerAppTier.SaveAndGetData->ExecuteImportDTS.ImportData_Isolated->WTIsolatedRoutines.Main->ExecuteImportDTS.ImportData->ImportValidation.ImportData->ImportValidation.ListOutDuplicates ErrorMessage: No column name was specified for column 2 of 'Temp'. For another scenario : 2) Added a new user defiled field, effective date for spouse and did not mark it as unique. Now, mapped this field to Spouse Information Effective date. Again coming back to Sub Template screen tried to mark the spouse effective date field as unique.system shows proper validation message "Spouse effective date cannot be unique" As first scenario is not working hence re-opening this jira Thanks, Jayshree CC : Rakesh Roy Prasad Pise Suraj Sokasane
            Hide
            Permalink
            jayshree.nagpure Jayshree Nagpure (Inactive) added a comment -

            Hi Ankur Deshpande,

            Verified on Lb
            company - City of Durham

            Verified Effective date validation message scenario for following import :
            1)Employee import - Pass (Shows validation for unique effective date)
            2)Spouse import - Pass (Shows validation for unique effective date)
            3)Child import - Pass (Shows validation for unique effective date)
            4)Salary - Pass (Shows validation for unique effective date)
            5)Election import - Pass(Effective date is by default unique)
            6)Paycheck import - (Effective date is by default unique)
            7)Emergency contact import - Fail (Allowed to mark effective date unique, ideally as per implementation of effective date it should not allow to mark effective date unique)
            8)Beneficiary import - Fail (Allowed to mark effective date unique, ideally as per implementation of effective date it should not allow to mark effective date unique)

            As 7th and 8th scenario is not working fine, Re-opening this jira

            Thanks,
            Jayshree

            CC : Rakesh Roy Prasad Pise Jaideep Vinchurkar

            Show
            jayshree.nagpure Jayshree Nagpure (Inactive) added a comment - Hi Ankur Deshpande , Verified on Lb company - City of Durham Verified Effective date validation message scenario for following import : 1)Employee import - Pass (Shows validation for unique effective date) 2)Spouse import - Pass (Shows validation for unique effective date) 3)Child import - Pass (Shows validation for unique effective date) 4)Salary - Pass (Shows validation for unique effective date) 5)Election import - Pass(Effective date is by default unique) 6)Paycheck import - (Effective date is by default unique) 7)Emergency contact import - Fail (Allowed to mark effective date unique, ideally as per implementation of effective date it should not allow to mark effective date unique) 8)Beneficiary import - Fail (Allowed to mark effective date unique, ideally as per implementation of effective date it should not allow to mark effective date unique) As 7th and 8th scenario is not working fine, Re-opening this jira Thanks, Jayshree CC : Rakesh Roy Prasad Pise Jaideep Vinchurkar
            Hide
            Permalink
            jayshree.nagpure Jayshree Nagpure (Inactive) added a comment -

            Verified on LB
            company - City of Durham

            Verified below effective date uniqueness validation scenario :

            1) Added a new user defined field, effective date for spouse and marked it as unique. On the mapping screen tried to map the field to Spouse Information Effective date. The field cannot be mapped as it is marked as unique error message is show.
            2) Added a new user defiled field, effective date for spouse and did not mark it as unique. Now, mapped this field to Spouse Information Effective date. Again coming back to Sub Template screen tried to mark the user defined field as unique. The field cannot be marked as unique validation message is shown .

            Verified Effective date validation message scenario for following import - Working Fine
            1)Employee import - Pass (Shows validation for unique effective date)
            2)Spouse import - Pass (Shows validation for unique effective date)
            3)Child import - Pass (Shows validation for unique effective date)
            4)Salary - Pass (Shows validation for unique effective date)
            5)Election import - Pass(Effective date is by default unique)
            6)Paycheck import - (Effective date is by default unique)
            7)Emergency contact import - Pass (Shows validation for unique effective date)
            8)Beneficiary import - Pass (Shows validation for unique effective date)

            Marking item state as Ready for stage.

            Thanks,
            Jayshree

            CC : Rakesh Roy Prasad Pise

            Show
            jayshree.nagpure Jayshree Nagpure (Inactive) added a comment - Verified on LB company - City of Durham Verified below effective date uniqueness validation scenario : 1) Added a new user defined field, effective date for spouse and marked it as unique. On the mapping screen tried to map the field to Spouse Information Effective date. The field cannot be mapped as it is marked as unique error message is show. 2) Added a new user defiled field, effective date for spouse and did not mark it as unique. Now, mapped this field to Spouse Information Effective date. Again coming back to Sub Template screen tried to mark the user defined field as unique. The field cannot be marked as unique validation message is shown . Verified Effective date validation message scenario for following import - Working Fine 1)Employee import - Pass (Shows validation for unique effective date) 2)Spouse import - Pass (Shows validation for unique effective date) 3)Child import - Pass (Shows validation for unique effective date) 4)Salary - Pass (Shows validation for unique effective date) 5)Election import - Pass(Effective date is by default unique) 6)Paycheck import - (Effective date is by default unique) 7)Emergency contact import - Pass (Shows validation for unique effective date) 8)Beneficiary import - Pass (Shows validation for unique effective date) Marking item state as Ready for stage. Thanks, Jayshree CC : Rakesh Roy Prasad Pise
            Hide
            Permalink
            jayshree.nagpure Jayshree Nagpure (Inactive) added a comment -

            Verified on stage all above scenario
            Company - Caiso for hspl

            Working fine

            Marking item state as Ready for production

            Thanks,
            Jayshree

            Show
            jayshree.nagpure Jayshree Nagpure (Inactive) added a comment - Verified on stage all above scenario Company - Caiso for hspl Working fine Marking item state as Ready for production Thanks, Jayshree
            Hide
            Permalink
            jayshree.nagpure Jayshree Nagpure (Inactive) added a comment -

            verified on production
            working fine

            Show
            jayshree.nagpure Jayshree Nagpure (Inactive) added a comment - verified on production working fine

              People

              Assignee:
              jayshree.nagpure Jayshree Nagpure (Inactive)
              Reporter:
              jayshree.nagpure Jayshree Nagpure (Inactive)
              Developer:
              Ankur Deshpande (Inactive)
              QA:
              Jayshree Nagpure (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Dev Due Date:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0h
                  0h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 62.5h
                  62.5h