LS Nav (11.05) Release Notes

About This Release

Build no. - 750
Released - October 18, 2018

This version is built on Microsoft Dynamics NAV 2018, build no. 23572

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 2018 (11.05).

New or Enhanced Features

Retail

BackOffice 

Web Service 2.0

The following web service has been created according to the Web Service 2.0 framework:

  • GetPosStartStatus - replaces GET_POS_START_STATUS.

Inventory Management Worksheets Removed

InStore Inventory masks and worksheets have been removed in this version and Store Inventory will be activated. 

Note: If you have not already activated Store Inventory before upgrading to LS Nav 11.05, you should consider doing so, if you wish to upgrade the Inventory masks (see Store Inventory Setup in earlier versions). All worksheets should be posted before the upgrade.

If Store Inventory is not activated before the upgrade, inventory masks will automatically be copied to Store Inventory worksheet setup.

Paying Customer Orders with Gift Cards

It is now possible to use gift cards as payment in eCommerce.

Hardware Station

Improvements in Hardware Profile Setup in LS Nav

A change has been made to the LS Nav POS Hardware Profile Card. It is now possible to detect what devices are available in an LS Hardware Station, and add them automatically to the POS Hardware Profile Card so that the user does not have to type them in manually. 

If a device has already been added, the user is asked if he or she wants to override the device. This simplifies setup and management of the LS Nav Hardware Profile Card.

Replenishment

Replenishment Control Data List 

Replenishment Control Data List is a new page in LS Nav which simplifies the maintenance of Replenishment Control Data by having all the replenishment parameters on a single page.

The new page supports easy definition of views, reusable filters, updates for a group of Items (marked or filtered), and cascaded updates of Item Store Recs from Items. For more information see the LS Nav Help.

Validation of Hierarchy Node Links

Validations have been added to the Hierarchy. The validations take place when you add or update the Hierarchy Node Links for a Hierarchy with the Link Only Once check box selected. The validations apply to the Link Type: 

  • Store
  • Store Group
  • Customer
  • Customer Group.

Recalculation of Threshold Rule Values

The system now recalculates the Threshold Rule Values and updates the No. of Exceptions field in the Purchase, Transfer, and Redistribution Replenishment journals whenever a Purchase or Transfer Order is created. This applies to all areas where the order documents can be created: 

  • The Create Purchase Orders or Create Transfer Orders actions in all Replenishment Journals.
  • The Add Items to Journal report accessible from all Replenishment journals.
  • The Redist. Preview page accessible from the Redistribution Replenishment Journal.
  • The scheduler job which performs the journal calculation and documents creation.

Web POS

EFT Implementation Supports Cancel and Reprint of the Receipt in Last Transaction

  • A functionality has been added to EFT implementation allowing the user to try to cancel a payment that has been sent to PED from the POS.
  • Another functionality has also been added to reprint the PED receipt of the last EFT transaction. This work is part of the ongoing PayEx certifying process for the LS POS.

LS Nav App

The LS Nav App is now available for download: 

Both versions are pre-configured to connect to a demo machine, https://appshell.lsretail.com, using an LS Nav user with a phone-size profile.

When using the demo machine for testing the LS Nav App, several partners may be testing simultaneously and may therefore be connected using the same LS Nav user. In case of a conflict, one solution is to switch to another Nav user (there is no need to change the password as all LS Nav users have the same password).

Available LS Nav users on the demo machine:

Hospitality

New Transfer Table Setting for Small Devices

A new Transfer panel structure that works with two sub-panels has been added.

The structure for small devices contains only one grid at a time, and switches between the order transferred from and the order transferred to (by clicking the header).

The structure for stationary POS (larger devices) operates with two grids at a time in the same way as in previous versions.

Note: When you upgrade to this version, the old Transfer panels must be replaced with the new ones. See the LS Nav Help for more details.

Other options added to transfer:

  • Move item lines between orders by clicking a column.

Order List for Orders on a Dining Table Is Fully Functional

The Dining Table list view now changes to an Order list view to show orders on a dining table (if more than one order is open).

Kitchen Display System (KDS)

New Option When Sending to KDS 

It is now possible to send items to the KDS as they get added to the POS. This is a very common scenario in quick-service restaurants and coffee shops.

A new option has been added to the Hospitality Type Card, the Kitchen Display/Printing field: On Item Added.

When this option is selected, the POS will create a new KOT on the first item added and send to KDS. When more items are added, the POS will simply add them to the existing KOT and send to KDS.

Fixed Issues

Replenishment: Exclusion in Allocation Rule

In Allocation Rule a bug where exclusion was not working correctly has been fixed. The exclusion did not work when the store exists in one of the existing store groups in the Allocation Rule Lines.

Web Service: Suspended Transaction not Deleted in Local Database

When Web Service is used to send a suspended transaction, the transaction is now deleted in the local database. The transaction is suspended in one database and finished in a different database or POS, and is then retrieved again on the original POS (where it shows up in the suspended list, the POS Transaction table).