Layout: Item | Purchase Order

The On Order quantity was not updating when:

1. a new item was created
2.  a PO was created from the Item layout

(This is using the Create PO button on the bottom right of the Item layout.)

Two scripts were altered: 

1.     select warehouse ID based on warehouse name
2.     set the balance quantity fields (parameters)

Modifications to select warehouse ID… was necessary to fix the bug.  Modifications to set the balance… is precautionary.

See log at bottom of those scripts for details.

Layout: Sales Order | Button: More.../Pick History

Button pointed to “display receipt history for order” instead of “display pick history for order”. 

Script: “display pick history for order” pointed to the Receipt History layout instead of the Pick History layout.  Likewise, the single search criteria was

Set Field [ RECEIPT::orderID ; $orderID ]

Instead of 

Set Field [ PICK::orderID ; $orderID ]

Custom dialog at the end of the script was also updated.

Layout: Menu

Added written instructions for adding a new menu item.  Instructions are to the right of the visible layout, in Layout Mode.

Layout: Purchase Order | Field: Vendor

Script trigger passes a JSON object with a misspelled key (“Compnay Type” should be “Company Type”).

JSONSetElement ( 
  "" ; 
  ["Compnay Type" ; "Vendor" ; JSONString] ;
  ["Window Top" ; 160 ; JSONNumber]
)

Should be

JSONSetElement ( 
  "" ; 
  ["Company Type" ; "Vendor" ; JSONString] ;
  ["Window Top" ; 160 ; JSONNumber]
)

Note: Thanks to Humberto Becerra for finding this.

Added WAREHOUSE_global table occurrence.

Layout: Putaway

Created a card window for users to add a location via the Putaway layout.  Previously, a user could add any alpha numeric string in the Actual Location field.  If the string did not correlate to an existing location, it was added to the Location table.  However, only LOCATION::location was updated and not the fields zone, aisle, section, row, or bin.  Now, if a user enters a location that does not exist, a card window appears and offers the user a list of locations for that warehouse or the option of creating a new location.

Layout: Location

The field LOCATION::location was not visible on the Location layout as it was a calculation field and can be seen in the sub-header section (a.k.a. light blue section).  Added the location to the layout, below description and above zone.

Changed LOCATION::location to an auto-enter calculation, creating a string from zone, aisle, section, row, bin.

NOTE: Location should be modified to best suite your warehouse organization.  Zone, aisle, section, row, and bin are commonly used, but may not be required in your situation.  Customize as needed.

Layout: Item, Quantity Card Window

The On Order and On Backorder fields in the Body part were in the wrong place (On Backorder was in column 4 and On Order in column 5).

Layout: Item, Item Vendor Card Window

Adding a single vendor did not mark that vendor as the primary vendor.

Modified script so that the first vendor added is marked as the primary vendor.  Otherwise, an item with a single vendor will not have a primary vendor.

Layout: Item, Item Vendor Card Window

When deleting a vendor in the Item Vendor card window, the global variable $$itemID was cleared. This prevented the item ID from setting in the ITEMVENDOR table if the user added a new vendor while the card window was still open.  (Closing and reopening the card window re-set the $$itemID.)  $$itemID now persists while the card window is open, even when a vendor is deleted for a particular item.