LS Nav 10.08 Release Notes

About This Release

Build no. - 524
Released - October 26, 2017

This version is built on Microsoft Dynamics NAV 2017, build no. 18197.

Note:
The 64-bit client is now the default client when opening NAV.

In this version the POS is only supported to run on the 32-bit Dynamics NAV Windows client. We recommend setting up the 32-bit client in the LS Nav Start tool for the POS.

The following is a list of changes and key features in LS Nav 2017 (10.08).

Hospitality:

Current Item Availability on a POS Button

Now current availability is shown as a counter on a POS button that has a PLU_K or DEAL command in all the menus of the restaurant. The counter shows how much quantity is available for the item or deal that is associated with the button. The counter is automatically updated.

 

When the item or deal is sold on the POS and the current availability is enough for the requested quantity, the system reduces the current availability accordingly. If not enough availability, the system displays an error. When the counter is down to zero, the button is disabled.

 

A new POS Command, AVAILABILITY_MODE, is used to set current availability on the POS buttons. The current availability feature is not supported on the Mobile POS in this version. It will be supported on the Mobile POS in future versions.

Identical Item Lines not Compressed if They Have a Menu Type

A new field, Compress Menu Type, has been added to the Restaurant Menu Type table. If this field is selected, and Compress When Scanned is enabled in the active functionality profile, identical items with this default menu type are compressed when entered.

Otherwise, the items are not compressed even if they have the same default menu type. This allows changing the menu type afterwards.

Replenishment:

Changes in Standard NAV Purchase Unit of Measure

Previously, the Purch. Unit of Measure (UoM) field on the Retail Item Card was not used and considered when items were being purchased, the Purchase Replenishment Journal was always calculated in the Base Unit of Measure. In this release, the below features have been introduced to improve the situation with the aim to leverage the Purch. Unit of Measure field.

Synching Order Multiple Field with Purchase Unit of Measure

The Order Multiple field in the Item (27) table and the Purchase Order Multiple field in the Replen. Item Store Rec (10012206) table will be updated with the value set up for Qty. per Unit of Measure when the Purch. Unit of Measure field for the item is changed. The Order Multiple fields will also be updated when the Qty. per Unit of Measure field in the Item Units of Measure page is changed, if the quantity changed belongs to the Purch. Unit of Measure currently assigned to the item.

To support the feature, a new FastTab, Integration, has been introduced in Replenishment Setup. In this new FastTab, a new field, Purch. UoM Updates Multiple Field, has been added to define if the Order Multiple field for an item should be updated when its Purch. Unit of Measure is changed. The field has these options:

  • Never - the item's Order Multiple field will never be updated.
  • With Confirmation - customers will be asked if they wish to update the item's Order Multiple field.
  • Without Confirmation - the item's Order Multiple field will always be updated.

Another field, Lock Order Multiple, has also been added to the Replen. Item Store Rec (10012206) table and the Replen. Item Store Rec (10012210) page. If this field is enabled, the Purchase Order Multiple field for the relevant Item Store Records will not be updated when its Purch. Unit of Measure is changed.

Purchase Replenishment Journal to Consider Purchase Unit of Measure for Purchase Order Creation

In this release, customers are presented with the option to create a Purchase Order (PO) in a Purch. Unit of Measure. When the POs are created from the Purchase Replenishment Journal, the Unit of Measure will be changed from Base Unit of Measure to Purch. Unit of Measure, if the quantity ordered is a full multiple. For example, the Purch. Unit of Measure is set to BOX and it is known that there are 50 PCS in 1 BOX, examples of full multiples would be 50, 100, or 150 PCS since they are equivalent to 1, 2, or 3 BOXES.

To support the feature, the Purch. Replen. Journal UoM Handling field has been added to the new Integration FastTab in Replenishment Setup. This field defines if the Unit of Measure will be converted when POs are created from the Journal. The field has these options:

  • Keep Calculated Base UoM - the Unit of Measure will be kept as it is and will not be converted.
  • Convert to Purch. UoM if Possible - the Unit of Measure will be converted to the Purch. Unit of Measure, if the quantity is a full multiple.

Display Warning when Quantity in Purchase Replenishment Journal Line is Changed

Customers have the option to change the quantity in Purchase Replenishment Journal Lines and Journal Detail Lines. Now, with the introduction of the option for conversion to Purch. Unit of Measure, it is necessary to display a warning if the changes by the customers lead to a Quantity which is not a full multiple.

A new field, Purch. Replen. Journal Quantity Warning, has been added to the new Integration FastTab in Replenishment Setup. It defines if a warning will be displayed when a changed Quantity in the Purchase Replenishment Journal is not a full multiple. The field has these options:

  • No Warning
  • Warn if Not Full Multiple.

Copy Sales Budget Improvements

Improvements have been implemented in the request page of Report Copy Retail Sales Budget:

  1. Control added to enable/disable the fields Division Code, Item Category, and Product Group, based on the selected Copy-from Budget Type.
  2. The field Budget Type has been added below the Budget Name field, which is updated when the user selects a destination budget.
  3. When the entries are being copied, the Division Code, Item Category, and Product Group fields in the destination budget will be replaced according to the global setup in Product Group/Item Category tables.
  4. A message is displayed at the end of the copy action if entries with an earlier start date compared to the destination's Budget Start Date are found.

Enhancements in Master-Child Budgets Consolidation for Retail Sales Budget

