About This Release
Released - June 29, 2023
This version is built on Microsoft Dynamics 365 Business Central 2023, release wave 1, cumulative update 2, 22.2.56969.57617.
Important Notices!
For information about breaking changes in previous releases, click here.
LS Central Universal Code Compliant
From version 22.0 LS Central is Universal Code compliant. This means that the property Target in the app.json files for the LS Central and LS Central System apps has been set to Cloud.
Customers who have the granule Implemented code is not cloud-optimized in their license can ask for this granule to be removed, once they have upgraded to LS Central 22.0 or higher, unless there are other extensions installed that are not Universal Code compliant.
Deprecation of Windows Authentication for Web Services
Windows authentication for web services has been deprecated. The Windows authentication was based on Business Central Windows authentication code. The Business Central Windows authentication code is marked as OnPrem and can therefore not be used by Universal Code compliant applications. This does not affect SaaS customers as the only authentication method supported in SaaS is Oauth authentication. On-premises customers must switch from Windows authentication to either Basic authentication (Web Service Access Key) or OAuth authentication for web services before upgrading to version 22.0 or higher.
See How to: Set Up Basic Authentication for Web Services in the LS Central Help for instructions.
Obsolete code marked with tag 20.0 and below removed
Our solution gets bigger with every release, but we intend to clean up by removing obsolete code in major releases as soon as the code has been marked obsolete for at least a year.
In release 22.0 we removed constructs like procedures and events, but there are no breaking schema changes yet, like Tables and Table fields.
Recommended action: Check if you are using a feature that has been marked obsolete for more than a year. The warning should state the reason and the alternative that is intended to be used.
OnPrem-only procedures are now obsolete
All procedures and objects that are marked #if _IS_SAAS_, previously marked [Scope('OnPrem')], have become internal, unless otherwise requested.
If your extension is using any of these, they will now get a warning.
Recommended action: If you have an OnPrem extension, check if there are any warnings. Usually, there are alternative procedures available, but partners can also request that a list of these is made public through the same flow as event requests.
Integration event triggers are now internal/local
In rare cases, it has been technically possible to trigger some of our events from an extension.
These cases are usually an oversight, since the internal/local keyword was missing for the IntegrationEvents so they became public, by default.
This has prevented us from adding new arguments to existing events, and therefore unnecessarily forcing new versions for events where a breaking change would not have been needed.
Recommended action: This should not require any work. There is a chance that somewhere an upgrade might fail, if it is calling an event function, for example in POS Transaction Event, which usually has no effect. Instead, the events are intended to be subscribed to, with an EventSubscriber.
Click here for a printable version of this notification.
New or Enhanced Features
LS Central
POS
POS constants, hard coded POS tags replaced with enums
Hard coded strings in POS tags have been replaced by enums.
Replenishment
Replenishment for BOM and Components
A new functionality in Automatic Replenishment has been introduced, to work with the replenishment calculation of Bill of Materials (BOM). The solution calculates the demand for the BOM items and then breaks down the demand into their Components, which are purchased and transferred.
This process is common in Hospitality, but is not limited to that industry, it can be applied to all item types that use the Assembly BOM concept.
For an overview of the Replenishment for BOM and Components concept, see Replenishment for BOM and Components in the LS Central Help.
New Replenishment Journal Types for BOM and Components
The BOM Replenishment Journal and Component Replenishment Journal have been introduced to work with the replenishment calculation for BOM and Component items. The calculation is done in a two-step approach where the demand of the BOM items are first calculated in the BOM Replenishment Journal, and then in the second step, the system calculates the replenishment quantities of the Components in the Component Replenishment Journal, based on the demand of the BOM and the number of each Component needed to assemble the BOM.
Refer to the following LS Central Help pages for more information:
- To understand how the items and Replenishment Templates can be set up to work with the BOM and Component Replenishment Journals, see Common Replenishment Data Fields and Replenishment Templates.
- To learn more about the process behind the replenishment calculation for BOM and Components, see Calculation Process for BOM and Components.
Assembly Orders in Replenishment
The BOM and Components replenishment process supports Make-to-Order (set up with the BOM Method of Explode at Posting in the item's Recipe Card) and Make-to-Stock (set up with the BOM Method of Produce in the item's Recipe Card) BOM items. For Make-to-Stock BOM items, since they will be produced in advance and stored in inventory, Assembly Orders can be created in the BOM Replenishment Journal for the BOM items to be produced in the warehouse or the stores.
Also, you now have the option to include the quantities from open Assembly Orders in the Effective Inventory calculation in Replenishment.
For more information see Create Assembly Orders in the LS Central Help.
Integrating Weekly Menu Planner with Replenishment
You can now link a Replenishment Planned Event with a Weekly Menu Planner, to allow the meals that have been entered upfront in the Weekly Menu Planner to be transformed into Planned Sales Demands. The additional sales from the Planned Sales Demand lines add to the demand from regular sales in the stores and the summarized demand is calculated in the BOM Replenishment Journal.
For more information see Producing Recipes in the Weekly Menu Planner in the LS Central Help.
Replenishment Calculation for Components without recipes
You now have the option to include Item Ledger Entries of type Negative Adjmt. and Assembly Consumption in the Daily Sales calculation in Replenishment Item Quantity (RIQ). You can activate this option by using the Consider Consumption as Sales setting in the item's Replenishment Control Data page. This allows the consumption history of Components without recipes, which are usually being posted as Negative Adjustments to be tracked similar to the sales history of generic items. As a result, the Components can be replenished with the Average Usage method, using the standard Purchase and Transfer Replenishment Journals similar to the process for non-BOM items.
For more information see Replenishment for BOM and Components - Component Centric in the LS Central Help.
LS Central Modules
Hotels for LS Central
Hotels for LS Central is a separate app extending LS Central.
Adjustments to Booking Engine Connector (BEC ) app
- As support to new localizations, VAT is no longer stored in tables.
- Promoted Actions are now used in all pages, no visual changes on pages.
Occupancy-based pricing extended to five adults
Now, when using Occupancy-based pricing, users can have separate pricing for adults 1-5 instead of only Adult1 and Adult2.
Pharmacy for LS Central
Pharmacy for LS Central is a separate app extending LS Central.
Credit Order to a different stock location
Functionality has been added to do an automatic inventory transfer to another location, when a POS transaction containing a Prescription Credit Order is posted in the Statement posting process. The user selects the Item type(s) and Refund Reason Codes.
Staff Management for LS Central
Roster creation added to license check in SaaS
When the roster is created, the SaaS subscription license is now checked.
Time batch registration
The employee name is now displayed in the Time Batch journal.
Supporting Functionality
Kitchen Display System for LS Central
Selection of multiple display stations, the Next Station field moved
In KDS, it is now possible to have more than one Next Station for a Display Station. The Next Station ID field has been moved to the Section Display Stat, Mappings list instead of on the Display Station itself.
Fixed Issues
LS Central
LS Central
Periodic discount & infocodes, mismatch between Trans. Discount Entry and Trans. Sales Entry
Code change was implemented to make sure that when the infocode affects the line VAT, the associated discount lines are also affected.
Replication of blob to SaaS
Encoding has been fixed when replicating BLOB to SaaS.
POS
The following fixes have been implemented in the POS:
Auto-Logoff in Tender Declaration with Safe Management
Now Auto-Logoff does not close the POS while in Tender Declaration state.
Error occurs when a POS menu is deleted
Function is not invoked if the interface has not been initialized.
Logo position
The position of the LS Retail logo in the Run POS screen has been corrected and is now in the center of the screen.
POS transaction posting error leaves POS hanging
If an error occurs in an extension (like divide by zero), the POS is no longer left in a hanging state.
Staff lookup, command CH_STAFF does not display the staff list
Staff lookup was showing an empty list when running the CH_STAFF POS command. This has been fixed.
Replenishment
Replen. Item Quantities Calculation issue in Add Items to Replenishm. Jrnl. Report
When the Calculate Inventory option is selected and the Vendor No. filter is defined in the Add Items to Replenishm. Jrnl. report via the Purchase Replenishment Journal, Transfer Replenishment Journal, or Redistribution Replenishment Journal, the system applied the filter strictly based on Item level setup, thus causing the Replen. Item Quantities not being calculated for items with different Vendor No. setup on their Item Store Records. This has now been fixed.
Restaurants
Issue with Loading Cards and Confirm Order command
Do not use POS command CONFIRMORDER for Loading Cards.
Shopify
Shopify fixes:
- Order of options (attributes)
- Support Blob data in Metadata.
- Fixed images being sent multiple times.
Hotfixes
See the LS Central Help for information about hotfixes that have been released since the previous release.