LS Nav Cumulative Updates 2007 - 2018, Overview

Use the column filters to display features of individual versions or feature groups.
Click the link to the right to open the MS Dynamics NAV feature comparison tool.

Feature
Industry Module
(with link to LS Retail help)

Updated
Offers
Platform
Replenishment
Replenishment
Offers
Offers
Open to Buy
Replenishment
Replenishment
Replenishment
Replenishment
Replenishment

Replenishment

Variant Framework

Platform
Role Center
Role Center
ABC
DD
Hosp
Hosp
Hosp
Inventory
Item
Item
Offers
Offers
Offers
Offers
Offers

POS

POS
POS
POS
POS
POS
Replenishment
Replenishment
Replenishment
Replenishment
Replenishment

Return Mgmt

Special Orders

Vendor Item Library

Forecout

Franchise Mgmt
Pre-pack
Web Integration
Coupon
Coupon
Coupons
DD
Hosp
Item Master
Loss Prevention
Member Mgmt
Member Mgmt
Member Mgmt
Member Mgmt
Member Mgmt
Member Mgmt

Offers

Offers

Offers
Offers
Offers
Offers
Offers
Offers
Offers
Platform
Platform
POS
Replenishment
Sales Commission
Variant Framework

Mobile Inventory
Mobile Inventory
Mobile Inventory
Mobile Inventory
Mobile Inventory

Mobile Inventory

Staff Mgmt

Cash and Safe Mgmt

Cash and Safe Mgmt

eCommerce

eCommerce
Member Mgmt

Mobile Loyalty

Mobile Loyalty
Mobile Loyalty
Mobile Loyalty

Mobile Loyalty

Mobile Loyalty

Mobile Loyalty

Mobile Loyalty
Mobile Loyalty
Mobile Loyalty
Mobile POS
Mobile POS

Mobile POS

Mobile POS

Omni
Platform
Platform

Replenishment

Replenishment

Mobile Loyalty
Hosp
Hosp
Hosp

Hosp

Hosp

Hosp

Inventory
Matrixes
Member Mgmt
Member Mgmt
Member Mgmt
Member Mgmt
Member Mgmt
Mobile Loyalty
Mobile POS

POS
 POS

POS

POS
POS
POS
POS
Service Pack Hosp
Service Pack Hosp

Mobile Hosp
Service Pack
Mobile Hosp
Service Pack
Service Pack Mobile Hosp

Mobile Hosp
Service Pack
Service Pack Mobile Hosp

Staff Mgmt
Service Pack
BI

Click and Collect

Demand Framework

Hosp

Hosp

Hosp
Hosp
Hosp

Hosp
 Hosp

Hosp

Item Master

Life Cycle

Member Mgmt
Offers
Platform
POS

POS

POS

POS

POS
POS
POS
Replenishment
Replenishment
Role Center

Special Orders

Staff Mgmt
Where Used

General POS Auto - detect Hardware

x
 General POS Support for KeyLock devices

POS Gratuity Management

General Role Center & GUI Simplified pages

Fashion Role Center & GUI Lifecycle Planning sub pages simplified

Map OPOS printing to Windows printer in

General Printing
Device Manager

General POS Customer sales history

x
 General POS Device Sharing

General POS Dual Display can display separate Journals

Fashion Permission Permission sets

Fashion Role Center & GUI Simplified version of Retail Setup

General Scale Certificate Scale Certification

x

General Replenishment Warehouse Replenishment

General Web services Web Service Enhancements

General Replenishment Count available days

General LS Nav Start Failover Checks in LS Nav Start

Deals only to display deal modifiers for

General POS
items included in item distribution
x

Member
General Frequent Buyer Program
Management
x
 Hospitality Mobile Hospitality Mobile POS

Hospitality KDS Kitchen Display System

Measurement Unit Popup-Selection Only

Hospitality POS
For Priced Units

Hospitality Product Design Recipe Batch Update Change in Recipe Component

Hospitality Product Design Possibility to Change the Order of Recipe Rows

General Data Director Data Director Web Monitor Release

General Rapid Installation Start Once Added to Rapid Installer

Hospitality Printing Kitchen Printing with Retail POS

Easier, Simpler and a Faster way to Copy

General POS
Transactions
x
 Finish a Sale Quickly with Quickcash -
General POS
Without Total and Specific Quickcash menu

General Items Inheritance of Discount Ban from Product

Hierarchy

General Omni Simplified Setup of LS Omni

Change Replication in eCommerce

General Omni According to new LS Plugin in
nopCommerce

General Backoffice Number Series on Validation Period

General Backoffice Add Hard Attribute to Store and Restaurant

x

General POS Redesign DYNMENU Functionality as POS Dynamic Menu

General POS Add Deals to Dynamic Menus

General POS Add Attributes to Deals and Deals to Dynamic Menus

Apply Modifications Found During Load

General Performance
Test

General Variants New Item Variants Creation

Include Item usage in BOM when

General Items calculating Qty. sold not posted

General Variants Matrix Dimension for Retail Availability by

Variant

Consolidate Actions Related to Item

General Variants
Variants

General POS Design POS Commands Where Used

Retail Message: Notify User When New

General POS
Message

Fashion Role Center & GUI Fashion - Reports

 Member Member Management Account/Contact
General
Management Enhancements
Retrieving Published Offer Related Items
General Omni
for Omni

General Omni Coupons and Points in Cart (Omni)

Web service for Published Offers and

General Omni
Personalized Coupons

Create Web Service for

General Omni
WEB_POS_PRINT_SETTLEMENT for Omni

General POS Loading Card

Hospitality POS Show Allergens on the POS

Hospitality Store Management Set up Hospitality Types in one Place

General POS Posting Exception

Simple Process for Starting or Replacing

General Rapid Installation
POS

Option to e-mail the last receipt or invoice

General POS on POS

Hospitality Store Management Hospitality type setup has been made easier and simpler by using configuration templates

Hospitality Role Center & GUI Hospitality Express Role Center and setup

General Staff Management Staff Management

General Staff Management Employee Portal

 Item Registration replaced with Simple
Fashion Role Center & GUI
Item Registration

General POS Print sales receipt upon request

x
Member contacts mobile number editable
General POS
from the POS

General Demo Data New Restaurant in Demo Data

General POS POS Journal Data-Update Refactoring

POS Data Grid: Hide Empty Rows When a

General POS
New Page Is Added

Confirm if Open Transactions on EOD or Z-

General Backoffice
Report

General Warehouse Adjust Cost - Item Entries

General POS Add POS Command SHOWPANELMODAL

General POS Add POS Command REFRESH_MENUS

General BackOffice Remove "Dimension Extension" from

Variant Dimension Groups
 Menu Type for Journal Lines Stored in
General POS
Posted Transactions

Void Transaction - Slip Includes

General POS Income/Expense Amount and Transaction
Number Is Printed

General Web services Web Service Default Data

General Variants Variant Creation - New Page for Selection

General Variants Add Variant Framework to Items

UOM & Variant Information Missing in

General POS
Mobile Price
Add POS Transaction Linked Tables to
General POS Suspend/Retrieve Functionality Using Web
Services

General Variants Sort Variant Creation Using Logical Order

General Backoffice MSR Functionality for Gift Cards

General Web services More Detailed Web Service Log

General Store Management Store Group in Price Check Card

Menu Type for Journal Lines not Stored in

Hospitality KDS
Posted Transactions

General POS Focus Skin on Active Menu Button

Infocodes Have a New Field to Allow MSR

General Backoffice
Functionality

General Web services Web Service Default Data

Retail Click and Collect Validation of Data for Click and Collect

General Variants Variant Creation - New Page for Selection

General Variants Variant Values Suggestion Page

Add Variant Framework to Items in Fashion

General Variants
Role Center

General POS Add More Tables to POS Commands

Where Used

General Backoffice Where Used for Infocodes

Weather Forecast Integration for Staff

Retail Staff Management
Management

Role Budget Adjustments in Staff

Retail Staff Management
Management Roster Schedule Page

Add Function to Add Shift/Role in Staff

Retail Staff Management
Management Roster

Support External Views & External views

Retail Staff Management on External Lines in Staff Management
Roster
 Change Lookup Pages for Shift/Role to
Retail Staff Management Simple Lookups in Staff Management
Roster

Only Display Name on Employee on the

Retail Staff Management
First Rostering Line

Statements to Action "Show Posted

Document" Added and
Retail
LS Action "Original Document" from
Customer Ledger Entries Removed

Hospitality KDS Menu Type for Deals

Hospitality KDS Setup for How to Handle Transfer and Split

Bill After Bill Is Printed

General POS Seeing When Data Entries Expire

 Option to Delete Before Import on the
General POS
Import Export Worksheet

General Upgrade to LS Nav 2017

Print a Specific Menu Type to KDS and

Hospitality KDS Change the Menu Type of a Line to a
Specific Menu Type (by Pressing a Single
Button)

Retail Attributes Changes in Retail Attributes

 Item Category and Product Group Tables
General Product Design
Adjusted

General Two New Field Types: Media and MediaSet

All Where-Used Instances Now Inside a

General
Single Code Unit

General Point of Sale MSR: Add AutoDisable and DecodeData

Fields to Hardware Profile
 Cleanup of Infocode Where-Used Related
General Backoffice
Functionality

General Changes in Release Purchase Document

General Backoffice Tables Added to Infocode Where-Used

General Web services LS Nav Web Service Test Application

General POS Print Gift Card and Voucher Balance

Retail Staff Management Support for Viable Week Definitions

Profit, COGS, and Sales, Based on Days,

Retail Staff Management
Shown in Roster Analysis View

General Web services Web Service for OMNI Server Stock Query
 Trailing Semicolon in Data Director
Retail Backoffice
Removed

Now Possible to Have Different License

General Omni Keys for OMNI Apps Installed on the Same
Device

General POS New LS Fonts Added

General POS New Example of a POS Look Added

General POS POS Commands

Release Notes and Online Help in a New

General Online Help
Look

LS Recommend Backoffice LS Recommend

 Added: An Option to Clear a Table Even If
Hospitality KDS
KOTs Are Not Served

FOB Created To Update Retail Item Link

General
When There Are Changes in Retail Images

Multiple Levels in Journals Shown With

General POS
Configurable Indents

Set Expiration Date Fixed in Codeunit

General
99000830
Previously Only a Single Return Slip Was
General POS Printed; Now the Slip Is Printed With a
Copy

Now Possible to Specify Which

LS Recommend POS LS Recommend Items Will Trigger a Call to
Azure
General Installation Guide Installation Guides

Hospitality POS: New Rush Option to

Hospitality POS
Create Rush Orders for KDS

Hospitality POS Hospitality POS: Time Registration Error

Corrected

Hospitality KDS Expeditor Bump Printing

General Web POS Web POS Version 1.0 Now Available

 Issues With the Functions Insert Web POS
General Web services Requests and Insert Inventory Mgmt
Requests

General POS New LS Font Added

Hospitality KDS New Permission Setting for Rush Orders

Hospitality POS Sales POS Can Be Opened Directly With

Logon - Skipping the Startup Screen

Selecting a Hospitality Type at Logon - Pop-

Hospitality POS up per POS Terminal

Selecting a Hospitality Type at Logon - by

Hospitality POS
Staff per POS Terminal

For Mobile POS, One Web Request Needs

Retail Mobile POS
an Additional Line
Retail Web services Extended Web Service Created

Retail POS Fix for the Trans. Disc. Benefit Entry

Member
Retail Member Management Online Help
Management
POS Users Can Now Scan a Code128
Retail POS
Barcode with GS1-128 Data

Retail eCommerce Refactoring of eCommerce Sale Handling

Retail Mobile POS Return Items via Mobile POS

Recommendation for a Single Journal Item

LS Recommend POS
in the POS
 Control When and Where to Update
Retail Performance
Replication Counters

For Mobile POS Purchases, LS Nav Now

LS Recommend Mobile POS
Registers Recommended Items

Code in POS Print Utility Removed and

LS Recommend POS
Print Bug Fixed

LS Recommend No Recommendations If the Transaction

Includes a Display Rule and a Member

Old Recommendations from Cache Are Not

LS Recommend POS
Displayed
General Hierarchy New Functionality: Hierarchy

General MS Dynamics Microsoft Dynamics NAV 2017 CU4

Upgrade

General Online Help New Search Filter

General Staff Management Multiple Updates

 Contact Info and Access to Hour

General Staff Management Acceptance Added to Salary Export
Overview
General Staff Management Optimal Hours on Work Arrangement Card

General Web POS Web POS Documentation

Hospitality KDS KDS Data Processing Has Been Improved

LS Recommend Rank Builds not Automatically Deleted

LS Recommend Recommendation Displayed When a

Member but No Items Are in a Transaction

Recommendation Is Not Shown When a

LS Recommend
Sale Is a Return Sale

LS Recommend Auto Increment Property Removed

LS Recommend Object Package for LS Nav

LS Recommend
2015 (8)
 LS Recommend Object Package for LS Nav
LS Recommend
2016 (9)

LS Nav Event Created and Published at the

Retail POS
End of a Transaction

Retail Offers Mix & Match Functionality Change

Retail New Field to Hold Global ID

Retail POS POS Printing: Support for Variable Line

Width (Characters per Line)
General LS Hardware Station A New Way to Connect Devices to LS Nav

Retail Product Design New Language Support Functionality

Retail Product Design New Translation Button

General Microsoft Dynamics NAV 2017 CU5

Upgrade

General Event Viewer Replenishment: Track RIQ Calculation

Progress in Event Viewer

General Indexing Search Index Updated

 Web POS: New Option Added to Browser
General Web POS
Control

Web POS: Search as You Type

General Web POS
Implemented
Recommended Items Filtered Out on the
LS Recommend POS
POS

General Online Help Online Help: Link to Demo Scripts

General Online Help Overview of Cumulative Updates

General Replenishment Item Quantities Calculation Improvements

 Changed Calculation for Effective Inventory
General Replenishment
When Using the Coverage Option

General Replenishment Demo Data Added

General Replenishment Filter Issue in the Purchase Replenishment

Journal

General Replenishment Forward Sales Factor Calculation

General Replenishment Link from the Product Groups Page to the

Replenishment Data Profile Page Removed

Track RIQ Calculation Progress in Event

General Replenishment
Viewer

Worksheet for Production Time with

Hospitality KDS
Comparison to Actual Production Time
Hospitality KDS Item Filtering Added to the Item Section
Routings Page

Hospitality KDS KDS Order Aging Report Updated

LS Omni Known Issues With LS Nav 10.06

 Adjust Coverage Calculation Time Horizon
General Replenishment
(From-Date)

General Replenishment Field Name Changes in Replenishment

Setup
 Hierarchy Relations for Assortment
General Replenishment
Management
 Planned Sales Demand Worksheet
General Replenishment
Enhancements
 Replenishment Out of Stock (OOS)
General Replenishment Calculation Improvements
General Replenishment Retail Budgets, Improvements
 Amount Based Line Discount Has Been
Retail
Fixed

General Web POS Changes in Web POS

 Deal, Store, and Customer Links in
Retail Hierarchy Hierarchies, and Hierarchy Relations
Between Hierarchies
Retail LS Hardware Station LS Hardware Station

Retail Named Relations Between Products

Purchase Orders Created Through Retail

Retail Campaign

POS External Printing: Option to Log and

Retail POS Print a Test Page Has Been Added

Transaction Balance Rounding Supported

Retail Mobile POS by Mobile POS 
 Status Code on Item Status Link Worksheet
Retail Backoffice
Now in Sync

Retail Various Fixes

Negative Adjustment Mode on the

Hospitality KDS, POS
Hospitality POS
 Planned Sales Demand Worksheet
General Replenishment
Enhancements
 Planned Sales Demand Worksheet
General Replenishment
Enhancements
 Planned Sales Demand Worksheet
General Replenishment
Enhancements
 Planned Sales Demand Worksheet
General Replenishment
Enhancements

Planned Sales Demand Worksheet

General Replenishment Enhancements
General Replenishment Retail Budgets Improvements
General Replenishment Retail Budgets Improvements
General Replenishment Retail Budgets Improvements

General Replenishment Improved Copy Budget Function

General Replenishment Budget Validation and Correction

General Replenishment Destination Group Validation in Allocation

Rule

Retail Backoffice Filter Added to AddItemsToHierarchy

Inconsistent Information on Receipts:

Retail
Rounding Difference Corrected

Retail Incorrect Sync Time in Search Index

Management Portal Into Hardware Station

Retail LS Hardware Station Service
Retail LS Hardware Station Service and Console

Retail POS New Event (LS Nav POS API)

Validation of String Length in the On-

Retail POS
Screen Keyboard

Warning Issued if Two Users Are

Retail Simultaneously Trying to Use the Same
Terminal
Server Tools: Control Panel for Functions in
Retail
Hardware Stations

