{UpdateVendorEntityItem} Directive on Date Field in Vendor Item File causes Null discontinue date for all items

This defect is in reference to the Order Guide issues seen a few weeks ago when the {UpdateEntityItem} Directive was added to the DiscontinueDate field in the vendor item file. This directive caused all discontinue dates for all items in the system, new and old, active and inactive, to be null, which then caused multiple duplicate and incorrect items to appear on all order guides. This change was supposed to help Unit of Measure accuracy by end dating old vendor items previously associated to a store with a different UOM. By doing so, the new UOM would display accurately. This was not the case and the null value was applied across the board instead.

Reproduction Steps:

Import a vendor item file with the {UpdateEntityItem} directive in the discontinue date field and view order guides, looking for duplicate/old items appearing on order guides.

Actual Results:

Order guides have items that are old or duplicates appearing on order guides, and all rules active or inactive, appear.

Sample date format:

4712/12/31 00:00:00

Note:

When the date of '4712/12/31 00:00:00' is received in the Vendor Item Import, the Discontinue Date in tbVendorItem gets set to Null, and when the directive is added, the Discontinue Date in tbVendorEntityItem was updated to Null for all items that were in the file and had this date. Even those items that had previously been discontinued in InFORM.

If there is a Discontinue Date in tbVendorEntityItem that is not Null, do not update, only the InFORM Order Guide should update VEI dates in this case.