Location Import - Add support for multiple vendors

As an admin I want the location import to be updated to support multiple vendors per restaurant so that I can assign one or more vendors to a specific location

Notes

• The Location Import creates and maintains mutually exclusive zones, for zone types
  • Location - DistributorName
    • This comes from dist:Name
  • Location - DistributionCenter
    • Concatenation of dist:ShortName + dist:DistributionCenter
• Update the Location Import to compare arrays, rather than single values, when maintaining the Vendor Entity relationship
• Support multiple vendors, not just two
• Update the XSLT
• Review the very last section in the XSLT , which puts a vendor into the entity table (is this needed or should we just drop it?)
• Change Zone Types, above, to no longer be mutually exclusive
• Sample File: Locations_all_with_multiple_distributors.xml
• Examples of changes:

  Data	Before	After
  Vendor 2	1	2
  Vendor 1 & 2	1	1 & 2
  Vendor 2 & 3	1	2 & 3
  Vendor 1, 2 & 3	1	1, 2 & 3
  Vendor 1	1 & 2	1
  Vendor 1 & 2	2 & 3	1 & 2
  Etc...

Acceptance Criteria

1. Confirm that the zone type Location - DistributorName is no longer has a constraint that makes it mutually exclusive
   • Note: this needs to be changed in the import and the UI (Zone Manager)
2. Confirm that the zone type Location - DistributionCenter is no longer has a constraint that makes it mutually exclusive
   • Note: this needs to be changed in the import and the UI (Zone Manager)
3. Confirm that a location file can be processed with only one Vendor included for a location
4. Confirm that a location file can be processed with multiple Vendors per location
5. Confirm that a location file can be processed that changes the vendor assignment from one to one
6. Confirm that a location file can be processed that changes the vendor assignment from one to many
7. Confirm that a location file can be processed that changes the vendor assignment from many to one
8. Confirm that a location file can be processed that changes the vendor assignment from many to many
9. Confirm that the XSLT is changed as a part of the deployment
10. Confirm that tests are executed for restaurants that are flagged as Smart Safe
11. Confirm that tests are executed for restaurants that are flagged as Non Smart Safe
    • Note: there are two sections in the XSLT that need to be updated, one for SS and one for NSS
12. Determine if the final section of the XSLT, that populates tbEntity.PreferredDistributionCenterId is required or not, and make the appropriate updates to support the decision
13. Confirm that Order Guide Rules are queued for processing correctly when adding/removing a vendor assignment via the Location Import