Hospitality, Retail POS Current Item Availability on Button

 Identical Item Lines not Compressed if
Hospitality POS
They Have a Menu Type

Changes in Standard NAV Purchase Unit of

Retail Replenishment
Measure
 Changes in Standard NAV Purchase Unit of
Retail Replenishment
Measure

Retail Replenishment Changes in Standard NAV Purchase Unit of

Measure
 Changes in Standard NAV Purchase Unit of
Retail Replenishment
Measure

Changes in Standard NAV Purchase Unit of

Retail Replenishment
Measure
 Changes in Standard NAV Purchase Unit of
Retail Replenishment
Measure

Changes in Standard NAV Purchase Unit of

Retail Replenishment
Measure

Retail Backoffice New Barcode Support - GS1 DataBar

Retail Backoffice BarCodes: Configuration Option

Retail Backoffice Hierarchy With a Defined Start Date

Retail Backoffice Hierarchy Enhancements

Retail LS Hardware Station LS Hardware Station: Improvements in the

Management Portal

Retail POS POS: Column No. Added to Event

 POS: InvokeScript Function for
Retail POS
BrowserControl Added

Retail POS POS: Support for Multiple OPOS Scanners

Retail POS POS: New Options in Record Zoom Control

POS: Terminal in Use by Another User -

Retail POS
Error Fixed

Retail Backoffice Reduce Locking on Transaction Work Table

Transaction Web Service Background

Retail Backoffice
Processes

LS Nav Start: Timeout Values not Affected

General
Until Restart

Column Number Added to POS Event

General
DATAROWSELECTED
General Web POS Web POS: POS Menu - Pages
 Enhancements in Master-Child Budgets
Retail Replenishment
Consolidation for Retail Sales Budget

Retail Replenishment New Report: Trend Report

Retail Fashion Fashion Role Center, Reintroduction

Retail POS Invalid Barcode on the POS: Improved

Notification

Performance Boost for Serial and Lot No.

Retail
Local Inventory Lookup
Retail POS End-of-Day Declaration Not Allowed

Error Fixed in the Function

Retail POS CurrencyKeyPressed in Amount Rounding
Precision

Retail POS Hardware Profile Multiple OPOS Scanners

Retail POS Hardware Profile Option to Block POS if Drawer Is Open

Retail Replenishment Add Stores to Allocation Rule from Store

Hierarchy

New Action in Allocation Rule Page: Add

Retail Replenishment
Stores from Store Hierarchy
 Extension to Check Rule Action in
Retail Replenishment
Allocation Rule Page

Retail Replenishment Copy Purchase Budget Improvements

Retail Replenishment Hierarchy Relations Hotfix

Retail Replenishment Improvements on Journal Filters

Retail Web POS Control Functions for Context Menus

Retail Web POS Watermark Function

LS Recommend LS Recommend 2.0

Hospitality New Table Allocation Feature

 How to Upgrade to LS Nav 2017 (10.9)
Hospitality
(Demo Data Changes)
Hospitality Known Issues with LS Nav 10.09
General Data Support for Omni Server 2.4

Events in POS Actions

Maintaining SQL Indexes for Unused Keys

Has Stopped

General Online Help Online Help

Retail Hierarchy Events in Hierarchies

Retail POS NAV Events Added to EPOS Controller

Retail Sales Budget Advanced

Retail Replenishment
Improvements
 Retail Sales Budget Advanced
Retail Replenishment
Improvements

Retail Replenishment Store Capacity Management

Retail Replenishment Store Capacity Management

Retail Fashion, Stock Coverage Management

Replenishment

Retail Fashion, Stock Coverage Management

Replenishment
 Fashion,
Retail Stock Coverage Management
Replenishment

Fashion,
Retail Various Improvements
Replenishment

Fashion,
Retail Replenishment Various Improvements

Retail Backoffice Scale Items

 New Worksheets Replace Instore
Retail Store Inventory
Management Worksheets

Retail

Version Check, JavaScript Add-In vs the

Retail Web POS
Server

Hospitality Backoffice Printing Option Added to Hospitality Pages

Hospitality Backoffice Updating Recipe Cost

Hospitality, Retail POS Retail Message Setup, New Check Box

When Using Hospitality Type Without

Hospitality POS
Service Flow, Error Has Been Fixed

When Using the Current Availability

Hospitality POS
Function, Error Has Been Fixed

Hospitality Backoffice Table Allocation V1.1, Online Help

General Upgrade to LS Nav 2018

Retail Backoffice Mobile Tables Removed

Action Management Removed from

Retail Backoffice
Standard Tables

Check Frequency Reset for "Retail message

General
in Use"

Retail Click and Collect New Method of Finalizing Orders

Retail InStore Management ICT Removed

Retail InStore Management Standalone Store Removed

Multiple Web Stores on the Same LS Nav

Retail
Setup

Retail Demo Data New POS in the Demo Data Company

Retail POS Clienteling

Retail POS Commands

Retail POS Performance Boost in Inventory Lookup

Retail Replenishment Allocation Plan Doc. Factbox

Retail Replenishment Journal Filter Fix

 Transfer & Purchase Thresholds
Retail Replenishment
Management
Retail Special Orders Special Order (SPO) Removed

Retail Web POS Multiple POSes Can Use One LS Hardware

Station for Printing

Retail Web services Web Store Basket Calculation Light

Hospitality Offline Call Center Error in Finalizing a Delivery Order

Tender Declaration, Safe Entry Description

Hospitality Hospitality POS
Adjusted
 Journal Lines Disappear after Coupon Line
Hospitality Hospitality POS
Is Voided

General Online Help Release Notes 2017

Microsoft Dynamics NAV 2016 - Feature Comparison Tool

Description

Avail Avail
Year since since
release CU

Price Reduction (price inclusive barcode) 2007 5 0

Store Dashboard 2007 5 0
Purchase Management 2007 5 0
Vendor Performance 2007 5 0
Best customer price from Item Price and Promotions 2007 5 5
Campaign Module 2007 5 5
Open to Buy – User interface improvements 2007 5 5
Buyers Workbench Improvements 2007 5 5
Automatic replenishment to support for Multiple Warehouses 2007 5 5
Replenishment Data Profiles for automatic replenishment 2007 5 5
Planned Sales Demand used by automatic replenishment 2007 5 5
Stock Recall Journal in manual replenishment 2007 5 5
Automatic replenishment log decision and calculation information when adding lines to
replenishment journals 2007 5
5
Variant sales information (dimension of variants)
2007 5
5
Move LS Nav 5.05 to Microsoft Dynamics NAV 2009 platform 2009 6 0
LS Nav support Role Tailored user interface 2009 6 0
Creation of Role Centers: Retail Buyers, Store Manager and Store Associate 2009 6 0
ABC classification by sales and profit amount for items 2009 6 1
Data Replication – committed transactions 2009 6 1
Hospitality – partial table transfer 2009 6 1
Hospitality – item modifiers 2009 6 1
Hospitality – Menu Types 2009 6 1
Item Tracking - lot and serial number support in in-store inventory processes 2009 6 1
Dynamic Item Hierarchy 2009 6 1
Item and soft and hard attributes 2009 6 1
Offer Improvements - trigger on amount validation 2009 6 1
Offer Improvements - trigger on total payment validation 2009 6 1
Offer Improvements - trigger on offer popup validation 2009 6 1
Offer Improvements - trigger on special group validation 2009 6 1
Offer Improvements - trigger on loyalty card validation 2009 6 1
POS Improvement - GUI Menus', Control, Quick Cash, Double lines in journal, POS
Expendability 2009 6
1
Support Cross Selling wit InfoCodes 2009 6 1
Item Finder to simplify item search 2009 6 1
Dynamic Lookup Forms for POS 2009 6 1
POS Extendibility - internal switches to control behavior 2009 6 1
POS Extendibility - all discount registered a specific table - full traceability 2009 6 1
Replenishment reports - Store Capacity and Stock Coverage 2009 6 1
Replenishment - Store prioritization when limited stock 2009 6 1
Replenishment - Replenishment Rule 2009 6 1
Replenishment - Item inherit sales history 2009 6 1
Replenishment - Define stock out quantity (ex: display stock) 2009 6 1
POS Return Management - Return Policy and ability to refund a single line in a transaction
2009 6
1
Special Orders 2009 6 1
Vendor Item Library
2009 6
1
LS Forecourt 2009 6 2
Franchise Management - Document communication between different legal entities and
item master 2009 6
2
Pre Packs 2009 6 2
Web Integration - support connection to web stores 2009 6 2
Coupons Improvements – traceability, benefits, issue, triggers 2009 6 3
Coupons Improvements – serial coupons 2009 6 3
Coupons Improvements – coupon to trigger a offer 2009 6 3
DD Monitoring 2009 6 3
Hospitality – Offline Call Center 2009 6 3
Item Status – new blocking, additional settings 2009 6 3
Loss Prevention - POS transaction analyzing 2009 6 3
Member Management - loyalty and staff club types 2009 6 3
Member Management - multiple levels within clubs 2009 6 3
Member Management - point collection or specific price for members 2009 6 3
Member Management - discount budgets for clubs or individual members 2009 6 3
Member Management - soft and dynamic attributes to segment members 2009 6 3
Member Management - Campaigns 2009 6 3
Offer System – simpler definition of offer triggers/benefits and blocking of other offer
types 2009 6
3
Offer System – multiple benefits like item gift, selection of item from a list, printing of
coupons or additional points 2009 6
3
Offer System – line discount offer to replace InfoCode offer functionality 2009 6 3
Offer System – total discount offer triggered by total transaction amount 2009 6 3
Offer System – tender discount offer, tender type charge, offer statistics 2009 6 3
Offer System – tender type charge 2009 6 3
Offer System – more detailed offer statistics 2009 6 3
Offer System – amount discount 2009 6 3
Offer System – calculation sequence of discount after automatic discounts 2009 6 3
Support web services for transaction services 2009 6 3
Data Director 3 2009 6 3
POS – store credit improvements 2009 6 3
Allocation Plan in manual replenishment 2009 6 3
Sales Commission – per transaction, sales targets 2009 6 3
Variant Improvement – dimension grouping, dimension status, hard/soft attributes
2009 6
3
Mobile Inventory - App supported on Pocket PC and Windows Mobile devices 2009 6 4
Mobile Inventory - App configured from LS Nav server 2009 6 4
Mobile Inventory - Master data lookup 2009 6 4
Mobile Inventory - all in-store worksheet processes supported 2009 6 4
Mobile Inventory - picking and receiving documents process (PO, TO, SO) 2009 6 4
Mobile Inventory - online and offline supported with online data synchronization
2009 6
4
Staff Management 2013 7 0
Cash and Safe Management - gives full control and traceability
2013 7
0
Cash and Safe Management - support bags
2013 7
0
Omni eCommerce solution - support NOP commerce with master data communication
2013 7
0
Omni eCommerce solution - support NOP with LS Nav server basket calculation 2013 7 0
Member Management - publish offers, coupons and offers for Omni Channel 2013 7 0
Mobile POS - shows member information, profile, personalized offers and sales history
2013 7
0
Mobile Loyalty - App supported on iOS, Android and Windows phone devices 2013 7 0
Mobile Loyalty - customer downloads app and registers for loyalty program 2013 7 0
Mobile Loyalty - customer has access to retailers item master 2013 7 0
Mobile Loyalty - shows all store locations of retailer with maps and gps driving instruction
support 2013 7
0
Mobile Loyalty - Item information visibility with store stock availability 2013 7 0
Mobile Loyalty - global text search item master, offers, notification and sales history
2013 7
0
Mobile Loyalty - shows the customers purchase history 2013 7 0
Mobile Loyalty - ability to scan item barcode with phone camera 2013 7 0
Mobile Loyalty - customer uses a QR-code to identify himself to the retail staff 2013 7 0
Mobile POS - App supported on IOS phone device 2013 7 0
Mobile POS - Simple Mobile Retail POS 2013 7 0
Mobile POS - holds master data with simple pricing and LS Nav server basket calculation at
request or at total 2013 7
0
Mobile POS - supports EFT payment cradles to finalize the transaction on the store floor
2013 7
0
Loyalty Portal for customers 2013 7 0
LS Nav supports the Microsoft Dynamics NAV web client 2013 7 0
LS Nav supports the Microsoft Dynamics NAV tablet App 2013 7 0
Automatic Replenishment - Demand Planner - multiple advanced forecasting methods
2013 7
0
Automatic Replenishment - Demand Planner - safety stock calculation with service levels
2013 7
0
Mobile Loyalty – shop on the phone with payment and delivery information 2013 7 1
Hosp. - multiple brand call center 2013 7 1
Hosp. - New external kitchen display system (KDS) 2013 7 1
Hosp. - time modifiers to increase or reduce cooking time 2013 7 1
Hosp. - menu improvements to support order taking at table with a tablet and LS Nav POS
2013 7
1
Hosp. - multiple brand call center 2013 7 1
Hosp - enter order on LS Nav POS by scanning a QR-Code on the customers Mobile Hosp
Loyalty App 2013 7
1
Label printing improvements in back office 2013 7 1
Fashion Matrixes 2013 7 1
Member Management – sales order point calculation 2013 7 1
Member Management – import contact list from LS BI 2013 7 1
Social Media – back office book offers and notifications to Facebook 2013 7 1
Social Media – back office book offers and notifications to e-mail 2013 7 1
Member Management – points for tender type 2013 7 1
Mobile Loyalty – book to social media (Facebook, twitter, e-mail, SMS) 2013 7 1
Mobile POS – cross selling, return item 2013 7 1
POS – inventory lookup profile, item inventory lookup – print, e-mail – remote lookup of
data, POS translation buttons, message 2013 7
1
POS - logoff functions, fade background, command macro 2013 7 1
LS Nav POS - Customer and item information screens accessed by swiping right or left
2013 7
1
LS Nav POS - keyboard quick select of menu buttons 2013 7 1
LS Nav POS - design mode 2013 7 1
LS Start - LS Nav start tool with backup server automatic failback options 2013 7 1
LS Nav POS - inventory stock lookup profile with printing to slip with QR code 2013 7 1
Table Management – status flow, alerts 2013 7 10.01
Hospitality – recipe production, multi brand call center 2013 7 10.01
Mobile Hospitality Loyalty - App supported on iOS, Android and Windows phone devices
2013 7
10.01
Mobile Hospitality Loyalty - customer downloads app and registers for loyalty program
2013 7
10.01
Mobile Hospitality Loyalty - gives the customer access to the restaurants menu 2013 7 10.01
Mobile Hospitality Loyalty - shows all restaurant locations with maps and gps driving
instruction support 2013 7
10.01
Mobile Hospitality Loyalty – create order on device, transfer with QR code 2013 7 10.01
Staff Management – staff day plan changes, plan changes, improved staff day plan
2013 7
10.01
New LS BI – Targit 2015 8 0
Click and Collect - Order from Mobile Loyalty or Web Store with picking and collection at LS
Nav POS 2015 8
0
Demand Planner – sale history adjustments, use sales history from an item/store
2015 8
0
Hosp. - KDS support Offline Call Center, Delivery and Takeout 2015 8 0
Hosp. - KDS reports - Performance Checks, Performance Period Detail,Performance Period
and Order Aging 2015 8
0
Hosp. - KDS ability to delay order 2015 8 0
Hosp. - KOT list view on POS for over-the-counter sales 2015 8 0
Hosp. - service charge and delivery charge supproted by retail charges 2015 8 0
Hosp. - control if adding a item to a printed bill can need autorization or not allowed
2015 8
0
Hosp. - Split relatively 2015 8 0
Hosp. - multi-level mobile loyalty menu be specially valid on certain weekdays or times
2015 8
0
Item status manipulation and overview improvements 2015 8 0
Life Cycle Management with overview of inventory, sell-through and variant availability.
Simple discount price, end-of-lifecycle processing for items 2015 8
0
Social Media – back office book offers and notifications to Twitter 2015 8 0
Archive Offers 2015 8 0
Online Help Improvements 2015 8 0
LS Nav POS - New POS search with free text input with search in multiple tables 2015 8 0
LS Nav POS - Dynamic POS Layout with spanning the difference between portraid and
landscape mode 2015 8
0
Multiple Drawers - multiple drawers per POS with drawers assigned to tender type and/or
currency 2015 8
0
LS Nav POS - POS Print Log with ability to save print lines to POS Print Buffer table.
Accesable from Transaction Registry 2015 8
0
LS Nav POS support of SMS messages 2015 8 0
POS – send out of stock store address to e-mail or SMS 2015 8 0
Retail Message – used in Click and Collect 2015 8 0
Allocation Plan improvements 2015 8 0
Allocation Plan improvements 2015 8 0
New Role Center for smaller Fashion Retailers 2015 8 0
Special Orders - supports partial delivery and cancelation of individual order lines
2015 8
0
Staff Management - Roster page improvements 2015 8 0
Where Used - Images and Retail Images 2015 8 0
Runs Open-Claim-Enable-CheckHealth command on each OPOS device found in the registry on the
computer. If all commands returns OK, the device is selected and Hardware Profile is updated with
the Device Name and set to OPOS Mode. If device is not found or command returns not OK, the 2015 8 1
Profile is updated with Status None and No Device Name.
Support for KeyLock devices that use the ElectronicKeyValue property has now been added.
KeyLock device is selected as before in the Hardware Profile.
When an ElectronicKeyValue is changed (e.g. Dallas Key Inserted/Removed) then the POS will use
the ElectronicKeyValue and check if an MSR Card Link setup exists for it.
If the ElectronicKeyValue exists in the MSR Card Link table and is linked to a Cashier the POS will use
Log that Cashier On/Off.
Typically the ElectronicKeyValue is 8 Bytes long and in the format "0x00, 0x00, 0x00...".
LS Nav will strip this text and create an Upper Case text string of 16 characters where each 2 2015 8 1
characters represent 1 byte (Hexadecimal Encoding).
The text value can therefore range from "0000000000000000" to "FFFFFFFFFFFFFFFF".
The POS Will interpret an empty string and the "all zero" string as Logoff. All other values will be
used to perform a Logon (given that the value exists in the "MSR Card Links" table)

Gratuity Management is an addition to Income/expense account functionality to handle Tips

received from Customers and Tips distributed to the staff using the POS. 2015 8 1
The pages have been modified in such a way that if they are opened with certain filtering, some
fields, tabs or actions irrelevant to the small business are hidden. These can also be values related
to default settings and are hence hidden under the terms of Easier, Simpler and Faster. Details on
the filtering are found in the Role Center user guide.
A mini POS terminal list page has also been created, page SB Mini POS Terminal List (10016324),
and settings have been added to the Mini Item Card (1302). Simplified pages: Retail Users, Store 2015 8 1
Staff Card, Store Staff List, Mix & Match, Store Card, Store List, Tender Type Card, Tender Type List,
POS Terminal Card, Discount Offer, Promotion, Store General Statistic and Promotion List

The Lifecycle Planning worksheet has been updated so that all relevant sub pages are displayed in
a simplified view. Periodic Discounts of the type Item Point are no longer supported via the 2015 8 2
worksheet.
A new Printer Type is now available called WinPrinter in the POS Printer setup. By selecting this
option the system will print to a windows printer without using the POS OPOS Emulation Report.
This option can be used on the POS to print directly (on client side) to a windows printer instead of
OPOS. 2015 8 3
This also enables windows printing for the Mobile POS solutions where printing is done in Web
Service calls (and reports cannot be run).

New Pages have been created to enable POS users to get a simple overview of previously sold items
to a selected Customer, to assist on future sales. These pages can be run on a tablet client on the
POS, using the browser control. This eliminates the need of replicating Customer Ledger from Head 2015 8 3
Office for history browsing.
Drawer Sharing Field has been added to the POS Hardware Profile Table and POS Drawer table. Also
the Printer Sharing field is back in use. Selectin the Sharing check-mark will make the system claim
the device just before use and release the device right after use. Drawer Claim Timeout and Printer
Claim Timeout fields are also added to make the claim timeout configurable (how long to wait until 2015 8 3
device is available).

The Dual Display and POS Terminal can now display separate Journals, using different data tables.
2015 8 4
New permission sets have been created for LS Fashion Express and are included in Rapidstart
packages for Fashion Express. 2015 8 4
A Simplified version of the Retail Setup is now accessible from the Setup Menu located in the Setup
Group on the Role Center ribbon. 2015 8 4
A Test Certificate has now been issued for Scale Certification in LS Nav 2015 (8.00.05) in accordance
to WELMEC 2.2 and WELMEC 2.3 guides. 2015 8 5
When a warehouse is replenished by summing up the need of the stores it serves the suggested
quantity should be brought to reorder point for each store if it is less. Note that this method is not
recommended for the Demand Plan calculation type create store record instead for the warehouse. 2015 5

LS Web Service Client has been improved in terms of disposing of streams properly and other
objects in the Web Service Connection. 2015 5
New parameter Count available days has been added to Replenishment Setup. If this option is set to
true then the days counted in the calculation of Average Daily Sales are from when an item is
available in a store. Default functionality is unchanged, days counted are from the date when the 2015 6
item is first sold.

New option in LS Nav Start, it is now possible to select to not monitor the POS availability while the
POS is running. 2015 8 6
Only items displayed with the deal are items that are valid for the active store, depending on the
item’s distribution setting. Same rule as when the valid price for an item is found.
2015 8 6

The Frequent Buyer Program is a loyalty program which targets customers buying same or similar
items repeatedly. These are repeated purchases and the retailer want to encourage customer
retention, so they give for example one item for free for every 10 purchased.
The required items can be purchased in different transactions. When required number of items 2015 7
have been bought a coupon is issued and can be used in future transaction.
The Hospitality Mobile POS is an app that can be installed to and used by mobile devices and works
with LS Nav Hospitality. It is a solution that enables waiters in a restaurant to take dining table
orders on a mobile device. The Hospitality Mobile POS works the same as a normal Hospitality POS
with a subset of possible actions. The app displays a dynamic menu structure for ordering items and 2015 8 7
deals The structure is set up in LS Nav Hospitality and can be based on POS menus and meal plan
menus to reduce maintenance.

More setup options have been added in the Site Manager for the Display Stations and Chit Control.
2015 8 8
New option field POS Selection = Allowed, Not Allowed, Only if Specific UOM Price has been added
to Item Unit of Measures. This field controls which units of measure can be selected in the UOM
pop-up on POS, and to which the unit of measure can be changed in the journal by the POS
Command UOMCH. Default values for POS Selection can be set on the Product Group. 2015 8 8

New Page under Hospitality/Product Design/Tasks - Recipe Ingredient Replacement. Makes it

possible to change ingredients simultaneously in all recipes the item is included in. 2015 8 8
You can easily rearrange the ingredient lines in your recipes by pressing Up and Down buttons for
the lines. 2015 8 8
The Data Director Web Monitor is a tool that enables a user to view Data Director jobs in a web
browser. The purpose of the tool is to be able to view Data Director host statuses from any device
at any time. The DD Web Monitor installer is located in the Setup folder of the release package. 2015 8 8

Start Once has been added to the Rapid Installer. Start Once offers a simple way of setting up
software and applications on a new host and keep it up to date. 2015 8 8
You can now use the hospitality kitchen printing in a retail store. If the transaction contains items
that are routed to a printer, the printing takes place when the order is paid for, at posting. The
order can be identified with an Order ID that is a queue counter. The order ID is printed on the 2016 9 0
kitchen slip and the customer receipt.

New POS commands have been added:

-COPY_TR - Copy a posted transaction (from the Transaction List) to the POS Journal, only item lines
and discounts re-calculated
- VOID_AND_COPY_TR - Void a posted transaction (use void functionality as is ) and copy it to the 2016 9 0
POS Journal, all except payment lines. Copy items, coupons and discounts.
A new TENDER_K_AM POS Command has been added. It works like the TENDER_K command except
that it can have an Amount in the Parameter as well as the Tender Type ID. This amount can be
dynamic by using a POS Tag (e.g. <#Balance> as the amount.
The Parameter Field of the Menu Button that has the TENDER_K_AM command can then be set to
"1,50.0" which will then insert a Tender (Cash) of 50. Also the Parameter field can be set to 2016 9 0
"1,<#Balance>" which will then insert a Tender (Cash) of the outstanding balance amount of the
Transaction.

When an item is created it will inherit the value of "Not Discountable" from the Item Category and
Product Group. The user can still overwrite this inheritance. 2016 9 0
To make the setup for LS Omni simple the WI Default Data page (10012868) was made accessible in
the Role Tailored Client. 2016 9 0
Changes done to eCommerce replication job according to new LS plugin in nopCommerce.
2016 9 0

Use Number series to create Validation Period and use instead of manual input in code field.
2016 9 0
Hard attributes are now available for stores. Up to five attributes can be set. Hard attribute setup
for items was removed from the Retail Setup card to a new Attribute Setup card containing all 2016 9 0
Attribute Setup.
POS Dynamic Menus appear on the POS like POS Menus, consisting of items. Instead of adding the
exact items into the menu as you do with POS Menus, you can add to a Dynamic Menu a selection
of Product Groups, Item Categories and Special Groups along with items with certain attributes.
When you press a POS menu button with the POS Command DYNMENU that has a POS Dynamic
Menu as parameter, the system builds the Dynamic Menu using the selection and sorting criteria of 2016 9 1
the POS Dynamic Menu. The menu is created automatically each time it is used.

Deals are added to Dynamic Menus if they have an attribute that is included in the POS Dynamic
Menu. A Preview Page for Dynamic Menu has been added to the POS Dynamic Menu Page. 2016 9 2
Attributes have a different structure: Attribute Type does not exist anymore. Instead there is a
specific Attribute Linking table that specifies with which tables the attribute is linked. Further
Release Notes
Chapter 7 - Key Features in LS Nav 2016 (9.00.01) 10
improvements have been made to attributes in order to make working with attributes easier,
simpler and faster.
Attributes can be assigned to deals. POS dynamic menus have a selection option; Attributes. When 2016 9 2
you select by attributes in a dynamic menu, you can select an attribute that is linked to deals. The
resulting dynamic menu is a menu with items (PLU Command behind buttons) and deals (DEAL
command behind buttons).

Some of the Codeunits used on the POS have been modified in order to prevent deadlocks and
increase efficiency. The main changes are in replacing old rec.FIND('-') and rec.FIND('+') statements
with FINDFIRST, FINDLAST, FINDSET and ISEMPTY. POS Post Utility now works entirely on temporary
tables that are flushed to the database at the end of the posting process. 2016 9 2

The Variant Framework button on the Retail Item Card will now open up the Item Variant
Framework page. From this page, new Extended Variant Values can be added and new item variants 2016 9 2
can be registered based on the value setup.
Quantity sold, not Posted calculation for a Retail Item now includes unposted sales of the Item as a
component in Recipes and BOM Items that are Exploded at Statement posting. 2015 9 3
The matrix dimension for Retail Availability by Variant page has been set up in such a way that the
value setup as Dimension 1 in the Variant Framework will be displayed as horizontal-axis, and if the
item consists of two dimensions, the Dimension 2 will be displayed as vertical-axis. 2016 9 3

All actions related to item's variants have been consolidated and moved into the Variant Worksheet
page. The new Variant Worksheet page is now available in the Variant dropdown. This will make it
easier for user to access all variant's functionalities from one page 2016 9 3

The POS command Where Used will now also show the command usage in POS Search, HMP Action
and POS Actions page. 2016 9 3
A button on the POS can be set to automatically inform the POS user that a new Retail Message to
him has arrived by adding a POS tag to a button. The frequency of checks and the text on the button
are set in Retail Message setup.
The status of the Retail Message button is now updated automatically when the POS is idle. 2016 9 3

The Fashion Role Center now has more reports under the reports tab. 2016 9 3
Various enhancements made to the Member Account and Member Contact cards, such as
Factboxes and simplifications. 2016 9 3
New web service LOAD_PUBLISHED_OFFER_ITEMS has been created to get a list of all Items
included in a selected Published Offer. 2016 9 3
The web requests WEB_POS, WI_NC_CALCULATE_BASKET and WI_NC_CREATE_ORDER now support
Coupons and Member Points as payment. 2016 9 3
New web request created, LOAD_PUBOFFERS_AND_PERSCOUPONS, to retrieve published offers
and personal coupons for membership card. Offers valid for an Item can be retrieved too. 2016 9 3

A web service has been created to reprint a card receipt using Samport authorization.
2016 9 3

Loading cards are used to enable a customer to load items onto his order in different sections of a
store or restaurant and then pay for the order at a cashier’s POS terminal. Transactions can be
Release Notes
Chapter 5 - Key Features in LS Nav 2016 (9.00.03) 8
combined by scanning in other loading cards so the customer can pay for more than his own
transaction. The loading card number is a simple number that identifies the customer's order
through this process. The loading card number can be manually entered. It can also be linked to a 2016 9 4
barcode or an MSR card number for immediate scanning or swiping.
Loading Card usage is designed for online POS terminals only.

Certain types of foods can cause an allergic reaction. There are 14 major allergens which may need
to be mentioned through provided information when they are used as ingredients in food according
to legislation in many countries. Allergens are represented by attributes and by using new POS
commands, they can be shown on the POS in a lookup panel for one line or all lines in the journal.
Item modifiers are included, deals and deal modifiers also and the allergens’ attributes for recipes 2016 9 4
are calculated from their ingredients. The Item Finder can be used to find items without certain
allergens.

A Restaurant POS terminal page has been added to the Hospitality Type Card to show where the
hospitality type is visible and to give access to hospitality related settings for each terminal. A link to
the Restaurant Card has also been added to the Hospitality Type Card.
A new factbox has been created for hospitality and added to the Restaurant Card.
The Populate Flow function has been removed from the Status Flow page and instead is 2016 9 5
automatically included when inserting a new flow.
The Posting Exception makes it possible to source an item from one or multiple locations, sell it
from different locations and keep the sourcing location inventory up to date. Example: POS 1 in
restaurant A orders Pizza from the Pizza restaurant. The Pizza restaurant produces the pizza but
restaurant A sells it. Posting Exception makes it possible to produce the pizza in the pizza restaurant 2016 9 5
and then reduce the stock of raw material from the restaurants inventory and increase the same in
restaurant A.

This is a new process for creating the POS Terminal setup on the fly. When implementing or
replacing a POS a web service contacts the central database creates the POS Terminal from a
template and replicates it to the POS database. The same process can be used when you are
replacing a POS. The process will do the same, that is it creates a new POS Terminal instead of using 2016 9 5
the old POS Terminal id. The advantage with this method is there is no need to find last transaction
number, number series, etc., to avoid conflicts.

New POS Commands were created in order to be able to email receipts and invoices.
The four new POS Commands are:
EMAIL_C
EMAIL_LAST_C 2016 9 6
EMAIL_IC
EMAIL_LAST_IC

Hospitality type setup has been simplified and made easier by adding fields that define service type,
guest handling, order guest marking and order identification. These fields control the setup in
various ways and make it possible to check for errors, make relevant fields editable or non-editable
and set appropriate defaults for all menus and panels. Configuration templates are used for
hospitality types and dining area profiles. Certain fields have been renamed and a few Boolean
fields changed to option fields in order to clarify their function. This applies to Hospitality Type and
Hospitality Status Flow that is now called Hospitality Service Flow. Hospitality types can now be
moved up or down in the sequence for the restaurant. Number of guests can be tracked for any 2016 9 6
orders, not just dining table service orders and Sharing Sales Type Filter can be used for non-dining
table service to show orders from multiple hospitality types in the order list for a hospitality type
included in the sharing type filter.

Hospitality Express Role Center and Hospitality Express Setup pages for Small Business have been
added, making it simple and easy to work with. The pages are number 10016350 SB Hosp Role 2016 9 6
Center and 10016351 SB Hospitality Setup.
Changes have been made to the general user interface of the Staff Management module and to the
role center to make it easier and better to use. The scheduling part has been improved and 2016 9 6
functionality has been added.
A new set of features related to the employee portal have been added. 2016 9 6
All Item Registration actions have been replaced to use the Simple Item Registration, similar to the
one used in the Fashion Role Center. 2016 9 6
POS user can select if he wants to print a sales slip or not. New option field Sales Slip in
POS terminal defines if confirmation window appears or receipt is e-mailed. 2016 9 7

Mobile Phone Number has been added to the Member Contact popup on the POS.
2016 9 7
A new restaurant has been added to the Cronus demo data company. The new restaurant
is number S0014, Cronus Cafeteria - Load Card, and has four terminals. This add-on is
specially intended for the new load card functionality that was released with version 2016 9 7
9.00.04.

The POS Journal Grid updates only the lines that need to be updated instead of all lines.
This increases performance substantially 2016 9 8
Both the POS and Dual Display hide empty rows when a new page is added. POS Data Grid
adds a line at the bottom instead of jumping to the top of a new page. 2016 9 8
When Safe Management is in use, clicking the TD_ENDDAY command will display a
confirmation on going ahead with the tender declaration. If the answer is No, the program
backs to the state when the button with the command was pressed (the state of the POS
and the transaction type of the current transaction are not affected). 2016 9 8

Value Entry fields Division, Item Category and Product Group are now filled in when cost
on Item ledger entries is adjusted. 2016 9 8
A SHOWPANELMODAL POS command has been added that can be used on Menu Buttons
to show panels in Modal state. This option gives the opportunity to pop-up panels that are 2016 9 8
smaller in size than the whole POS.

The POS Command REFRESH_MENUS pops up a status dialog while it forces the POS to get
the latest design data changes (Menu Profiles) from the database (e.g. when replicating
data with the Data Director). The shortcut Ctrl + Shift + F5 was also added to the POS to 2016 9 8
run the command.

The Dimension Extension field has been removed from the page Variant Dimension
Groups. 2016 9 8
Restaurant Menu types are now posted with the sales transactions. When a posted
transaction is copied to a new POS Transaction (VOID© command), the menu type
information is stored. A new table, Trans. Hospitality Entry has been created for this that
includes restaurant menu type information per sales entry. It also includes necessary 2016 9 8
information on the Transaction Header for copying a split transaction.

Voiding a POS Transaction prints a slip with total amount. Income/Expense amount is now
included in the total amount and Transaction Number is also printed. 2016 9 8

When Web Service is activated, the TEST_CONNECTION request definition will now be
inserted as a part of the Web Service default data. 2016 9 8
Item created with Variant Framework Code of type Automatic Selection will now pop-up a
new page: Variant Suggestion. This page allows the user to filter and select multiple variant 2016 9 8
combinations.

Fashion Role Center now has a Variant Framework dropdown that contains these pages:
a) Variant Framework Codes Setup, b) Variant Framework Base Values. The Variant action
in the Mini Item Card now behaves similar to the one in the Retail Item Card. 2016 9 8

