Uploaded image for project: 'ui-data-import'
  1. ui-data-import
  2. UIDATIMP-456

Mapping Profiles Form existing record type recognition behavior is wrong

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      EPAM BatchLoader Sprint 38
    • Story Points:
      2
    • Development Team:
      Folijet

      Description

      Bug symptoms are the following:

      1. Form loads with empty mapping details section when it loads for existing record edit mode.
      2. When the user changes existing record type for already existing mapping profile and then returns to original existing record type, form believes nothing has changed and leaves the previous section type initial data that prevents the form from correct work behavior.

      Root causes:

      1. When the form loads with existing record in edit mode it first persists null as previous (initial) existing record type value and then loads the form data with actual value from the form state. This pushes the form logic to believe existing record type has changed and empty initial data load is needed

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                taras_tkachenko Taras Tkachenko
                Reporter:
                taras_tkachenko Taras Tkachenko
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases