About This Release
Build no. -
Released - September 28, 2017
This version is built on Microsoft Dynamics NAV 2017, 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 2017 (10.07).
Hospitality:
Negative Adjustment Mode on the Hospitality POS
Negative adjustments and physical inventory postings on the Hospitality POS are no longer sent to the KDS.
Replenishment
Planned Sales Demand Worksheet Enhancements
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:
- 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 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 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 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 in the Replenishment FastTab. The quantity in the initial budget entry will be distributed to the new entries based on the weights and share percentage as per setup for each store in the Allocation Rule.
Retail Budgets Improvements
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. 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.
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 Retail Purchase Budget pages respectively, have been added for opening the budget for maintenance.
- Minor naming fixes have been implemented in Retail Budget.
Improved Copy Budget Function
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.
Budget Validation and Correction
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.
Destination Group Validation in Allocation Rule
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 one Allocation Rule Line.
Retail:
Backoffice: Filter Added to AddItemsToHierarchy
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.
Inconsistent Information on Receipts: Rounding Difference Corrected
A potential rounding difference has been fixed between a transaction line discount amount and a discount amount in underlying transaction discount lines.
Incorrect Sync Time in Search Index
Incorrect sync time has been fixed in search index where the time zone is other than UTC.
LS Hardware Station: Management Portal Into Hardware Station Service
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.
LS Hardware Station: Service and Console
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.
POS: New Event (LS Nav POS API)
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 BrowserControl by using the LSUtils.SendPosCommand function.
POS: Validation of String Length in the On-Screen Keyboard
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.
Warning Issued if Two Users Are Simultaneously Trying to Use the Same Terminal
A warning is now issued if a POS user is logging on to a POS terminal that is already open in another session.
Server Tools: Control Panel for Functions in Hardware Stations
Tools have been added to restart Hardware Station service and to reset configurations.