mPOS now supports price down to unit of measure.

2016 9 9
When a suspended transaction is retrieved from Head Office to same or different POS
Terminal then all information suspended is retrieved back. 2016 9 9

Variants with Framework Codes of type Automatic Selections is now sorted according to its
Logical Order. 2016 9 9
MSR functionality is now enabled for both selling gift cards and using gift cards for
payment. The functionality can be enabled by selecting Allow MSR Cards in the Infocode 2016 9 9
Card for gift card.
New connection log file has been added to the Web Service Client Log functionality. Before
the log created contained two different files with identical names combined from the
request Id and time of creation ending with _1 for request xml and _2 fore response xml.
The new file follows the same naming convention but ends with _3. This file holds the
connection chain used to fulfill the request. One line for each web server connection until 2016 9 9
one succeeds or all fail.

The Store Group field is now available in the Price Check Card for Periodic Discounts. With
the Store Group field, offers can now be tested without necessarily having to pre-select a
Store No. and POS Terminal No.. When a Store Group is selected, the first Store No. and
POS Terminal No. that are attached to the Store Group will be automatically picked up by 2016 9 9
the system.

Restaurant Menu types are now posted with the sales transactions. When a posted
transaction is copied to a new POS Transaction (VOID© command), the menu type
information is stored. A new table, Trans. Hospitality Entry has been created for this that
includes restaurant menu type information per sales entry. It also includes necessary 2016 9 9
information on the Transaction Header for copying a split transaction.

A Focus Skin field has been added to POS Menus. If a skin is selected in this field and
buttons in the menu can have focus then this skin will be used to highlight the button. If no
Focus Skin is selected, buttons that have focus will show a black dotted line within the 2016 9 9
border/edges of the button.

Infocodes now have an Allow MSR Cards field to allow MSR functionality.
2016 9 9
When Web Service is activated, the TEST_CONNECTION request definition will now be
inserted as part of the Web Service default data. 2016 9 9
Price and net price will now be validated before it goes through.
2016 9 9
Item created with Variant Framework Code of type Automatic Selection now will pop-up a
new page: Variant Suggestion. This page will allow the user to filter and select multiple 2016 9 9
variant combinations.
When setting up combinations of Dimensions and Variant Values for a Variant Framework
Code, we can now utilize the Variant Values Suggestion page. It will display all available
Variant Values to be assigned to a Dimension and we can select or deselect values from
the page. This offers a very flexible and effective way to setup Variant Framework Codes. 2016 9 9

Fashion Role Center now has a Variant Framework dropdown that contains these pages: a)
Variant Framework Codes Setup, b) Variant Framework Base Values. The Variant action in
the Mini Item Card now behaves similar to the one in the Retail Item Card. 2016 9 9

The Where-Used action for POS Commands now covers the following tables: a) POS Key
Command, b) POS Context Menu Line, c) POS Test Script Line 2016 9 9
All pages that use Infocode as its source table now has Where-Used action to see where
the infocodes are used. 2016 9 9
Integration to http://www.yr.no web service to receive weather information directly into
the roster scheduling page. 2016 9 9
In the Roster Scheduling page, the user now has access to the role budget settings from
the scheduling page Navigate action. There is also access to the role budget from the Assist
Edit button on the role budget total lines. Basically the user can adjust or view the role 2016 9 9
budget adjustments for the current roster.

In the roster scheduling page, the user now has access to adding a shift and/or role to the
role budgets. This functionality allows the user to edit the base role budgets and add roles
and shifts to the roster. This could be needed if roles and shifts are added to the role
budgets after a roster has been created. See the Add role/shift on the roster action menu. 2016 9 9

In the external view setup there is the possibility to add new views through external
codeunit where the results can be displayed on the matrix per employee. This functionality
can be used by a partner to add new views to the roster matrix or to the analysis pages.
See sample and register codeunit 10015008 as an external in the staff management setup. 2016 9 9
More demo samples and document on usage to come in near future.
Use simplified lookup pages for the role/shift when employee is assigned to the roster
from the Assist Edit button. Release Notes Chapter 4 - Key Features in LS Nav 2016
(9.00.08) 5 The previous lookup pages showed more fields then needed for the purpose of 2016 9 9
these lookups.

When employee is more than twice in the roster (using the add employee line function)
then only show the name on the first line but additional lines are blank to make it easier to
spot that the line belongs to the same employee. The employee can have extra line in the
roster schedule when there is need to assign multiple shifts or role on the employee per
day. Previously the solution would then show the employees name twice which could be 2016 9 9
confusing. Now the additional lines will have the name blank.

Showing retail transaction is now part of showing posted documents when the user
navigates from customer ledger entries.
2016 9 10

A default menu type can now be defined for Deals. The method is the same as for Items: a
different menu type can be set for each restaurant. There is also a new option field in the
Hospitality Type card under KDS, called "Menu Type Deal Usage". The field value is Yes or
No to indicate if a menu type is used for Deals. Release Notes Chapter 0 - 2 If a single line is
selected in the journal, the menu type can be changed for that line. If a menu type needs 2016 9 10
to be changed for multiple lines, it is necessary to mark those lines.

There is now a setup for each hospitality type to control how transfers are handled. This
applies if the bill has been printed, either for the order you are transferring or for the order
for the dining table that you are transferring to. Changing an order after the bill has been
printed is considered non-acceptable for some businesses but necessary for others. 2016 9 10

The Data Entry Expiry Date can now be seen by using the POS command
VIEW_DATAENTRY_BAL. 2016 9 10
An IT manager can now import new web requests via the Import worksheet and let the
import delete the old request setup before he inserts the new one. This way, the IT
manager can make sure there are no leftovers from the previous version (for example 2016 9 10
obsolete fields or tables).

In this first version of LS Nav 2017 no upgrade is done to the existing Division/Item
Category/Product Group hierarchy, except that default values (standard numbered fields
moved in the standard version) are moved to Item Templates, but to keep a similar
approach as before, a new field, Item Template Code, has been added to Item
Category and Product Group. Therefore, as before, when you select a product group for an
item, the default values are set according to the default values of the Item Template. The
default values are are defined on the Item Category / Product Group cards. LS Nav specific 2017 10 0
upgrade is mainly focused on upgrading Picture and Images to follow the standard use of
the new Media and MediaSet data types.

Three commands regarding restaurant menu type can now take a specific menu type as a
parameter. The commands are: 1) BOMMENTYPE (send menu type to kitchen), 2)
MTYPE_CHG (change menu type on selected line(s)), 3) POPUPMENUTYPE (set the
currently active menu type in the POS). Instead of having a pop-up window appear with
the list of available menu types, the waiter can now press a single button to send, for
example, starters to the kitchen. The above commands can also be used in a POS macro: 2017 10 0
for example, to change the menu type of a line to a certain menu type and then send this
menu type to the kitchen, all by pressing a single button.

This is a change made in LS Nav to adapt to new major changes in Dynamics NAV 2017.
Item List pages Hospitality Item List and Retail Item List now support Attribute Filtering in a
similar way as Microsoft Dynamics NAV 2017 does for Item Attributes. Dynamics NAV 2017
uses the newly introduced Item Attributes while LS Nav supports similar filtering on its 2017 10 0
already implemented attributes.
This is a change made in LS Nav to adapt to new major changes in Dynamics NAV 2017. For
the time being, LS Nav will stick to its three-level item hierarchy: Division, Item Category,
and Product Group. Now that Dynamics NAV has introduced multilevel item category
hierarchy, LS Nav has to limit that functionality to a single level by blocking item categories
from owning a parent category. To maintain a similar functionality as before, now that
Microsoft Dynamics NAV has moved default values from item category to item templates,
a new field Item Template Code has been added to the Item Category and Product Group
tables. When a new item is created and a product group selected, the program finds the
relevant item template from the Item Templates Code field in the Item Category and/or
Product Group tables. If the item template has not already been used to assign default 2017 10 0
values, the values are assigned to the item. This combines the new and the old way of
defining defaults and working with default item values.

This is a change made in LS Nav to adapt to new major changes in Dynamics NAV 2017.
Microsoft has introduced two new data types to Dynamics NAV 2017: Media and
MediaSet. These two data types hold a GUID link to the Tenant Media tables. The Media
field has a link to table 2000000184 Tenant Media and the MediaSet field has a link to
table 2000000183 Tenant Media Set. LS Nav Upgrade
Microsoft provided LS Retail with an upgrade process that moves the contents of the
Picture BLOB fields in the standard Dynamics NAV tables to the Tenant Media tables. The
Media and the MediaSet fields now contain a link to the Tenant Media tables. LS Nav has 2017 10 0
also provided a similar upgrade process that moves pictures in the Retail Image, Store, and
Retail Setup tables to the Tenant Media tables.

All Where-Used instances are now inside a single code unit, the Object-Where Used utility.

2017 10 0
For MSR (Magnetic Stripe Reader), an AutoDisable field has been added to the hardware
profile to make this MSR property configurable. 2017 10 0
The following tables have been removed: a) Item Related Assignment (10000766), b)
Infocode Table Assignment (99001549). The page Hosp. Modifier (10001480) has been 2017 10 0
renamed to All Infocodes and Modifiers.

The functions CreateReceiving and CreatePicking have been removed as they are no

longer used. 2017 10 0
The following tables have been added to the infocode Where-Used: a) Dual Display
Infocode Pop-Up, b) Table Specific Infocode, c) Infocode, d) Information Subcode. 2017 10 0

A Test Connection utility application has been added to the Toolbox to test a connection to
a LS Nav Web Service. The application is installed with the Client Components and can be
found in [Program Files (x86)]\LS Retail\NAV\LSWSTestConnection\ if the default install
folder is used. 2017 10 0
A readme.rtf file containing help for the application is located in the folder.

An option is now available to print the balance of gift cards and vouchers when using the
POS command VIEW_DATAENTRY_BAL without starting a transaction. 2017 10 0
In the Staff Management Setup the user has the option to define which weekday starts the
week. The default start day is Monday, which complies with the ISO standard and the 2017 10 0
Microsoft Dynamics NAV default.

The Roster analysis (accessible from the Roster page and Roster list) shows the COGS (Cost
of Goods) and a profit total per day. The formula is: Total Sales-COGS-Total Salary=Total
Profit. The prerequisites for showing these values are: a) The store and department must
be assigned on the Work Location card, b) The G/L Sales account filters must be set in the 2017 10 0
Staff Management setup to filter which revenue accounts will be summarized for the sales
total.

The web service method MM_MOBILE_GET_ITEMS_IN_STOCK, which is used by an OMNI

server to query for item inventory information in LS Nav, has been enhanced in the
following manner: a) Store_No is now an optional field. If the OMNI server did not supply
any Store_No, then LS Nav will return the inventory status for all stores, b) Reorder 2017 10 0
information is now included in the results returned by LS Nav.
A trailing semicolon has been removed from the Connection string in the Distribution
Location table. The semicolon caused the Data Director to not always select the correct 2017 10 0
client when replicating objects.

Hosting of the Omni App license key and Device ID has been moved from the POS
Terminal table to a separate new table called MobileLicenseRegistration, making it
possible to store more than one Device/License connection per terminal. 2017 10 0

Two new fonts have been added to the LS Nav system fonts: LS1 and LS2. These fonts
include many icons that can be used by the POS for buttons. LS1 contains icons for
hospitality use while the LS2 icons are general ones intended for retail. Included with the 2017 10 0
fonts are PDF sheets with an overview of the icons.

The new POS look is called #LEO and is included in the demo data company. An example is
available in store S0004, POS P0009 (color option) and P0010 (black/white option). 2017 10 0

There are no changes to the POS commands in this release. 2017 10 0

The Release Notes and the LS Nav Online Help now have a new look. The Release Notes
are now included in the Online Help and will be published as separate notes per release,
instead of the previous cumulative document. Starting with this release, older release
notes will remain available in the Online Help. A print version (PDF for two-sided printing)
is provided in the Online Help and in the installation package. The Online Help search
engine has been improved. Users can search across the product help and the included 2017 10 0
Microsoft Dynamics NAV help.

LS Recommend is a new tool in Dynamics NAV developed by LS Retail to help their

customers recommend products to their consumers based on the consumers' purchase
history. LS Recommend provides item and user based recommendation. All manipulation
and configuration of LS Recommend is done in Back Office LS Nav. The recommendation
can be displayed in the LS Nav POS or printed on the slip, and it can also be displayed in LS 2017 10 0
Omni eCommerce and mobile POS from version 2.3.0.
Lets the user set up the service flow in a restaurant so that every time a payment is
received for a dining table, all KOTs (Kitchen Order Tickets) are posted, whether they have
been served or not. This is useful for restaurants where prepayment is never allowed; the
guests always pay upon leaving. In case something went wrong with serving and bumping
orders in the kitchen, this option makes sure that on payment, the dining table is free
again. This behavior is controlled by the Table Is Cleared field (the On Payment Regardless 2017 10 1
of KOTs option) in the Hospitality Service Flow page.

When a Retail Image is linked to an Item, the associated MediaSet (GUID) is now mirrored
to the Item Picture field (MediaSet). In other words, the MediaSet is mirrored from the
Retail Image to the Item whenever the Retail Image or the Retail Image Link is changed.
This is done to reflect changes in Retail Images onto the Item and subsequently for the 2017 10 1
changes to be shown in the brick view of the web client.

To show the relationship between lines in journals, so that POS users, who are working on
the journals, can better see which lines belong together. Instead of previously having only
a single level, there can now be multiple levels of indentations. An Indent Symbol for each
level can be defined in the Interface Profile. 2017 10 1

The function previously set New Expiration Date instead of Expiration Date. This has now
been fixed. 2017 10 1
A return slip is now always printed, even when a receipt slip is not printed.
2017 10 1

By setting a Display Rule, an LS Recommend user on the LS Nav POS can now select which
items will trigger a call to Azure to get recommended items in return. Display Rules are set
on item hierarchy levels, such as product group or item category. The rules are linked to a
model and can be accessed via the Models pages. 2017 10 1
LS Nav Installation Guides are now available on the LS Nav Online Help web. The three
guides, the Installation Guide LS Nav 2017, Online Help Installation Guide LS Nav 2017, and
the Toolbox Installation Guide LS Nav 2017, have been combined in a single guide,
the Installation Guide LS Nav, which is now part of the online help and is also available as a 2017 10 1
PDF document in the release package.

A RUSH option is now available in the Send to KDS - CONFIRM window. This option gives
any KOT (Kitchen Order Ticket) top priority when it is sent to the KDS. You can also RUSH a
KOT that has already been sent to the KDS, by pressing the Rush KOT button on the
KDS Order Kitchen Status panel. This ticket then becomes the first ticket in the KOT queue. 2017 10 2

It is now possible to call the Time Registration command (SHOWPANEL Parameter

#TIMEREGROSTER) from the Hospitality Pre-start Panel. The commands STAFF_ENTRY and 2017 10 2
STAFF_EXIT can also be entered.

When you configure KDS, you can now set up expeditor bump printing, if you want KOTs to
be printed at the same time they are bumped from the KDS Expeditor display station. 2017 10 2

The Web POS module, version 1.0, is now available in LS Nav. This is a low footprint POS
that runs in a web browser. The Web POS 1.0 is a production ready version for new
installations that use EPSON EPOSPrintAPI for printing and scanning (OPOS devices not
supported). Scanning is also available via keyboard input. The Web POS is feature
complete for retail. The Web POS is compatible with and tested on the latest versions of
IOS 10, Chrome, and iPad Air 2. Known issues: a) In order to modify the appearance of the
POS you will still need to use the Windows client to run some of the back-office pages and
Design Mode.
b) Voiding posted transactions will cause an error in a data grid that crashes the POS. 2017 10 2
c) Buttons with an access restriction are not “grayed out”. The system will show an error
when trying to use a COMMAND that is restricted to the user; however, the POS will not
gray the button out.
Running the Insert Web POS Requests and Insert Inventory Mgmt Requests functions in
the Web Service Setup deletes some manually added App_ID nodes in the Demo Data.
Please note that if you run these two functions, you will have to add again the App-ID
nodes to requests: WEB_POS_GET_DEVICEID, WEB_POS_SET_DEVICEID, 2017 10 2
IM_GET_SETUP_DATA.

