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

Order Guide-Location import does not make the change from non-national to national Vendor in certain edge scenarios

    Details

    • Type: Sprint Defect
    • Status: Done (View Workflow)
    • Priority: Blocker
    • Resolution: Completed
    • Affects Version/s: CFA 2019R1
    • Fix Version/s: CFA 2019R2
    • Component/s: OrderGuide
    • Labels:
      None
    • SCRUM Team:
      Watchmen
    • Source Code ID(s):
    • Sprint:
      CFAMX 2019R1 Sprint 5, CFAMX 2019R1 Sprint 6, CFAMX 2019R1 Hardening, CFAMX 2019R2 Sprint 3

      Description

      Order Guide-Location import does not make the change from non-nation to national Vendor in certain edge scenarios:

      1. First, I associated a Store to a non-national Vendor through the location import, which removed the Vendor Entity relationship, but retained the Distributor Name and Distributor Center
      2. I reprocessed the same file after making the Vendor national through MMS
      3. https://inform.jatesting.cfahome.com/MMS_HO_Distributors.aspx?MenuCustomItemID=185

      Results: The Store did not get associated with the National Vendor

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                soma.dixon Soma Dixon (Inactive)
                Reporter:
                soma.dixon Soma Dixon (Inactive)
              • Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 10h Original Estimate - 10h
                  10h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 17.25h
                  17.25h

                    PagerDuty

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