Uploaded image for project: 'CFA MX '
  1. CFA MX
  2. CFAMX-133

TESTING - INF-10517 - Item Maintenance: Updated Panel data does not persist to DB if you toggle the suggested item flag first

    Details

    • Sprint:
      CFAMX 2018R4 Sprint 1

      Description

      When you update the Default Order Quantity (DOQ) for several (>2) items and then click save on the Item Maintenance Page, all the updated quantities are not persisted to the Database tbEntityitem.DefaultOrderQuantity

      • Note: this is true for any entries into the Item Maintenance page (Safety Stock, UPT, DOQ)

      Reproduction Steps:
      1. Navigate to Denton Town Crossing in MxConnect
      2. Navigate to the Item Maintenance page
      https://m.inform.jatesting.cfahome.com/#/Administration/ItemMaintenance
      3. Select View All
      4. Search something that has multiple items - mix
      5. NULL all the DOQ fields for all the items (toggle the suggested item flag for some of the items)
      6. Click Save
      Observe the DB - all items are not updated to NULL
      7. Go back and populate the fields again with quantities 1-5

      Expected Results:
      No matter how many properties you select and save, they should all be persisted to the entity item table

      Actual Results:
      The items for which you toggle the Suggested item flag and update the DOQ field, the default quantities do not update in the Database 

      TestRail Link:
      http://testrail.redbookconnect.com/index.php?/cases/view/12834714

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                neha.shah Neha Shah (Inactive)
                Reporter:
                will.englefield Will Englefield (Inactive)
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.