LS3 is a new font that has been added to the LS Nav system fonts. This is an addition to the
LS1 and LS2 fonts. LS3 includes many icons that can be used by the POS for buttons. 2017 10 2

A manager can now define in the manager interface if he alone or the staff should have
permission to rush an order. 2017 10 3
For a hospitality type that functions like a normal retail POS, the system can open the Sales
POS directly at logon. The system skips the startup view and saves the user from seeing a
list of unfinished transactions (usually an empty list) and pressing the New action item. 2017 10 3

It is now possible to have hospitality types, which are displayed on a POS terminal, appear
in a pop-up page at logon. This makes it easy for the staff to decide, right at logon, which 2017 10 3
hospitality type they are going to work with.

It is now possible to control which hospitality type is selected at logon. A staff member can
have a default sales type specified per POS Terminal. The system uses the sales type to
determine which hospitality type is selected, when the staff member logs on to a POS 2017 10 3
terminal with hospitality types.

For Mobile POS a line is missing in a web request in LS Nav. To fix this do the following:
Open Departments - LS Retail - Administration - Web Service Setup.
Click the Web Requests action.
Select web request WEB_POS_GET_DEVICEID, and click the Request xml action.
On the WS Request Setup page, add a new line including:
Level: 3
Node Type: Normal 2017 10 3
Source Type: Text
Source: App_ID Note: This fix in only needed for mPOS when it is used with a valid
license.
This is a new web service, based on the existing CUSTOMER_ORDER_CREATE web service.
The new service adds the possibility to log Name and Address for mail delivery. 2017 10 3

The Post Utility in the POS has been fixed to refer correctly to a temporary version of
the Trans. Disc. Benefit Entry table. 2017 10 3
Help topics covering the  Member Management component are now included in the LS
Nav Online Help. 2017 10 3
The POS now extracts the Item Barcode from segment 01 GTIN in a Code128 barcode.
2017 10 3
A new back-end functionality has been implemented in LS eCommerce Web Store:
the Customer Order Table has been redesigned to handle eCommerce orders. Now a
Customer Order is created via Web Service and a linked Sales Order is created
subsequently or later by the Scheduler. After a Sales Order is posted, a transaction is 2017 10 3
created that contains the Customer Order.

Refund by receipt is now supported by the web request WEB_POS, command REFUND.
Example of usage:
Using the web request GET_TRANSACTION, a posted transaction is retrieved from the main
database to the mobile POS. The Refund Qty. field in the Trans. Sales Entry table shows the
number of items that have not been refunded already.
A mobile transaction is created on the mobile POS. For each line, the field Quantity is set
to the number of quantities to be refunded.
Using the web request WEB_POS and the REFUND command, the mobile transaction is
then recalculated and verified. The REFUND command returns a return sale transaction
which is fully calculated according to the value in the Quantity field.
The mobile POS then adds the payment lines to the mobile transaction that was returned 2017 10 3
by the REFUND command. Finally, the REFUND transaction is posted by using web request
WEB_POS and the POSTPRECALC command.

The user can now select a line in the item journal in the POS, and press a button to ask for
a recommendation based only on that particular item. The stock levels of the 2017 10 3
recommended items are always shown.
It is now possible to control if replication counter fields in transaction tables are updated
when records are inserted or modified. This is to improve POS performance when no
replication is needed from a location.
This functionality is controlled by a new flag, Skip Repl. Counter Update, on the
Distribution Location card where maintenance of replication counters can be disabled. The
replication counter is not updated, if this flag is set for the counter's distribution location.
The current location is controlled by the Retail Setup Distribution Location field.
The final control is that if the Retail Setup field points to a distribution location for which
this flag is set, the replication counters in that location are not updated. In all other cases
the process remains as before, that is the replication counter is updated.
This functionality can be used as performance boost wherever replication of transactions is 2017 10 4
not needed, for example in all online setups or at some specific location like Head Office.

LS Nav now registers items that are recommended by LS Recommend in Mobile POS sales.
2017 10 4
If the Print Recommendation on Slip check box in the Display on POS FastTab on
the LS Recommend Setup card is the only check box that is selected, a call to get
recommendations from Azure is triggered. If either one or both of the other options on the
FastTab are also selected (including Print Recommendation on Slip), previous 2017 10 4
recommendation results within the transaction are used to print on the slip.

When a display rule is active, recommendations are not triggered, if there is a member in
the transaction and no items that trigger recommendation according to the active rule. 2017 10 4

Now old recommendation items from the POS cache are not displayed as recommended
items. 2017 10 4
Multilevel hierarchies can now be created for items. A hierarchy can be filtered by Store
Distribution as well as by Attributes. Hierarchy information can be retrieved by Web
Requests. Items can be added to hierarchies directly from the Retail Item card, and users
can look up where an item is located in the hierarchies. 2017 10 4

 cumulative update 04 for Microsoft Dynamics NAV 2017 has been released. The update
includes all application and platform hotfixes and regulatory features that have been 2017 10 4
released for Microsoft Dynamics NAV 2017.

The Online Help search bar now has a search filter. Click the filter icon, located to the right
in the search bar, and use the filter to narrow your search and limit it to one of the product 2017 10 4
categories.
Main issues that have been covered:
a) When an employee's salary is based on quantity of hours or thresholds, accepted and/or
rejected salary entries are re-calculated for future entries
b) Cosmetic fixes
c) Shift exchanges are supported on Employee Portal
d) Optimal hours per month can have specific figures per month
e) Enhancements on Administration of salary export:
i) Access to responsible person
ii) Now possible to see location closed period
iii) Now possible to see how many salary entries are still open
iv) Access to hour acceptance
f) Employee card
g) Access to absence history
h) Send roster email
i) Time acceptance page:
i)Edit option 2017 10 4
ii) Bug fix, when roster does not exist for the current date
j) Vacation planner:
i) Cosmetic fixes
ii) Bug fix when displaying weeks
iii) Add month view selection showing entries per day
k) Time Entries, History added to Posted menu pane
l) Tooltips added to role center, Employee card and roster view.

Contact information has been added to the Administration section in Staff Management
(Salary Export overview) to provide the supervisor with easy access to the staff by email or
phone in case he needs to push them to close entries.
The overview now provides access to the Hour Acceptance page where a supervisor for
multiple locations can view status, contact local supervisors, accept or reject entries, all to 2017 10 4
clear the road for exporting a period to salary.
An option to have month specific hours has been added in the work arrangement setup. A
more specific setting of optimal hours per month is now possible on the Work 2017 10 4
Arrangement card with access to settings per year/month.

Online help has been added for the Web POS. 2017 10 4
The processing of KDS data has been improved and requires data upgrade. A new
configuration, which specifies next station and production order, has been added for the
preparation and expeditor display stations. This configuration is set up manually, and an
action can be run to update the KDS data for KDS reporting. Two new KDS reports have
been created: 1) KDS Performance Station: this report tracks ticket time for the display
stations grouped by KDS report period and 2) KDS Performance Item: this report gives an
overview of the average ticket time for items, product groups, or item categories. By
selecting Split Entries on the Transaction register for the original transaction, it is now 2017 10 5
possible to view transactions that were created by splitting the original transaction.

Rank builds are now prevented from being deleted in automated build procedures.
2017 10 5
When there are no items in a transaction but only a member, a recommendation is
displayed based on the member's previous purchases. This only applies when there is no
active display rule. 2017 10 5

A recommendation is not shown when a transaction is a return sale.

2017 10 5

In order to make replication easier, an auto increment property has been removed from
2017 10 5
tables 10016252, 10016257, and 10016261.

An object package with LS Recommend objects for LS Nav 8.00.08 is available on the
Partner Portal. The package consists of new and modified objects and help code units that 2017 10 5
generate demo data for the solution. See guidelines included in the package.
An object package with LS Recommend objects for LS Nav 9.00.10 is available on the
Partner Portal. The package consists of new and modified objects and help code units that 2017 10 5
generate demo data for the solution. See guidelines included in the package.

A new integration event, OnAfterPostTransaction, has been added to the POS Post Utility.
2017 10 5
Mix & Match least expensive offers has been changed back to optimize customer value.
This was the default until version 9.00. Now the offer picks all items involved from the high
end and optimizes the customer value, eliminating the possibility of multiple transactions
giving better results than selling all in one transaction. A new check box, Skip Least Exp.
Customer Opt., has been added to the Mix & Match card to overwrite this optimizing
behavior. It is now possible to set up offers to behave as in version 9.00. If this check box is
selected, the offer will select the least expensive items from the lower end, therefore 2017 10 5
making it possible for the customer to get a better deal by dividing the purchase into two
or more transactions.

This modification lets transactions be exported as XML files for review by local tax
authorities. This is also known as “Fiscal Printing”. Tax authorities issue global codes that
are added to the Tender Types, Product Groups, and POS Commands tables. Store
Management can group their items as before, but now they can also group by predefined
codes for outbound purposes. The code is added to the Outbound Code field in the tables
mentioned above. When the Outbound Code has been added to the POS Commands table, 2017 10 5
LS Retail will start logging all activity for the selected command, making it possible to
export the data.

