About This Release
Build no. - 673
Released - May 9, 2018
This version is built on Microsoft Dynamics NAV 2018, build no.
Note:
The 64-bit client is now the default client when opening NAV.
In this version the POS is only supported to run on the 32-bit Dynamics NAV Windows client. We recommend setting up the 32-bit client in the LS Nav Start tool for the POS.
The following is a list of changes and key features in LS Nav 2018 (11.02).
New or Enhanced Features
Retail
EU General Data Protection Regulation (GDPR) Adjustments
Microsoft now has two new properties in their table fields:
- Level 1 - the DataClassification property, released in early March with CU3.
- Level 2 - the DataSensitivity property, released in April with CU4.
Adjustments have been implemented in LS Nav to comply with those new properties.
Data Classification Level 1
This classification requires access to the database tables and can be set by Microsoft Partners.
There are seven Data Classification values:
- CustomerContent - General DataClassification, used in most tables.
- ToBeClassified – Default value when a new field is created.
- EndUserIdentifiableInformation - References or relations that identify the NAV user.
- AccountData - Used for billing information. Not currently used.
- EndUsePseudonymousIdentifiers - ID or No Series that reference the NAV user. Not used.
- OrganizationIdentifiableInformation - Used to identify Tenants. Not in standard LS Nav (Consulting/Partners).
- SystemMetadata - All FlowFilters and FlowFields.
Data Sensitivity Level 2
- This will be visible and editable by IT managers.
- Work can be started in Excel and then later imported.
There are four values:
- Sensitive: political opinions, religion, physical or mental health, sexuality.
- Personal: Information that can be used to identify a data subject, either directly or in combination with other data.
- Confidential: Business data used for accounting or other business purposes, ledger entries for example.
- Normal: General data that does not belong to any other categories.
All LS Nav fields have been classified in the same manner as the Microsoft Dynamics NAV fields. Please note that this classification is a recommendation – it is then up to you to make sure you are following your local regulations.
Microsoft has announced that the DataClassification property and Data Sensitivity classification are in the latest CU for NAV 2015 (CU 41), NAV 2016 (CU 29), NAV 2017 (CU 16).
See Classifying Data in Dynamics NAV and Data Protection Resources on the Microsoft web site for more information.
Customer Orders on POS
The Customer Orders feature now supports creating customer orders on the POS. The orders are entered on the POS and sent through web services to the Head Office database. All updates to customer orders are done by web services.
Customer orders created on the POS can be collected by the customer from another location or be shipped from stores and warehouses to the customer.
The Customer Order feature lets the user configure, if payment occurs when the customer collects the order or if payment must be made when the order is placed. Shipment orders must always be paid at the time of placing the order.
When a collection order is created, the system will trigger the transfer order needed between the locations.
Replenishment Enhancements
Multi-Company Replenishment for Automatic Replenishment
The Multi-Company Replenishment feature is now supported in automatic replenishment. It works in an environment with multiple legal entities, which involves a central supply chain company with one or more sales companies, where all these companies reside in the same LS Nav database.
The Replenishment Journal calculation takes place in the central supply chain company. It will process the Replenishment Item Quantity (RIQ) data in the central supply chain company together with the pre-calculated RIQ data consolidated from the sales companies. This process facilitates the central purchases in the supply chain company, and then distribution of the items by creating sales orders to the sales companies.
Master-Child Replenishment for Automatic Replenishment
The Master-Child Replenishment feature works in an environment with stores that operate as a stock buffer (Master store) for other stores (Child stores). The item replenishment is only performed and received at the Master store, and therefore, the Replenishment Item Quantity (RIQ) of the Master store will contain the aggregated information (Inventory and Quantity on Purchase Order, for example) from its own and also from its assigned Child stores.
New setup and fields have been added to the Location (14) and Replen. Item Quantity (10012205) table to support these two features.
Order Multiple and Transfer Multiple in Decimal Values for Automatic Replenishment
Order Multiple and Transfer Multiple in decimal values are now enabled in automatic replenishment.
A multiple in decimal is handled similarly to a multiple in whole number. During the replenishment journal calculation, if the quantity suggested by the system is not in full multiple, depending on the Replen. Multiple Rounding setup, the quantity will either be rounded up to the next nearest full multiple, or rounded down to the last nearest full multiple.
Copy Budget Improvements
The Copy Budget functionality in the Retail Sales Budget and Retail Purchase Budget page has been improved.
The budget entries of a more detailed budget can now be copied to a more generic budget (for example, to copy an Item budget to a Product Group budget). An Item Hierarchy budget has the same level as an Item budget, where its budget entries can be copied to another Division, Item Category, Product Group, Item, or Item Hierarchy budget.
Master-Child Budgets Consolidation Improvements
The Calculate Budget from Child Budgets functionality in the Retail Sales Budget and Retail Purchase Budget page has been improved. Similar to all other types of budget, when served as a child, an Item Hierarchy budget is able to push its budget entries to a parent with a more generic budget type. An Item Hierarchy budget shares the same level as an Item budget, which means, it will be able to push entries to a parent with Division, Item Category, Product Group, Item, or Item Hierarchy budget type.
Improved Page Structure for Retail Sales Budget and Retail Purchase
The structure of the Retail Sales Budget and Retail Purchase Budget pages has been improved to support multiple-user environment.
The budget entries' tree view is now a subpage within the primary Retail Sales Budget and Retail Purchase Budget pages. These subpages make use of a temporary source table so that each user accessing the page is assigned with a unique virtual workspace, thus allowing multiple users to access the budget page at the same time.
New Field in Stock Coverage: Ending Date
A new field, Ending Date, has been added to the Stock Coverage table. The Ending Date will be populated automatically while selecting Season Code. When the Ending Date is not empty, the Goal (weeks) is dynamic.
Clienteling Improvements
- Breadcrumbs now use Retail Hierarchy's description instead of the code.
- It is now possible to click a filter's text to select check boxes, instead of having to press the tiny check boxes.
- A new Product Compare feature has been introduced in Clienteling to compare two items and the attributes assigned to them.
- It is now possible to add a member to the sale in the Clienteling panel.
- New panels have been added showing information about the member that has been added to the sale. This includes a small panel showing basic information and a large panel showing detailed information including purchase history, offers, and coupons.
New Web Services
New web services have been introduced in Framework 2.0:
-
GetDirectMarketingInfo
This web service replaces LOAD_DIR_MARK_INFO and LOAD_PUBLISHED_OFFER_ITEMS. Instead of the item list, the lines are now received from the published offer. The lines are either from the Offer, Periodic Discount, or Coupon Header tables.
-
GetTransaction
This web service, which is also published as a part of the Omni Wrapper, replaces GET_TRANSACTION.
Functionalities Now Handled by Event Subscription
The following functionalities have been removed from standard MS code and are now handled in LS Nav by subscribing to events:
- Purch. Price Calc. Mgt.
- Inventory Posting To G/L (C5802)
- Item Jnl.-Post Line (C22)
- Gen. Jnl.-Post Line (12)
- CaptionManagement
- TransferOrder-POST
Dynamic Menus
Dynamic menus have been extended to support item images.
New POS Commands
The following POS commands are new in LS Nav 11.02:
| Function Code | Description |
|---|---|
| CO_CANCEL | Cancel customer order |
| CO_CREATE | Create customer order |
| CO_CUSTOMER | Open customer panel |
| CO_ITEMS | Open item panel |
| CO_LIST_COLLECT | Customer order filter list is on to collect orders |
| CO_LIST_INSTORE | View all customer orders in current store |
| CO_LIST_PICK | Customer order filter list is on to pick orders |
| CO_LIST_SHIPPED | Customer order filter list is on to put back orders |
| CO_LIST_WAITING | View incoming customer orders from other stores |
| CO_OK | Customer order OK |
| CO_SHIPCOLLECT | Open collect/ship panel |
Other
New Topics in Online Help
New help topics have been added to the LS Nav Online Help:
Fixed Issues
Web POS
-
Printing Z-Report
Code has been moved so the X-Z-Report Statistics record is now modified after printing is finished (dialog is shown on Web POS).
-
Safe Management
The Safe Management functionality is now available in the LS Nav Web POS with the same functionality as in LS Nav Win POS.
Replenishment: Retail Budgets Actuals View
When the Retail Sales Budget and Retail Purchase Budget page is switched to Actuals view, the Value Entries page, which opens when drilled-down from the budget value, is now filtered correctly according to the Item Group or Item Hierarchy of the selected budget value.