The Master-Child Budgets Consolidation feature for Retail Sales Budget has been extended to allow a more flexible planning: a master budget is not only allowed to relate to child budgets with the same budget type, but also to child budgets with more specific types.

For example, if the master budget has a type Item Category, the child budget types allowed would be Item Category, Product Group, or Item. When child budget entries are consolidated into master budget, the type of the entries will be transformed according to the type of the master budget. For example, a child entry with Product Group DVD will be transformed to Item Category AUDIO when it is consolidated into a master budget with Item Category type.

Improved Check and Correct Action in Retail Sales Budget

A new validation and cleanup functionality has been introduced to the Check and Correct action on the Retail Sales Budget page (10012417). The aim of the functionality is to identify budget entries that have a date not matching the budget's Period Type, and to suggest cleanup measures.

Two cleanup options are available when such entries are identified:

  • To consolidate the entries into the budget entry which falls on the first day according to the Period Type. For example, a 22-Oct-2017 entry will be consolidated into the entry of 01-Oct-2017 in a monthly budget.
  • To delete the entries.

New Report: Trend Report

A new report, Trending Report Hist., has been introduced in LS Retail - Replenishment - General - Reports and Analysis. The report provides inventory and sales information for a specific period of time and has the functionality to combine the inventory information of current and previous year.

Variant Suggestions Improvement

The Item Variant Suggestion page, which opened with the Add a New Variant action in Variant Worksheet, has been improved. Records will not be inserted into the Extended Variant Values table (10001413) when the suggestions are populated. The Extended Variant Values records will only be inserted when the actual variants are created.

Retail:

New Barcode Support - GS1 DataBar

Expanded support for barcodes has been implemented as newer barcodes contain more information than the standard EAN barcode. This information is, for example, expiration date, lot numbers, serial numbers, and weight.

 

Discount Offers have been enhanced so automatic discounts can now be given for items with fixed dates (the Valid From Before Expiration Date and Valid To Before Expiration Date fields).

 

For an example of how the GS1 DataBar barcodes can be used, see the LS Nav Online Help.

BarCodes: Configuration Option

In the GS1 DataBar Configuration option, it is now possible to overwrite what to do with an item with an expiration date. You can configure how many days before the item's expiration date you want to block the sale.

You can also specify, how many days before (and even after) the expiration date of a certain item, the POS should display a question asking the customer if he or she would like to buy the item even if the item's expiration date is coming soon (or has passed).

The GS1 DataBar Configuration option can also be used to block the sale of a certain Lot No. This can be helpful when a Lot No. needs to be recalled.

Hierarchy With a Defined Start Date

Web Store can now have an active hierarchy that is applied on a defined start date. The GET_HIERARCHY web service returns the active hierarchy for a store according to the current date and time.

Hierarchy Enhancements

  • The Web Store can now have more than one hierarchies linked to it by adding Hierarchy Date lines to the WI Setup page. Hierarchies and starting dates are selected. Active Hierarchy is then returned according to CURRENTDATETIME when requested for the Web Store.
  • Images and descriptions can now be set for each node in a hierarchy. The Retail Image functionality is used to link nodes to images.
  • When an item is added to a hierarchy, the whole hierarchy is shown from the root to the node.
  • The function Add Items to Hierarchy Node has been enhanced to support filtering on attributes, special groups, and from a different hierarchy node.

For more information see Hierarchies in the LS Nav Online Help.

LS Hardware Station: Improvements in the Management Portal

  • The LS Management portal user interface has been improved to support enhanced customization.
  • An option has been added to select the debug log level.

POS: Column No. Added to Event

POS event MARKEDCOUNTCHANGED now contains information on the active Column and Row in the Source (Data Grid Control).

POS: InvokeScript Function for BrowserControl Added

A new InvokeScript function has been added to the EPOS Control Interface where developers can invoke JavaScripts in the BrowserControl.

 

Note that an option to send POS Command events from the BrowserControl HTML has also been added. Using these two options together, a developer can create custom UI with the BrowserControl using HTML/CSS/JS, and interact with it.

POS: Support for Multiple OPOS Scanners

POS Hardware Profile now provides support for multiple OPOS Scanners.

POS: New Options in Record Zoom Control

New options have been added to Record Zoom Control on the POS.

  • It is now possible to select the field Hide Headerto hide the column headers in the Control.
  • The Header Height field can now be used to control the height of the column headers.

POS: Terminal in Use by Another User - Error Fixed

The error POS Terminal is already in use by user xxx, which occurred when the service tier was stopped while the POS was open, has been fixed. Users are no longer prevented from opening the POS in this situation.

Reduce Locking on Transaction Work Table

Handling of unsent transaction data has been changed to reduce locking. This affects sending transaction data at the end of a transaction and applies to transaction server and web service.

Transaction Web Service Background Processes

Sending transaction data at the end of a transaction, send unsent data, is now also supported as background process. This process is serviced by a background session which then frees up time for the client session running the POS.

Other:

LS Nav Start: Timeout Values not Affected Until Restart

Changing Ping Timeout (ms) and Database Timeout (s)in LS Nav Start will now take effect as soon as the Options dialog is confirmed, instead of on program restart.

Column Number Added to POS Event DATAROWSELECTED

Column number has been added to the DATAROWSELECTED event to determine what column was clicked (if a mouse or finger was used to select the row).

Web POS: POS Menu - Pages

It is now possible to have multiple pages in Web POS menus.