It is now possible to use more than 40 or less than 40 characters per line in POS printing.
Until now, the number of characters was fixed to 40 characters. Fields have now been
added to POS Hardware Profile and POS Printer to set the characters per line for printing.
The current design for printing (in the POS Print Utility codeunit) has not changed ('#L####
### #' and so on, 40 characters), but this new feature will automatically cut or extend the 2017 10 5
design, depending on the selected Line Length for the printer.
With this release the LS Hardware Station is introduced for the first time. This is a new
component that is intended to take care of the communication with external devices. The
Hardware Station service has a well-defined interface that is based on SignalR, a proven
protocol from Microsoft. In this release the focus has been to connect the WebPOS with
the LS Hardware Station. The goal for coming releases is to provide support for EFTs with
the LS Pay product as well as other devices commonly used with LS Nav. Supported devices
in this version are: an OPOS cash drawer, OPOS scanner, OPOS line display, and an OPOS
printer.
Documentation for LS Hardware Station is available in the LS Nav Online Help (Retail - POS 2017 10 5
- Hardware - LS Hardware Station - How to: Set Up LS Hardware Station).

A new functionality, Language Support, has been added under BackOffice - Product Design.
With this functionality all field values in all tables can have a translation in different
languages stored in the Data Translation table. On the Data Translation Setup page there is
an Excel Import/Export functionality that can be used to get data translations in and out of
LS Nav. Currently, the Language Support functionality is only available as part of 2017 10 5
BackOffice, but it can be sent to LS Omni via data replication.

To make it easy for the user to access the Translation system in LS Nav, it is now possible
to create a translation button whose function it is to go over the setup and find the correct 2017 10 5
record in the Translation system.

An overview of cumulative LS Nav updates, version 8 up to current version 10.05, is now

available in the online help. Click the link on the home page or the Release Notes page to 2017 10 5
open an Excel document with filtering options.

The RIQ (Replenishment Item Quantity) calculation progress can now be tracked in Event
Viewer. You enable the option by selecting the Track Progress in Event Viewer check box
on the Replen. Setup page. The Items Log Frequency field should be filled in with a value to
indicate how frequently the calculation progress should be tracked. 2017 10 5

Search indexing has been updated with a progress dialog box that shows how long the
indexing will take. 2017 10 5
A new option has been added to the Browser Control in the Web Client. The option
enables Browser Control to be used as a generic HTML element instead of an IFrame
element. This gives the control more options and access to the DOM in the Web POS 2017 10 5
instead of being sandboxed in the IFrame as before.

The "Search as you type" function on current input has been implemented for Web POS.
2017 10 5
If a recommended item does not exist in the POS database, the item is filtered out from
the recommendation results on the POS. 2017 10 5
The LS Nav Online Help home page now has a link to a list of demo scripts on the Partner
Portal. 2017 10 5
An overview of cumulative LS Nav updates, version 5 up to current version 10.05, is now
available in the online help, see here and here. The link opens an Excel document with 2017 10 5
filtering options.

Query-based calculation approach in Replen. Item Quantities calculation: this can be

enabled with the field Enable Query in the Replenishment Setup. By enabling the
functionality, the calculation codeunit (10012200, Replen. - Calc. Qtys) utilizes new Query
objects to calculate the Replenishment Item Quantity table, instead of the original nested
loop table read approach. Activating this feature reduces the calculation time due to less
reads from the SQL server, but increases RAM consumption of the NAV service. Parallel
calculation approach in Replen. Item Quantities calculation: by enabling this functionality,
the items to be calculated are put into calculation buckets according to the number of
existing parallel NAS and Schedulers. The calculation is done on the parallel NAS jobs, and
the master job on the primary NAS waits until the sub-jobs are finalized, before it
continues with other Scheduler jobs. A detailed description can be found in Replenishment 2017 10 5
Calculation using Multiple NAS LS Nav 2017 (10.04) Memo.pdf in the folder "Older
Documentation" in the released files for the cummulative update. The new approaches
can be combined or used individually.
New fields have been introduced to Replenishment Setup to define the E363calculation
horizons for the Effective Inventory calculation. When the calculation option Coverage is
chosen, the new fields Sales Order Coverage Days, Purchase Order Coverage Days, and
Transfer Order Coverage Days on the Replen. Setup page, the Effective Inventory FastTab,
are used instead of the fields Store Stock Cover Reqd (Days) and Wareh Stock Cover Reqd
(Days) from Item, Item-Store Record, or Data Profiles. This affects the Effective Inventory 2017 10 5
calculation only. This has no effect for the calculation options Include and Exclude.

Demo data have been added to Demo Database 2017 10 5

Filtering on Vendors in the Purchase Replenishment Journal did not work when Data
Profiles were assigned to Items indirectly by using Divisions, Item Categories, or Product 2017 10 5
Groups. This has now been fixed.

The calculation of the Forward Sales Factor has been improved: it now considers the
Invoiced Quantity instead of the Adjusted Quantity from table Value Entry. This provides 2017 10 5
more accurate results.

A link from the Product Groups page to the Replenishment Data Profile page has been
removed. Instead, use lookup in the Replen. Data Profile field on the Product Groups page. 2017 10 5

The RIQ (Replenishment Item Quantity) calculation progress can now be tracked in Event
Viewer. You enable the option by selecting the Track Progress in Event Viewer check box
on the Replen. Setup page. The Items Log Frequency field should be filled in with a value
to indicate how frequently the calculation progress should be tracked. 2017 10 5

The Production Time Worksheet can now be used to adjust the production time of items
and recipes on KDS preparation stations. It is also possible to compare the assigned
production time on the items to the actual ticket time on preparation stations. 2017 10 6
Item filtering has been added to the Item Section Routings page to make it easier for the
user to see which lines apply to a specific item.
A Retail Item/Recipe Station Mapping Check page has been added where the user can see
to which display stations selected items are mapped with certain test criteria.
The online help for the Kitchen Display System has been reorganized in order to make the 2017 10 6
help topics easier to find.

The KDS Order Aging report has been updated to use queries. The report gives an
overview of how long it takes to prepare KOTs. The report can show totals per KDS report 2017 10 6
period or information on each KOT for the selected time period.

The latest LS Omni release, v2.3.3, has the following known issues with Nav 10.06.
iOS Mobile POS:
When paying an amount that is not in the currency denomination, an error occurs yet a
tender line is still created.
App crashes when a loyalty contact pays with points.

Android Mobile POS:

App crashes when the user pays with cash and the currency is changed afterward. 2017 10 6
App crashes when a loyalty contact pays with points.
This fix is for the Effective Inventory calculation, using calculation type Coverage.
In this calculation type, Sales Orders (Purchase Orders, Transfer Orders) were considered
within a time range from tomorrow ("WORKDATE + 1") until the defined time horizon in
the Replenishment Setup. This created problems in the calculation: if delayed and/or
undelivered, orders remained in the system. Replenishment proposed to reorder these
orders when their shipment/receipt date went into the past, because they went out of the
calculation horizon.
The lower date range has now been changed to zero date (0D). This means that the
Effective Inventory calculation will now expect all undelivered/delayed orders with
delivery/receipt date in the past as being "on the way" and will not propose substitute 2017 10 6
orders, unless the users deletes the old orders. This is according to standard NAV
principles.

The following fields in the Replenishment Setup page have been renamed:
RIQ Enable Query is now RIQ - Enable Query
OOS Enable Query is now OOS - Enable Query
Track Progress Frequency is now Item Counter Interval. 2017 10 6
Hierarchy Relations is a new concept in LS Nav which lets you create relations between
two Hierarchies of the same or different type. A Hierarchy is a flexible tree structure with
Nodes which allows the linking of Items, Deals, Stores, and other entities to the Nodes.
This concept can be used for multiple purposes, one of which is the creation of
Assortments. To define an Assortment a relation is created between an item-based
Hierarchy and a store-based Hierarchy to define which items are available/replenished in
which stores.

The assortment rules are stored in the Item Distribution table which can be maintained on
the Retail Item Card, FastTab Distribution. Hierarchy Relations can be used to maintain this
information in a simpler and faster way. Hierarchy Relations also let you update the
relevant tables manually or via Scheduler Job.

Supported features:

Easy creation and maintenance of Hierarchy Relations

Top-down data maintenance approach with inheritance
Copy function for Hierarchy Relations
Maintenance of multiple versions of Hierarchy Relations (via Starting Date) 2017 10 6
Simple work log
Comments for applied changes
Manual creation of Item Distribution records
Manual creation of Replenishment Control Data (Data Profiles)
Scheduler based creation of Item Distribution and Replenisment Control Data.
New Planned Demand Types
In this release new calculation types for Planned Sales Demand are added. In previous
releases a forecast quantity could only be substituted with a planned substitute quantity.
With this release new types are introduced to add to the forecast quantity with absolute
numbers or % factors. This makes it very easy to cover complex demand changes
(overlapping effects) or demand changes for heterogeneous destinations (varying store
sizes, regional aspects).
New fields, Line No., Planned Demand Type, Planned Demand Event, and Status have
been added to the Replen. Planned Sales Demand (10012374) table and the Replen.
Planned Sales Demand (10012322) page.

Also, the Planned Demand (Qty.) field has been renamed to Planned Demand.

Three types of Planned Demand Type can now be selected from the Replen. Planned Sales
Demand page:

Substitute Quantity - the input Planned Demand will be used to substitute the average
daily sales of the affected item.
Additional Quantity (to Forecast) - the input Planned Demand will be added on top of the 2017 10 6
average daily sales of the affected item.
Additional % Factor (to Forecast) - the input Planned Demand will be treated as a % factor
which added on top of the average daily sales of the affected item.

Planned Sales Demand Events

Planned Sales Demand lines can now be linked to a Planned Sales Demand Event and be
maintained directly from the Event page. Prior to this release, Planned Sales Demand
could only be maintained manually on the Retail Item Card, which is inconvenient,
especially when a large number of items is involved. As a solution to this, a new Replen.
Planned Events (10012326) page has been introduced to allow maintenance of Planned
Sales Demand in one place. The page can be found in LS Retail - Replenishment -
Automatic - Replenishment Planned Events.

Simple Maintenance of Planned Sales Demand

Planned Sales Demand are easily maintained by using the Add Lines and Remove Lines
actions on the page for Planned Sales Demand Events. Those actions let the user add (or
remove) Planned Sales Demand lines by using reports with a large variety of filters.

Linking Planned Sales Demand to Discounts and Budgets

Planned Sales Demand is a component of Automatic Replenishment and influences the
proposals for Purchase Orders and Transfer Orders. Linking the Planned Sales Demand to
Budgets and Discounts lets the user plan promotions or seasonal sales which are picked up
and considered by Replenishment.
An event can be linked to Periodic Discount or Retail Sales Budget and Planned Sales
Demand can then be directly created from the Periodic Discount or Retail Sales Budget by
using the Update Lines action. Currently, Discount Offers and Multibuy Discounts are
supported, and the Retail Sales Budget must have Budget Type Item, Period Type Day, and
budget entries with Store No.
Two approaches have been introduced to improve the performance of OOS calculation:
1. Query based calculation approach - this can be enabled with the OOS - Enable Query
field in Replenishment Setup. By enabling this functionality, the calculation codeunit
(10012203, Replen. Out of Stock Mgt.) utilizes new Query objects to calculate OOS instead
of the conventional nested loop table read approach. Due to fewer reads from the SQL
server, enabling Query reduces the calculation time while it increases RAM consumption of
the NAV service. It also produces more accurate results as backdated-posting item ledger
entries (ILE) are taken into consideration when performing the OOS calculation.
2. Parallel calculation approach - by enabling this functionality the items and ILEs to be
calculated are put into a calculation bucket according to the number of existing parallel
NAS and Schedulers. The calculation is done on the parallel NAS jobs and the master job on
the primary NAS waits until the sub-jobs are finalized before it continues with other
Scheduler jobs.
These new approaches can be combined or used individually. A detailed description is 2017 10 6
available in the document Replenishment Calculation using Multiple NAS LS Nav 2017
(10.06) Memo.pdf in the Older Documentation folder delivered with the cumulative
update.
Enhanced Maintenance of Budgets
A Store No. filter has been introduced in the Edit Retail Sales Budget (10012416) and Edit
Retail Purchase Budget (10012415) pages. This allows easy maintenance of budget entries
for individual stores in Retail Sales Budget and Retail Purchase Budget. The Store No. filter
is defaulted with the Store No. from the Retail Sales Budget or Retail Purchase Budget
page, but the filter can always be changed to another value. The budget lines are
calculated according to the selected store in the filter. If no Store No. filter is selected,
budget lines will be recalculated to show the consolidation of all entries. Also, the fields in
the Edit Retail Sales Budget and Edit Retail Purchase Budget pages can now be drilled
down to show an overview of the budget entries created

Copy Budget Allows Append or Replace

Prior to this release, the Copy Budget action on the Retail Sales Budget (10012417) page
always added or appended the budget entries from the source to the destination budget.
In this release, a new Option field has been added to the Copy Budget action. With this
new field, customers can now add or replace the entries. When Replace entries is
selected, all entries in the destination budget will be deleted and replaced with the entries
copied from the source.
2017 10 6
Budget Consolidation with Master-Child Budgets
This new functionality lets customers work on multiple budgets (for example for different
Item Divisions) simultaneously and to consolidate those budgets into one corporate
budget.
A master-and-child relationship can now be defined for Retail Sales Budget and Retail
Purchase Budget. To achieve this, a Master Budget field, which lets customers specify if a
budget can be consolidated into a master budget, has been added to

Retail Sales Budget Name (99001555) table

Retail Sales Budget Card (10012418)
Retail Purchase Plan Name (10012400) table
Retail Purchase Budget Card (10012420).
A new Calculate Budget from Child Budgets action has also been introduced in the Retail
Sales Budget (10012417) page and the Retail Purchase Budget (10012419) page. This
action allows the master budget to pull and recalculate entries from the child budgets.

New fields, Consolidated from Budget Name, Consolidated Date, and Consolidated Time,
which store the details of the child budgets when entries are merged into master, have
been added to

Retail Sales Budget Entry (99001556) table

Cat./Prod. Gr. Budget Entries (99001666) page
Retail Purchase Plan Entry (10012401) table
Retail Purchase Plan Entries (10012408) page.

Budget Transformation/Breakdown
New functions are added in this release to transform budgets.
For more information see the Planned Sales Demand Worksheet Enhancements section in
these Release Notes.
Amount based line discount has been fixed, so changes in calculation sequence will not
affect the calculation. This fix requires adding a new field, Amount Based Discount, to the
POS discount table (POS Trans. Periodic Disc.). This new field affects three web requests:
GET_POSTRANS_SUSP
SEND_POSTRANS_BACKUP
SEND_POSTRANS_SUSP
2017 10 6
The setup of these request must be updated.

Fix for Manager Key and Permissions on Web POS: disabled buttons are now grayed out.
Employee images in Staff Management have been moved to the Tenant Media table. The
old BLOB Picture field has been removed.
Fix for images in Web POS (background images, store logos, and so on that were not
shown on Web POS).
2017 10 6
The Hierarchy system's user interface has been rewritten; pages have been combined for
improved overview.
There are now two types of Hierarchies in LS Nav:

Item/Deal: for a Hierarchy containing links to Items and Deals.

Store/Warehouse Loc./Customer: for a Hierarchy containing links to Stores, Store Groups,
Warehouse Locations, Customers, and Customer Groups.
Hierarchy Relations is a new concept in LS Nav which lets you relate Nodes in two different
Hierarchies of the same or different Hierarchy type. See the Hierarchy Relations for
Assortment Management section in these Release Notes for more details on Hierarchy
Relations.

The Hierarchy page has been changed. Links are now added at the bottom of the page
instead of being shown in a FactBox. By clicking the appropriate action, it is now possible
to add a Sibling or a Child directly to a selected node. Hierarchy information is now
displayed in a FactBox. Links can be copied from one node to another by right-clicking the
selected links. Multiple links can be added to nodes using the respective Add actions
where filters can be set.
2017 10 6
Item, deal, and store links to a Hierarchy can be managed directly from their list or card
pages.

The Use Distribution field has been removed from the Hierarchy table. Hierarchies of the
Item/Deal type can be filtered to a store and this can be done directly on the Hierarchy
Viewer page. Attributes can be managed directly on the Hierarchy Viewer page and saved
as default.

The web service GET_HIERARCHY_TREE was renamed to GET_HIERARCHY. Both

GET_HIERARCHY and GET_HIERARCHY_NODE now support deals/stores. A hierarchy is
now retrieved by its code and not by a Web Store number. The Hierarchy code for a web
store is kept in the WI Setup table with other web store information.

The term "tree" has been removed from the Hierarchy functionality. For nodes, the terms
Parent, Sibling, and Child are used.

For more details refer to the LS Nav Online Help, Hierarchies and Hierarchy Relations .
LS Hardware Station is now run as a service rather than a separate application.
Devices can now be ignored which prevents them from being loaded.
UI usability for Management Portal has been improved:
- Unused config fields have been removed.
- Labels for virtual devices and ignored devices have been added.
- Device tools have been made more user-friendly. 2017 10 6
- Drop-down added for device list.

It is now possible to create named relations for Items. Item Links is used to link an Item to
other Items/Deals.
To create Item Links, an Item Link Group is created first, and then Items/Deals are added
to the selected group. 2017 10 6

Purchase Orders (POs) can be now be created on the Retail Campaign card by clicking
Create Documents on the Actions menu and filling the Quantity field in the
Replenishment Lines FastTab. All POs that are created through Retail Campaign will
appear in the Documents FastTab. 2017 10 6

A test page can now be printed from the POS External Printers page.
A debug log in the POS External Printing setup can now be enabled to see what is
happening inside the Device Manager assembly used in the POS External Printing codeunit. 2017 10 6

The Mobile POS (WEB_POS request) now supports transaction balance rounding. Balance
rounding is a combination of sales and payment rounding (when tender rounding is used
and there is a difference between sale and payment, the result is transaction balance
rounding).
 
The Mobile POS now allows a transaction to be posted as long as the balance difference is 2017 10 6
within the limit set by the Allowed Diff. in Trans field on the Store card. This field
represents the sum of all tender rounding allowed for a given transaction.
The Status Code on the Item Status Link Worksheet is now in sync with the Item/Item
Status Links page for items with variants.
The Item Status module can now be used more effectively by using the worksheet for
variants and there use the Items Status blocks. 2017 10 6

A number of issues, reported by an LS Retail partner, have been fixed in the following
modules: 
Retail Receiving, SPO, POS, POS Data Entry, POS Print, POS Terminal, Inventory
Worksheet, Replenishment, Statement, Tender Declaration, Retail Calendar, WS Service, 2017 10 6
and Sales.

Negative adjustments and physical inventory postings on the Hospitality POS are no longer
sent to the KDS. 2017 10 7
New Planned Demand Types
In this release, new calculation types for Planned Sales Demand have been added.
Previously, a forecast quantity could only be substituted with a planned substitute
quantity. In this release new types have been added to increase the forecast quantity with
absolute numbers or % factors. This makes it very easy to cover complex demand changes
(overlapping effects) or demand changes for heterogeneous destinations (varying store
sizes, regional aspects).
New fields, Line No., Planned Demand Type, Planned Demand Event, and Status, have
been added to the Replen. Planned Sales Demand (10012374) table and Replen. Planned
Sales Demand (10012322) page.

The Planned Demand (Qty.) field has been renamed to Planned Demand.

Three types of Planned Demand Type can now be selected from the Replen. Planned Sales
Demand page:
2017 10 7
Substitute Quantity - the input Planned Demand will be used to substitute the average
daily sales of the affected item.
Additional Quantity (to Forecast) - the input Planned Demand will be added on top of the
average daily sales of the affected item.
Additional % Factor (to Forecast) - the input Planned Demand will be treated as a % factor
which added on top of the average daily sales of the affected item.
Planned Sales Demand Events
Above all, Planned Sales Demand lines can now be linked to a Planned Sales Demand Event
and directly maintained from the Event page. Prior to this release, Planned Sales Demand
could only be maintained manually in the Retail Item Card. This is inconvenient, especially
when a large number of items are involved. As a solution to this, a new Replen. Planned
Events (10012326) page has been introduced to allow maintenance of Planned Sales
Demand in one place. The page can be found in LS Retail - Replenishment - Automatic -
Replenishment Planned Events.
Simple Maintenance of Planned Sales Demand
Planned Sales Demand is easily maintained by using the Add Lines and Remove Lines
actions in the page for Planned Sales Demand Events. Those actions let the user add (or
remove) Planned Sales Demand lines by using reports with a big variety of filters.
Linking Planned Sales Demand to Discounts and Budgets
Planned Sales Demand is a component of Automatic Replenishment and influences the
proposals for Purchase Orders and Transfer Orders. Linking the Planned Sales Demand to
Budgets and Discounts lets the user plan promotions or seasonal sales which are picked up
and considered by Replenishment.
An event can be linked to Periodic Discount or Retail Sales Budget and a Planned Sales 2017 10 7
Demand can then be created directly from the Periodic Discount or Retail Sales Budget by
using the Update Lines action. Currently, Discount Offers and Multibuy Discounts are
supported, and the Retail Sales Budget must have Budget Type Item, Period Type Day, and
budget entries with Store No.
In order to allow Periodic Discount to be used for Planned Sales Demand creation, a new
Replenishment FastTab consisting of the new fields Planned Demand Type, Planned
Demand, and Consider Calendar has been added to the Discount Offer (99001594) and
Multibuy Discount (99001599) pages. Two new fields, Planned Demand Type and Planned
Demand, have also been added to the Lines FastTab in these pages. Planned Sales Demand
are created according to the Validation Period ID and Price Group assigned to the discount.
Retail Calendar or Base Calendar can also be taken into consideration, where non-working
days will be excluded from the Planned Sales Demand creation. This can be setup with the
Consider Calendar field on the Replenishment FastTab.

In order to allow Retail Sales Budget to be used for Planned Sales Demand creation, a 2017 10 7
Replenishment FastTab, consisting of the new fields Planned Demand Type, Consider
Calendar, and Allocation Rule Code, has been added to the Retail Sales Budget Card
(10012418).
Transformation of Budgets
In order to allow Retail Sales Budget to be used for Planned Sales Demand creation, the
budget has to be on Day, Item and Store level. Three new actions Breakdown to Days,
Breakdown to Items, and Breakdown to Stores have been added to the Retail Sales Budget
(10012417) page so that all types of budgets can be converted to the required format for a
Planned Sales Demand creation.
The Breakdown to Days action will break down budgets that are not in the Period Type Day
(that is Year, Quarter, Month, or Week) to Day. Similar to Periodic Discount, the action can
also take into consideration the Retail Calendar or Base Calendar when performing the
breakdown, where non-working days will be excluded from entries creation. The quantity
in the initial budget entry will be evenly distributed to the new entries.

The Breakdown to Items action will break down budgets that are not in Budget Type Item
(that is Division, Item Category, or Product Group) to Item. Only items that are not blocked 2017 10 7
from purchasing or transferring will be considered. Similar to Breakdown to Days, the
quantity in the initial budget entry will be evenly distributed to the new entries.

A budget entry must have a Store No. in order for it to be usable for Planned Sales
Demand creation. The Breakdown to Stores serves the purpose to breaking down budget
entries without a Store No., according to the Allocation Rule Code setup on the
Replenishment FastTab. The quantity in the initial budget entry will be distributed to the 2017 10 7
new entries based on the weights and share percentage as per setup for each store in the
Allocation Rule.
Enhanced Maintenance of Budgets
A Store No. filter has been introduced in the Edit Retail Sales Budget (10012416) and Edit
Retail Purchase Budget (10012415) pages. This allows easy maintenance of budget entries
for individual stores in Retail Sales Budget and Retail Purchase Budget.
The Store No. filter is defaulted with the Store No. from the Retail Sales Budget or Retail
Purchase Budget page but it can always be changed to another value. The budget lines are
calculated according to the selected store in the filter. If no Store No. filter is selected then
budget lines will be recalculated to show the consolidation of all entries.

Also, the fields in the Edit Retail Sales Budget and Edit Retail Purchase Budget pages can
now be drilled down to show an overview of the budget entries created.

Copy Budget Allows Append or Replace

Prior to this release, the Copy Budget action in the Retail Sales Budget (10012417) page
will always add or append the budget entries from the source to the destination budget.
In this release, however, a new Option field has been added to the Copy Budget action. 2017 10 7
With this new field, customers are allowed to add or replace the entries. When Replace
entries is selected, all the entries in the destination budget will be deleted and replaced
with the ones copied from the source.
Budget Consolidation with Master-Child Budgets
This new functionality lets users work on multiple Budgets (for example for different Item
Divisions) in parallel and to consolidate those Budgets into one corporate Budget.
A master and child relationship can now be defined for Retail Sales Budget and Retail
Purchase Budget. To achieve this, a Master Budget field has been added to the Retail Sales
Budget Name (99001555) table, Retail Sales Budget Card (10012418), Retail Purchase Plan
Name (10012400) table, and Retail Purchase Budget Card (10012420). This field lets users
specify if a budget can be consolidated into master budget.

A new Calculate Budget from Child Budgets action has also been introduced in the Retail
Sales Budget (10012417) page and the Retail Purchase Budget (10012419) page. This
action allows the master budget to pull and recalculate entries from the child budgets.
New fields, Consolidated from Budget Name, Consolidated Date, and Consolidated Time,
have been added to the Retail Sales Budget Entry (99001556) table, Cat./Prod. Gr. Budget
Entries (99001666) page, Retail Purchase Plan Entry (10012401) table, and the Retail
Purchase Plan Entries (10012408) page, to store the details of the child budgets when
entries are merged into master. 2017 10 7

Budget Transformation/Breakdown
New functions have been added in this release to transform budgets. Click here for more
detailed information.
Retail Budgets Menu Improvements
The user navigation experience in the Retail Sales Budget page has been improved: New
actions, New, Edit, and Delete, have been introduce on the Retail Sales Budget List for
more user-friendly way of maintaining the Retail Sales Budget Name with the NAV
standard.
Self-explanatory buttons, Sales Budget and Purchase Budget, in the Retail Sales Budget and 2017 10 7
Retail Purchase Budget pages respectively, have been added for opening the budget for
maintenance.
Minor naming fixes have been implemented in Retail Budget.

The Copy Budget function, in the Retail Purchase Budget page, has been improved.
Options have been added to add or replace entries in the destination budget. 2017 10 7

A new action, Check And Correct, has been added to the Retail Sales Budget page.
Users can use this action to consolidate or delete budget entries that have the value
Opening Stock Value outside the budget start date. Also used to correct budget entries
that are outside the budget's period. 2017 10 7

A validation has been added to the Check Rule action in the Allocation Rule page, where a
warning will be displayed if the same Destination Group is found to be used in more than 2017 10 7
one Allocation Rule Line.

A new functionality has been added to the Hierarchy system that allows the user to add
Items, Deals, Stores, Warehouses, and Customers to Hierarchy nodes. 2017 10 7

A potential rounding difference has been fixed between a transaction line discount amount
and a discount amount in underlying transaction discount lines. 2017 10 7

Incorrect sync time has been fixed in search index where the time zone is other than UTC.
2017 10 7
The Hardware Station Management Portal is now hosted (default is http://localhost:8088),
rather than using a shortcut to a static file. This also enables the use of https. 2017 10 7
It is now possible to run LS Hardware Station as a services and as a console application.
This feature was added to accommodate internal developer needs. 2017 10 7
A new Event Type no. 28 (BROWSERNAVIGATED) has been added to the POS Events: when
a link is pressed in the BrowserControl and new document is loaded, this new event
occurs.
It is also now possible to invoke POS commands from the user's own HTML in a 2017 10 7
BrowserControl by using the LSUtils.SendPosCommand function.

A maximum string length has been set for inputs on the POS. This prevents users from
entering texts that exceed the length of what Dynamics NAV can save to tables. 2017 10 7

A warning is now issued if a POS user is logging on to a POS terminal that is already open in
another session. 2017 10 7

Tools have been added to restart Hardware Station service and to reset configurations.
2017 10 7
The 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.
  2017 10 8
A new POS Command, AVAILABILITY_MODE, is used to set current availability on the POS
buttons. The current availability feature is not supported with the Mobile POS in this
version. It will be supported with the Mobile POS in future versions.
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. 2017 10 8
Otherwise, the items are not compressed even if they have the same default menu type.
This allows changing the menu type afterwards.

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: 2017 10 8

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 2017 10 8
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: 2017 10 8
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: 2017 10 8
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:
Control added to enable/disable the fields Division Code, Item Category, and Product
Group, based on the selected Copy-from Budget Type.The field Budget Type has been
added below the Budget Name field, which is updated when the user selects a destination
budget.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.A message is displayed at the end of the copy action if 2017 10 8
entries with an earlier start date compared to the destination's Budget Start Date are
found.
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 2017 10 8
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.

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 2017 10 8
Variant Values records will only be inserted when the actual variants are created.

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). 2017 10 8
 
For an example of how the GS1 DataBar barcodes can be used, see the LS Nav Online
Help.
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/she would like to
buy the item even if the item's expiration date is coming soon (or has passed). 2017 10 8
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.

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 2017 10 8
current date and time.

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.
2017 10 8
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.

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

POS event MARKEDCOUNTCHANGED now contains information on the active Column and

Row in the Source (Data Grid Control). 2017 10 8
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 2017 10 8
BrowserControl using HTML/CSS/JS, and interact with it.

POS Hardware Profile now provides support for multiple OPOS Scanners.
2017 10 8
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.
2017 10 8

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 2017 10 8
opening the POS in this situation.

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 2017 10 8
web service.

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 2017 10 8
then frees up time for the client session running the POS.

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. 2017 10 8

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). 2017 10 8
It is now possible to have multiple pages in Web POS menus. 2017 10 8
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 2017 10 8
transformed to Item Category AUDIO when it is consolidated into a master budget with
Item Category type.

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 2017 10 8
current and previous year.

The Fashion Role Center is reintroduced in this release. The aim of the role center is to
create an easy-to-use environment for fashion store managers, and to make all the most
commonly used functions and basic statistics immediately available to them.
The role center provides easy access to POS Statements, Transaction Register, Purchase
Orders, and Return Orders in tiles format. It also presents the store managers with a
number of useful Value Charts, such as the PO Sales and Store Hourly Sales chart. The role
center is also equipped with an action menu and a navigation pane which provide
convenient access to various functionalities, such as the Retail Item Registration, Lifecycle
2017 10 9
Planning Worksheet, and more.

For more information see Fashion Role Center in the LS Nav Online Help.

When an invalid barcode, or a barcode that is not in the system, is scanned, the operator is
notified with a pop-up message and he/she must press OK to continue. 2017 10 9

Performance boost implemented for serial and lot numbers in local inventory Lookup.
2017 10 9
It is not possible to do an End-of-Day Tender Declaration on a POS, if the POS is in Training
Mode and the Safe Mgnt. in Use check box is selected for the Store. 2017 10 9
Amount Rounding Precision for foreign currency in the POS has been fixed.
2017 10 9

Support for multiple OPOS scanners has been added in the POS Hardware Profile.
2017 10 9
A new option has been added for drawers in the Hardware Profile. It is now possible to
select a Drawer Alert Type Block to block all actions on the POS while the drawer is open. 2017 10 9

The below features have been introduced to allow customers to conveniently add lines to
Allocation Rule with Stores, Store Groups, Warehouse Locations, Customers, and Customer
Groups as setup in a Store Hierarchy. 2017 10 9

A new action, Add Stores from Store Hierarchy, has been introduced in the Allocation Rule
page (10012254). The action opens up a report which lets customers add Stores, Store
Groups, Warehouse Locations, Customers, and Customer Groups as defined in the Store
Hierarchy's node links to the Allocation Rule Lines. From the report's request page,
customers can choose from Share Type Default Weight or Manual Weight, and define the
weight to be assigned to each line.
To support the feature, a new Action Message field has also been added to the Allocation
Rule Line table (10012329) and Allocation Rule Lines page (10012255). Allocation Rule
Lines added from Store Hierarchy will be marked as New in the Action Message field. This
is to assist the customers to easily identify lines that are added from Store Hierarchy and 2017 10 9
they are still allowed to update the weight. The customers must use the Clear Actions
action to clear the Action Message once they're satisfied with the changes.
The Check Rule action in the Allocation Rule page has been extended with the below
validations:
If there are Allocation Rule Lines marked as New in the Action Message field.
If the total weight of all Allocation Rule Lines is equal to zero. 2017 10 9
For more information see How to: Add Stores to Allocation Rule from Store Hierarchy in
the LS Nav Online Help.

A new Budget Type field has been introduced in the Copy Retail Purchase Budget
(10012408) report, accessible from the Copy Budget action on the Retail Purchase Budget
(10012419) page.
This field is updated with the Budget Type of the selected destination budget. The Division
Code, Item Category, and Product Group fields on the report will now be enabled or
disabled according to the Budget Type of the source budget. For example, if the source
budget has the type Product Group, only the Product Group field will be enabled on the
report. If a value is selected for one of these fields, the Division Code, Item Category, and
Product Group fields of the copied entries will be replaced according to the selected value
and the hierarchy setup in the Product Group, Item Category, and Division tables. Also, a
warning message will be displayed to the customer, if the copied entries have an earlier 2017 10 9
start date than the destination's Budget Start Date.

For more information see How to: Copy a New Purchase Budget in the LS Nav Online Help.

In a Hierarchy Relation with active relations on multiple node levels, the Remove Relation
(preserve child relations) action for a node on a middle level resulted in an incorrect value
in the Relation Type and Inherited from Node1 fields. These fields were not inherited
correctly from the parent nodes. 2017 10 9
This has been corrected in the current release.

The Season Filter in the Replen. Template for the Purchase Replenishment Journal and the
Transfer Replenishment Journal has been improved. It now supports special characters,
such as "<>" and "|", to let customers perform advanced filtering. 2017 10 9
Control functions for context menus have been implemented. It is now possible to view
and/or modify control and panel properties, move controls around, copy, paste, and add
new controls. It is also possible to copy and paste buttons and button properties, and so 2017 10 9
on.

Watermark function has been implemented for Web POS. A watermark can, for example,
be used to indicate if the POS is in Design Mode or Training Mode. 2017 10 9
One part of the LS Nav 10.09 release is LS Recommend version 2.0. This version of LS
Recommend supports LS Omni version 2.4 and ongoing.
In the new LS Recommend version the model procedure in Back Office LS Nav has been
simplified and made easier for the user. The biggest simplification is in procedures to
include features in the model, which are necessary to make cold item recommendation. 2017 10 9
Display options on the POS and in Omni are the same as in previous version.

A new feature, Dining Table Allocation, has been added in LS Hospitality. Add walk-in
guests quickly to a waiting list with the relevant information, and allocate them to tables in
the Dining Allocation Panel. Waiting times can be estimated by viewing the statistics for
the dining area, and the user has a good overview of when tables will be ready. Guests can
be seated quickly when a table becomes available, and it is now easy to search for tables 2017 10 9
and for guests occupying tables or waiting lists.
The Dining Table Pop-up Menus in Demo Data Notes
#HOSP-POP-ADJUST Changed Default Skin and Font = #HO-POP-LINES
First line has #HO-POP-HEADER font and skin.
#HOSP-POP-CLEAN Changed Default Skin and Font = #HO-POP-LINES
First line has #HO-POP-HEADER font and skin.
#HOSP-POP-CLEAN-OS New New menu to accommodate the new option for Table
Becomes Occupied - On Ordering or Seating (Service Flow).
Includes both Seat Guests and Open POS commands.
#HOSP-POP-CLEAN-S Changed Default Skin and Font = #HO-POP-LINES
First line has #HO-POP-HEADER font and skin.
#HOSP-POP-FREE Changed Default Skin and Font = #HO-POP-LINES
First line has #HO-POP-HEADER font and skin.
#HOSP-POP-FREE-OS New New menu to accommodate the new option for Table Becomes
Occupied - On Ordering or Seating (Service Flow).
Includes both Seat Guests and Open POS commands.
#HOSP-POP-FREE-S Changed Default Skin and Font = #HO-POP-LINES
First line has #HO-POP-HEADER font and skin.
#HOSP-POP-LOCKED Changed Default Skin and Font = #HO-POP-LINES
First line has #HO-POP-HEADER font and skin. 2017 10 9
Second line has #HO-POP-SUB-HEADER font and skin.
#HOSP-POP-OCCP New Replaces the four menus #HOSP-POP-OCCUPIED, #HOSP-POP-
OCCUPIED-C, #HOSP-POP-OCC-OTHER, and #HOSP-POP-OCC-OTHERC
#HOSP-POP-OCCP-PAID New Replaces #HOSP-POP-OCCUP-PAID
#HOSP-POP-OCCP-CLEAR New Replaces #HOSP-POP-OCC-CLEAR
#HOSP-POP-SEATED-C New Replaces #HOSP-POP-SEATED
#HOSP-POP-TRANSFER Changed Default Skin and Font = #HO-POP-LINES
First line has #HO-POP-HEADER font and skin.
If you are upgrading your system to LS Nav 10.9 you must import certain data from the
demo data (use the Import Export Worksheet):

1. Import the ##DEFAULT POS Menu Profile, ##DEFAULT POS Interface Profile and
##DEFAULT POS Style Profile -without overwriting. The new menus, panels, and controls
will be imported.
2. Import the POS commands - also without overwriting. The new commands will be
imported.
3. Import the POS Data Tables - also without overwriting. The new data tables will be
imported.
4. Import the POS Tags - also without overwriting. The new POS tags will be imported.
5. Change the Hospitality Service Flows so that they point to the appropriate dining table
pop-up menus (see the demo data Hospitality Service Flows). You can switch between the
Table Becomes Occupied and Table Status after Clearing options (end with the correct one)
to let the system put in some of the new menus for you. You need to change the Occupied
and Occupied-Paid and Clear menus manually. 2017 10 9
6. Change the skin and font of those dining table pop-up menus that are changed and not
new according to the list above.
7. If you have created your own style profiles, you will have to create the #HO-POP-LINES,
#HO-POP-HEADER, and #HO-POP-SUB-HEADER fonts and skin for each style profile you
have created.

Hospitality has the following known issues with LS Nav 10.09.

1. If Current Availability is set for the restaurant and the POS is in Dining Table Layout and
idle for 20 seconds, an error will pop up.
2. If there is no Service Flow for a Hospitality Type, then an error pops up. 2017 10 9
This can be mitigated by adding an empty service flow to the hospitality type.
There is now full support for Omni/ECom by running the jobs OMNI_INIT. Updates can
then be run by the scheduler job OMNI_UPDATE.
The Omni Server works with prior versions of LS Nav. Earlier versions of the Omni Server
will work with this new LS Nav version, but cannot use new features related to Customer 2017 10 9
Orders.

Events and publishers have been added in a POS Transaction where POS Actions were
called before. 2017 10 9
SQL Indexes for non-mainstream or unused keys are no longer maintained. This can be
turned on again for individual customers, if needed. 2017 10 9
The LS Nav Online Help home page has been rearranged for improved navigation. The
available search options are expanded, and links have been added to a printable PDF
version of the Release Notes and to an Excel document with an overview of new events. 2017 10 9

New events have been added to Hierarchies. 2017 10 10

First Integration Events to POS Controller codeunits.
2017 10 10
New Budget Type Introduced in Retail Sales Budget: Item Hierarchy
Item Hierarchy can now be selected as a Budget Type in Retail Sales Budget. When this
type is selected, the user can assign an Item Hierarchy to the budget, and then perform
planning for the items that are linked to the Hierarchy. The Hierarchy can be assigned with
the new Hierarchy Code field introduced in the Retail Sales Budget page, and budget
entries can then be created and maintained at item level. 2017 10 10
Note: The Item Hierarchy must be set to Link Only Once for it to work with Retail Sales
Budget.
Retail Sales Budget Functionality Improvements for Item Hierarchy Budget Type
The various functionalities on the Retail Sales Budget page, such as Calculate Budget from
Child Budgets and Copy Budget, can now be used on an Item Hierarchy budget on the
condition that the budgets involved are linked to the same Item Hierarchy. The Create
Budget from Sales report has also been improved to work with the new Item Hierarchy
budget type. The report will only create budget entries based on the historical sales data
for items that belong to the Item Hierarchy currently assigned to the budget. Also, View
Start Date has been added to the Retail Sales Budget page to let the user refresh the page
with a specific start date. 2017 10 10

For more information see Retail Sales Budgets in the LS Nav Online Help.

Store Capacity Page Improvements

These fields have been added to the Store Capacity table (10012320) and page (10012330)
to show the actual capacity utilization of the stores:

Inventory
Actual Capacity
Capacity %
Last Time Calculated
The calculation of the above fields can be performed manually with the Calculate Capacity
action on the Store Capacity page, or automatically using the Scheduler Job with Job ID
REPLEN-STORECAPACITY. The page has also been enhanced to allow any combination of
Location Code, Item Category Code, Product Group Code, and Season to be added.
Furthermore, the page can now be accessed from the MenuSuite LS Retail - Replenishment
- General - Lists, Store Capacity, as well as from the Retail Item Category, Retail Product
Group, and Seasons page.
Store Capacity Report Improvements
The Store Capacity Report can now be accessed from the MenuSuite LS Retail -
Replenishment - General - Reports and Analysis, Store Capacity. The report has been
enhanced to display the store capacity utilization information, such as Actual Capacity and
Capacity % based on the Goal Capacity setup and Inventory for each Item Category or
Product Group. Users also have the option to generate the report with item details, if they
enable the Show Items field on the report's request page. 2017 10 10
For more information see Store Capacity in the LS Nav Online Help.

Stock Coverage Page Improvements

These fields have been added to the Stock Coverage table (10012321) and page
(10012331) to show the actual weekly stock coverage:

Weekly Sales Qty.

Actual (weeks)
Coverage %
Last Time Calculated
The Goal field has been renamed to Goal (weeks). The calculation of the fields can be
performed manually with the Calculate Coverage action on the Stock Coverage page, or
automatically using the Scheduler Job with Job ID REPLEN-STOCKCOVERAGE. The Location
Code and Item Category Code fields on the page are now mandatory, and the Stock 2017 10 10
Coverage can be set up per item category or product group, as well as for a specific
season. Furthermore, the Stock Coverage page can now be accessed from the MenuSuite
LS Retail - Replenishment - General - Lists, Stock Coverage, as well as from the Retail Item
Category, Retail Product Group, and Seasons page.

New Field in Replenishment Setup: Number of Sales Days to Analyze

A new Stock Coverage FastTab and a new Number of Sales Days to Analyze field has been
added to the Replen. Setup table (10012200) and page (10012200). This field defines the
number of sales days to go back in history to be considered for the Weekly Sales Qty. 2017 10 10
calculation in Stock Coverage page and report.
Stock Coverage Report Improvements
The Stock Coverage Report can now be accessed from the MenuSuite LS Retail -
Replenishment - General - Reports and Analysis, Stock Coverage. The report has been
enhanced to calculate its Weekly Sales Qty. based on the new Number of Sales Days to
Analyze field introduced in Replenishment Setup, if there is no From Date and To Date
selected in the report's request page. Moreover, when the report is generated, only lines
with matching Stock Coverage setup (that is, with matching Item Category or Product
Group, and Location Code) found will be displayed, and the Total lines when the report is
being displayed by Product Group or Item have been removed. 2017 10 10

For more information see Stock Coverage in the LS Nav Online Help.

Store Group Setup Improvement

A new action, Store Setup, has been introduced to the Store Groups (10001397) page to
improve the user experience when maintaining Store Groups and related Stores. 2017 10 10

Purchase Replenishment Journal and Transfer Replenishment Journal Improvement

Three new actions have been added into the Purchase Replenishment Journal (10012205)
and the Transfer Replenishment Journal (10012215),

Replen. Item Quantities, has been introduced to the pages Purchase Replenishment
Journal (10012205) and Transfer Replenishment Journal (10012215). This action opens the
Replen. Item Quantities (10012218) page for the selected item. Furthermore, the actions
on the Navigate menu have been rearranged.
New actions, Delete all lines and Delete zero lines, have been introduced to the pages
Purchase Replenishment Journal (10012205), Transfer Replenishment Journal (10012215) 2017 10 10
and Replen. Template List (10012202). These actions let the user quickly delete Journal
Lines after the Replenishment calculation.

The Virtual Scale can now be configured to return lb, oz or g in addition to kg. 2017 10 10
InStore Management worksheets have been revised and replaced with Store Inventory
worksheets. InStore worksheets are based on standard NAV objects and many
unnecessary validations are run for each journal line that is entered. Sometimes, in large
installations, this results in waiting in deadlocks. Now, however, LS Nav has Store Inventory
Worksheets based in LS Nav's own object range where we have full control. Hopefully, this
will make the system easier, faster, and simpler to use.

The new worksheets are used for inventory adjustments such as positive and negative
adjustments, transfers, and exploding prepacks. There are also worksheets for counting, 2017 10 10
purchasing (+returns), label printing, stock requests, and price checking. Text files, for
example from handheld devices, can be imported to any worksheet type.

LS Nav now offers Cycle count (Periodic count), a new type of counting. Cycle counts are
normally done on a small section of the inventory, usually on a particular brand, type, or
supplier's items and can be done during regular opening hours. It is possible to run
multiple cycle counts at the same time (just make sure you do not have the same item in
more than one count). The frequency of counting is set on an Item, Product Group, or Item
category by selecting a Physical Inventory Counting Period.

In this version you can select if you want to keep on working in InStore Management or 2017 10 10
switch to Store Inventory, see the Store Inventory Setup page. The Mobile Inventory
application for handhelds works with both versions.

The WebPOS Add-in now verifies that the JavaScript Add-in is the same version as the
Server Side objects/toolbox. This prevents users from using updated Toolbox components 2017 10 10
without updating the JavaScript Add-In.

A new drop-down menu, Printing, has been added to the Hospitality Items List and Card
pages. The new option is available on the Navigate menu.

A new action, Extra Print Setup, has also been added to the Recipe List and Recipe Card 2017 10 10
pages.
Clicking the Calc Standard Cost action on the Recipe Card now prompts the question: "Do
you want to update recipe cost with unit cost from items".

A new action, Adjust Cost - Update Recipes, lets the user update all recipes for all or 2017 10 10
selected items with the new cost that is calculated from the Item Entries.

A new check box, Retail Message in use, has been added to Retail Message Setup. If the
check box is not selected, the Web Service is not called. 2017 10 10
It is no longer necessary to have a Service Flow for Hospitality Type.
2017 10 10
An error message was sometimes generated, if the Current Availability function was used
while the POS was idle in the Dining Table Area panel. This has now been fixed. 2017 10 10

The online help for Dining Table Allocation has been improved. 2017 10 10
LS Nav 2018 (11.0) supports upgrade from version LS Nav 2017 (10.x). For this upgrade
there is no specific LS Nav upgrade toolkit, the standard upgrade works here.
Upgrades from LS Nav 2015 (8.0) and LS Nav 2016 (9.0) to LS Nav 2018 (11.0) will be
available in later releases.
Note: The Standard Dynamics NAV upgrade toolkit from version 2015 and 2016 does not 2018 11 0
work for LS Nav 2018 (11.0).

Mobile tables for Mobile POS and Omni that are no longer in use have been removed.
2018 11 0
Action Management is now handled using events. So-called “Preactions” are created by
subscription events that utilize “Database Table Trigger” events. These events are 2018 11 0
published by the “Application Management” codeunit.

The value of the Check frequency (minutes) field on the Retail Message Setup page is now
set to zero when the Retail Message in use check box is selected. 2018 11 0
The Click and Collect process has been modified to ship orders. Instead of items being
stored and collected at the store, a transaction is created and posted immediately to ship 2018 11 0
items directly to the customer.
The Retail ICT module is now limited to only supporting journal mirroring. Handling of ICT
transfer and document handling has been removed, but the module is still able to mirror 2018 11 0
journal (G/L and ILE) posting between databases.

Standalone Store has been removed from the system. This is to support handling of
documents (PO, TO, SO) between databases and companies. 2018 11 0
Multiple Web Stores are now supported in a single company. A Web Store number is
required when a basket is calculated and web orders are created.
WI Setup and WI Stores have been moved to the Store table.
Jobs to prepare data for eCommerce have been reduced to two jobs: OMNI_INIT and 2018 11 0
OMNI_UPDATE. Older jobs, processes, and objects that are not used any more have been
removed from the system.

A new self-service POS, the Coffee POS, has been added to the Demo Data Company. This
self-service POS has the Profile #COFFEE-Q and is set up on terminal P0068 for Restaurant 2018 11 0
S0010 and on terminal P0071 for store S0001.

Clienteling is a new extension to LS Nav POS which adds a new "customer-in-store"

experience to the POS. Using the Clienteling view, store staff can now engage with the
customer and navigate items in a way similar to what the customer is accustomed to in
web-stores.
In this first version, which is currently only available for the Windows POS, the framework
and basic functionality for Clienteling has been implemented. Later, Clienteling will also be
available for the Web POS.
A new POS setup has been added to the Demo Data company to demonstrate Clienteling 2018 11 0
with profiles #TAURUS. In the Demo Data company terminal number P0069 has been set
up with these profiles.
For more information see Clienteling in the LS Nav Online Help for more details.
The following POS commands have been removed in this release:
ADDCHARGE
ORDERMGT
ORDPMTHIST
CUSTOMERSPO
MARKSPO
GIFT_MARK_LINE
POPUPSPODETAILS
SPODETAILS
SPOCANELLINE 2018 11 0
SPOFINALIZE
SPOPARTFINALIZE
The list of POS commands in the POS online help and in the corresponding Excel document
have been updated.

In order to improve performance local inventory lookup for serial and lot numbers has
been changed. 2018 11 0
Page 99009132, Allocation Plan Doc. Factbox, did not show the Captions Purchase Orders,
Transfer Orders, and Sales Orders correctly. This has now been fixed. 2018 11 0

When the Purchase Replenishment Journal or the Transfer Replenishment Journal is

calculated with the Add Items to Journal report, the filters for Vendor No., Replenishment
Calculation Type, ABC Amount, ABC Profit, Special Group Code, Item Hierarchy, and Item
Attribute will now also work for Replenishment Item Quantity (RIQ) calculation.
In other words, when the Calculate Inventory option is selected in the Add Items to Journal
report, these filters will also work for RIQ calculation where only items which fulfill the 2018 11 0
filter will be considered.
Transfer & Purchase Thresholds are a new feature to reduce transportation cost. It is a tool
designed to avoid small Purchase Orders or Transfer Orders by setting Threshold limits. If
they do not meet the Threshold limits, Purchase Order and Transfer Order proposals in the
Replenishment Journal will be marked with a warning.
Actual Values in the Replenishment Journal
Thresholds Management calculates and displays the Actual Values for:
Quantity
Cost Amount
Sales Amount 2018 11 0
Profit Amount
Weight
Cubage

in the Replenishment Journal Details and totals the values to Replenishment Journal Lines
and the whole Replenishment Journal. An Information FastTab has been introduced in the
Purchase Replenishment Journal (10012205) and the Transfer Replenishment Journal
(10012215) to show these total values. The total fields are also introduced in the Replen.
Template List (10012202) where they will show the total values of all journals under the
Replenishment Template. The calculation of the Actual Values is triggered when:
The journal is calculated using the Add Items to Journal report.
The journal is calculated with the scheduler job.
A Replenishment Journal Line or Detail Line is added, changed, or deleted.
The Quantity or Unit of Measure fields are changed in the Replenishment Journal Line or
Detail Line.
Threshold Fields Visibility Setup
It is possible to set up the visibility of the Actual Value fields. A new Replen. Journals
FastTab has been introduced in Replenishment Setup with these check boxes:
Show Cost Fields in Purch. Replen. Journal
Show Sales Fields in Purch. Replen. Journal
Show Profit Fields in Purch. Replen. Journal
Show Cost Fields in Transf. Replen. Journal
Show Sales Fields in Transf. Replen. Journal
Show Profit Fields in Transf. Replen. Journal
The check boxes are used to define which of the Actual Value fields should be displayed in
the Journal. These visibility settings will be copied to any newly created Replenishment
Template. Existing Replenishment Templates will not be updated when these check boxes
are changed. It is also possible to setup the Actual Value fields visibility per Journal or
Template. This can be done on the Replen. Template (10012201) page, with the Show Cost
Fields in Journal, Show Sales Fields in Journal, and Show Profit Fields in Journal check boxes
on the Visible Fields FastTab.
Threshold Rules Setup
A new Threshold Rule (10012310) table and Threshold Rules (10012333) page have been
introduced where the upper or lower limit of Threshold Fields can be defined. The upper
and lower limit can be set up with the Minimum Value and Maximum Value fields, and the
options available for the Threshold Fields to be compared against the limits are:
Quantity
Cost Amount
Sales Amount
Profit Amount
Weight
Cubage
The Threshold Rules can be defined per Vendor, Store/Location, and Item hierarchy
(Division, Item Category, Product Group, and Item). Three types of Rules can be set up:
Purchase to Warehouse - works with the Purchase Replenishment Journal with Purchase
Order Type One Purchase Order per Vendor or One Purchase Order per Vendor with Cross
Docking.
Purchase to Receiving Location - works with the Purchase Replenishment Journal with
Purchase Order Type Purchase Orders for Receiving Locations.
Transfer - works with the Transfer Replenishment Journal.
The Threshold Rules page is accessible from LS Retail - Replenishment - Automatic -
Administration - Threshold Rules, as well as from the Location and Retail Vendor pages.
Threshold Rule Values Calculation
When a journal is calculated, the Thresholds Management will go through all Threshold
Rules and copy applicable rules to the Threshold Rule Value (10012311) table, which is an
individual Rule definition for a specific Replenishment Journal. Next, the Thresholds will be
calculated for the applicable Rules and the results will be shown in the Actual Value field
on the Threshold Rule Values (10012334) page, as well as reflecting the Status of the value
if it has violated the Threshold (Below Minimum or Above Maximum). The No. of
Exceptions field on the Information FastTab in the Purchase or Transfer Replenishment
Journal can be used to check if an Exception is raised.
To support the feature, a new Exception Management FastTab has been introduced in 2018 11 0
Replenishment Setup. This new FastTab has a check box, Thresholds for Autom. Replen.,
and the Threshold Rule Values calculation will only be performed, if this box is selected.

Block Documents Creation When Threshold Exceptions Raised

A check box, Thresholds Block Doc. Creation, has been introduced on the Exception
Management FastTab in Replenishment Setup. If this box is selected, the creation of
Purchase Order and Transfer Order from Replenishment Journals with unresolved
Exceptions will be blocked. This applies to the scheduler-based document creation and the
Create Purchase Orders, Put Creation of Purchase Orders on Batch Posting Queue, Create
Transfer Orders, and Put Creation of Transfer Orders on Batch Posting Queue actions on
the Journal pages.
Resolving Threshold Exceptions
The No. of Exceptions field in the Replenishment Journal indicates existing unresolved
Exceptions. The Threshold Rule Values page can be opened by drilling down the No. of
Exceptions field, or by clicking the Show Thresholds action. On the Threshold Rule Values
page, users have a choice of:
Accepting the Exceptions without adjusting the quantities.
Adjusting the quantities in the journal to increase or decrease the Actual Value until it
meets the Thresholds.
The Exceptions can be accepted manually by changing the Rule Action field to Accepted, or
by clicking the Accept all Threshold Exceptions action to accept all Exceptions in one step.
Alternatively, the Threshold Exceptions Details page can be opened with the Show Details
action, where it will show all Replenishment Journal Detail Lines causing the Exception.
Quantities can be adjusted from the page and the Recalculate Actual Values action on the
Threshold Rule Values page can then be used to recalculate the Actual Values and to check
if the Exceptions have been resolved.
For more information see Transfer and Purchase Thresholds in the LS Nav Online Help.

Special Order (SPO) has been removed from LS Nav 2018. Special Order will be replaced by
a new functionality, Customer Order. 2018 11 0
Multiple Web POSes can now be used with a single LS Hardware Station for printing. For
more information about the LS Hardware Station see the LS Nav Online Help. 2018 11 0

A new and lighter version of Web Services has been introduced for Web Store Basket
Calculation. This improves LS Nav's ability to handle heavy load on the Web Store Basket 2018 11 0
Calculation.

An error occurred when finalizing orders in the Offline Call Center. The Web Service
OFFLINECC_SENDFINALORDE did not finish since the table Trans. Hospitality Entry was not 2018 11 0
optional. This has now been fixed.

The length of the Trans. Safe Entry description has been set to maximum 30 characters in
the Start/End float. 2018 11 0
This issue has been fixed. Now, deal lines are not lost when a coupon is voided.
2018 11 0
On the Online Help home page, a new link (Release Notes LS Nav 2017 (10.00-10.10) opens
a single PDF document with all release notes that were published in 2017. 2018 11 0