About This Release
Released - August 24, 2023
This version is built on Microsoft Dynamics 365 Business Central 2023, release wave 1, cumulative update 4, 22.4.59114.59535.
Important Notices!
For information about breaking changes in previous releases, click here.
LS Central release plan changes
We are changing how we release new features in LS Central. Until now, we have included new features in our monthly releases. The monthly releases therefore included new events and hotfixes as well as new functionality.
Based on feedback from our partners and customers, we are scaling this back a little. We have decided to align our product development with the release timeline used by Microsoft for Business Central. This means that we will release new features for LS Central in two major release waves every year – scheduled for April and October, coinciding with the general availability of Business Central Release Wave 1 & 2. Our partners will be granted access to a feature-complete release candidate five to six weeks ahead of time.
We will continue to release new events and hotfixes on a weekly basis and cumulative updates on a monthly basis, but new features will be focused on the April and October updates.
We will have a release candidate ready five to six weeks before the major release from Microsoft. This means that the release candidate for version 23.0 will be made available by the end of August.
After the changes, the LS Central release plan looks like this:
- Version 22.3 is scheduled for August 23.
- Version 22.4 is scheduled for September 20. This version will only include hotfixes.
- Versions 23.0 is scheduled for the first week of October, depending on the availability of the 2023 Wave 2 update from Microsoft.
- After this, minor versions will be made available on a monthly basis, depending on the availability of the minor update from Microsoft.
We expect to follow the same process for the 2024 wave 1 version, with a release candidate scheduled to be made available late February 2024 and an official release coinciding with the release of Business Central 2024 wave 1 from Microsoft.
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
LS Central
Loyalty points calculation based on store currency
The way the system calculates member points earned during a sale has been changed. Earned points are now calculated using the LCY value.
Printing reports with Hardware Station in more formats than A4
The Hardware Station printing capabilities have been expanded to include a range of paper sizes beyond A4. To support this, the field Printer Paper Kind has been added to the Printer Selections page.
Fashion
Description for Variant Dimensions
It is now possible to input a description that can better describe the Variant Dimensions, by using the new Description field that was added to these pages:
- Variant Framework Base Values
- Variant Framework
- Item Variant Framework.
New Quantities Item/Variants Report
A new Quantities Item/Variants report has been introduced showing the Sales (Qty.), Purchases (Qty.), Negative Adjmt. (Qty.), and Positive Adjmt. (Qty.) information for item variants over a specified period and a comparison period. The report shows the information for each variant, and also the aggregate on the item and item category level.
POS
EFT configurations moved to POS Terminal Card
Configurations on the POS EFT Card that are not related to EFT specific functionality but are rather to control the behavior of the POS itself have been moved to the POS Terminal Card, to a new FastTab called EFT.
These configurations have, for example, to do with configurations for printing EFT receipts and how to handle the tips functionality within the POS.
EFT configurations that were previously part of the General FastTab on the POS Terminal Card have been moved to the new EFT FastTab or marked as obsoleted.
Hardcoded panel IDs and profile IDs replaced with enums
Enums have now replaced hardcoded strings in control IDs.
Improved filtering
An issue that prevented filtering with more characters than the field type has been fixed. It is now possible to use special characters in filtering.
New field in POS Functionality Profile Card
A new field, Receipt Scanner Behavior has been added to the POS Functionality Profile Card.
The field specifies which panel will be displayed when you scan a transaction receipt. By default, the current Return panel opens.
There are two more options are available, one to open the Transaction List panel, the other to ask which panel to open.
Two new POS Commands were created: SCANNER_BEHAVIOUR and POPUP_SCANNER_BEHAVI.
Note: Regarding the Clear Filter button, there is already a RESET command that can be added to the menus. In that case, for Demo Data, you just have to add it to the #TRANS menu.
New field in POS Terminal Card
A new field, Include EFT information in Z Report, has been added to the POS Terminal Card, in the EFT FastTab.
The available options for the field are:
- Never - the POS will not add information from the EFT device to the X/Z reports. Use this option when the EFT device does not support this functionality.
- Ask user - displays a message box where the cashier can decide, if this information should be retrieved or not.
- Always - retrieves this information from the EFT device and adds it to the X/Z report without asking the cashier to confirm.
The default value for all terminals is Ask user, because that is the current default behavior.
POS commands and URL parameters created for Debug Log and Profiling
The following POS commands were created to reduce the manual overhead when this kind of data is needed for troubleshooting.
- DEBUGLOG
- DEBUGLOG_OPEN
- ALPROFILER
- ALPROFILER_OPEN
- POSREC
Some further debugging commands were also added to troubleshoot runtime errors or other dialog-based methods from Microsoft: ERROR_DIVZERO, ERROR, ERRORBEEP, MESSAGE, MESSAGEBEEP, CONFIRM and STRMENU. These commands are only expected to be used internally.
ShowPanel improved with empty panel ID
When the SHOWPANEL command is used with an empty parameter, the POS now displays the last active panel (closes the current panel).
Replenishment
Auto-Fill removed in Replen. From Warehouse setup
When entering Item No. in the Replen. From Warehouse list, the system will no longer automatically fill in the entry with the Division Code, Item Category Code, and Retail Product Code of the item.
Enhanced Replenishment for BOM and Components
Functionalities have been added to further improve the Replenishment solution for BOM and Components.
Support for Multi-Company Replenishment
The BOM and Component Replenishment Journals now support replenishment calculation with Multi-Company setup. The Replenishment Item Quantity (RIQ) for the BOM and Components will be calculated in each of the sales companies, before they are copied and consolidated into the supply chain company for centralized replenishment calculation.
When calculating the Component Transfer Replenishment Journal in the supply chain company, if the destination location resides in the sales company (set up with the Data Source of Other Company or Other Database in the Location Card), then Sales Orders will be created instead of Transfer Orders from the journal. As for the Assembly Orders involving BOM items that are produced in stores, they will be created from the BOM Transfer Replenishment Journal in the respective sales company, instead of the supply chain company.
For more information see Multi-Company Replenishment in the LS Central Help.
Bulk data maintenance with Replenishment Control Data List
The Replenishment setup fields related to BOM and Components replenishment calculation have now been added to the Replenishment Control Data List, to enable you to perform bulk update on the fields if needed. The fields that have been added include the following:
- Parameters that are available on the item's Replenishment Control Data page:
- Consider Consumption as Sales
- Use BOM/Component Journal
- Calc. Sold Comp. in BOM Jrnl.
- Parameters that are available on the item's Replenishment Control Data page, Item Store Record, and the Replenishment Data Profile:
- Effective Inv. Assembly Ord.
- BOM Assembled In
For more information see Replenishment Control Data List in the LS Central Help.
Get notified in the Component Replenishment Journal when a recalculation is needed
When a BOM Replenishment Journal has been updated, a notification will now be displayed in its relevant Component Replenishment Journals, to inform that a recalculation of the Component Replenishment Journal is needed to get the updated result. You can easily switch the notification on or off by using the Disable Notification (BOM Journal Update) setting in the Replen. Setup.
Improved Threshold Rule Values page
We have refactored the Total Cost Amount, Total Sales Amount, Total Profit Amount, Total Quantity, Total Weight, and Total Cubage fields which reside in the Information FastTab in the Threshold Rule Values page, to now show the total values of all the Replen. Journal Detail Lines, instead of the ones without threshold exceptions only from the relevant Replenishment Journal. This improves the performance of the page.
Furthermore, the integration event OnBeforeOnAfterGetCurrThresholdRuleValueRecord in the Threshold Rule Values page has been obsoleted and replaced with OnBeforeRecalculateTotalFields, to allow overriding the new behavior, if needed.
Item attribute value filter with lookup in Replenishment Journals
The Purchase and Transfer Replenishment Journals have been enhanced. Their Add Items to Replenishm. Jrnl. reports now come with an Item Attribute Value filter with lookup functionality. This makes it easier to select an available attribute value and add it to the report.
Also, to allow more attribute values to be used as filters, the Item Attribute Value Filter field has been obsoleted in the LSC Replen. Template and LSC Replen. Item Quantity tables, and the field is replaced with the new Attribute Value Filter field, having an extended field length of Text[250].
Rounding of Lead Time Sales Quantity in Replenishment Calculation
In Replenishment calculation, the Lead Time Sales Quantity has been updated to round to nearest instead of up, based on its defined rounding precision.
Setting up number series per location for sales orders created from Replenishment Journal
When working with Multi-Company Replenishment setup, you can now specify a different number series per location, for the sales orders that are created from the Replenishment Journal for the sales companies. You can set this up by using the Sales Order No. Series field in the Location Card and enabling the Create Sales Orders per Location setting in the Replen. Template for the journal from which you wish to calculate and create the sales orders.
Warehouse location selection in Allocation Plan and Stock Recall pages
A new field called Warehouse Location Selection has been introduced in the Allocation Plan Defined, Allocation Plan Distribute, and Stock Recall pages.
- The default option is From Replenishment Setup, where the system uses the Warehouse Location Code based on the setup from the Replen. From Warehouse if it exists, before using the Warehouse Location Code specified on the Allocation Plan or Stock Recall page to create the order documents.
- The second option is From Current Page Setup, where the system always uses the Warehouse Location Code specified on the Allocation Plan or Stock Recall page to create the order documents.
Restaurants
Hospitality table lock changed
In the Staff Permissions and Staff Permissions Group List pages, the field Open Din. Tbl. Locked By Staff has been added. This permission makes it possible for the cashier to open a dining table that is locked by staff (the staff member owns the table from seating) without having manager privileges. The cashier must also have the Open Sales POS permission.
Self-Service Kiosk: Upgrade to a meal
Customers are now offered to purchase a meal deal after selecting an item to buy. For example, when the customer selects a cheese burger from the menu, the Self-Service Kiosk now offers the customer to purchase a cheese burger meal. You must activate the upsell for the hierarchy the Kiosk is using and specify which deals are available for each item that is offered as an upsell deal.
LS Central Modules
Bookings for LS Central
Guest types
The Bookings module now supports Guest Types as an additional pricing identifier. This allows users to simplify product setup, by using same product settings for multiple pricing options, that is Adults, Seniors, and Children, for example.
New fields in Activity Setup
New fields, Backoffice POS Terminal No. and Backoffice Deposit Staff ID", have been added to Activity Setup and are used to make prepayments from Backoffice.
Web API enhancements
The Guest Type settings have been added to the Bookings' Web APIs for requesting availability and confirming reservations.
Hotels for LS Central
Hotels for LS Central is a separate app extending LS Central.
Booking Engine Connector adjustments
- The Booking Engine Connector app was adjusted to support new localizations. The tax amount is now coming from the Booking engine (SynXis). No VAT is now stored in tables.
- The Booking Engine Connector is now using Promoted Actions in all pages, but there are no visual changes are on pages.
Folio Deposit process in BackOffice
A new feature, Deposit Assignment, was introduced to assign Deposit Collected to different folios so that when paying, folios will consume the deposit assigned. This feature is accessible from Actions, below Balance Transfer. From this page, assignments can be done manually or automatically with the Auto-Assign button.
The deposit assignment consumption will be registered in the LSCHT Res. Payment Entry table, so a new type of line, Deposit Consumption was introduced. The Deposit field is replaced by Entry Type, an enum field that differentiates between Payment, Deposit, or Deposit Consumption.
Additionally, it is now possible to make a deposit directly to a folio. The Folio No. field was added to the LSCHT Deposit Amount Payment page.
New fields in Hotel Setup
-
A new field, Res. Extra Shoulders (No. of Days), has been added to Hotel Setup. The field specifies if and for how long the reservation extra shoulders are allowed. For example, if the user enters 7 in this field, the reservation extras can be added 7 days prior to arrival date and 7 days after departure date. For now, there is no limitation on the length of the shoulders. There are no shoulders, if the value in this field is 0.
Reservation extras are now in sync when reservation dates are shifted. When the reservation is changed, and the date on the reservation extra is not in the new reservation date range, the reservation extra is added, either on the first day or the last.
-
New fields, Filter Days Back and Filter Days Forward, have been added in Hotel Setup under Default Values. If these fields are set, they define the filter interval, otherwise the default is 90 days and 2 years like before.
New Rate Code config action
New action, Export to Excel, has been added to the Daily Room Rate Config and Previous Rate Config pages. The action exports the data to an Excel sheet in a format that the import action understands and users can import back to publish the rates again. This improves working with rates.
Night Audit Deposit consumption and folio check
If there are prepaid deposits for a reservation, the deposit is consumed as much as possible for each day. The deposit is posted as debit to the Customer Prepayments account and as credit to the Customer account. If the deposit is attached to a Folio, it is only consumed to that Folio, but otherwise it is used without a Folio check. The deposit consumption is posted to the Reservation Payment Entry table.
Routing Rules changed in line with folio structure
Demo Data for Routing Rules have been updated to comply with the new folio structure.
Split Bill panel removed from Hotel POS
The Split Bill panel and all its functionality has been removed from the Hotel POS.
Visual indicators added in Cancellation Prompt
New field, Included in Fee, was added to the lines page in Cancellation Prompt. Also, when you use the Escape key from the Cancellation Prompt, the Extras Fee is reset to 0 in the Hotel Res. Cancellation page.
Also, the Fee Created field is now displayed in the Hotel Res. Cancellation page to show what line was used to create the cancellation fee.
Pharmacy for LS Central
Pharmacy for LS Central is a separate app extending LS Central.
Expiry handling
Expiry handling is now part of the LS Central solution.
New Pricing experience
New Pricing experience has been implemented in W1 and IS and NO localizations.
Procedure SetMarkedLines
Selecting one or more lines in Pharmacy Customer Order POS panels is now possible and visible.
Staff Management for LS Central
Deleting roster removes all entries in the Day specific table
Deleting a roster in Staff Management now removes all related capacity and unavailability settings in the Bookings module.
Supporting Functionality
Hardware Station for LS Central
Hardware Station printing app: print different sizes on a Windows printer
The Hardware Station for LS Central printing app can now print in sizes other than just A4.
Note: The regular Hardware Station for LS Central is not capable of this.
OPOS printing on a Windows configured printer: line spacing
To avoid generating extra lines, the default value for line spacing in Windows printers has been changed from 10 mm to 1 mm.
Other
POS Commands
The following POS commands are new in LS Central 22.3:
| ALPROFILER | To start AL Performance Profiler or stop/download from it. |
| ALPROFILER_OPEN | To open the AL Performance Profiler page. |
| DEBUGLOG | To start POS Debug Log or stop/download from it. |
| DEBUGLOG_OPEN | To open the POS Debug Log Setup page. |
| POPUP_SCANNER_BEHAVI | Displays a pop-up menu with the option values from the "LSC Receipt Scanner Behaviour enum. The command is called to select what panel to open when scanning a transaction receipt. |
| POSREC | To start POS Client data or stop/download from it. |
| SCANNER_BEHAVIOUR | Process the scanned transaction. Based on the POS Functionality Profile field Receipt Scanner Behaviour, which opens the respective panel. |
See POS Commands in the LS Central Help and the corresponding Excel list with filters for a complete list of POS commands.
Fixed Issues
LS Central
LS Central
Bug-Fix-For-Purge_Transactions
Code has been added to make sure the Purge functionality only applies to the active terminal. Some performance tweaks were also added to the code.
Error replicating Hierarchies to LS Magento - node ID too long
Handling of preactions has been enhanced to handle correctly a primary key where ‘;’ is part of any primary field's value.
Parameter character length issue
Procedure parameter CheckItemUnitOfMeasureCode was updated to allow a bigger Description.
Recipe item explode at posting not working
Statement posting has been enhanced to include the field LSC Statement No. when posting BOM items. This enhances navigation for posted statements to include (show) inventory movements for BOM items and components.
Note: Everything is already posted correctly, it is only the navigation page that does not pick up all the posted entries.
Statement calculating transaction integrity
A check was added to confirm that the Trans Sales Entries line count is equal to the Trans Item lines count, and that the Trans Payment Entries lines count is equal to the Trans Payment lines count. An already existing procedure was used.
Web Request enhancements
The following web requests enhancements have been implemented:
GetActionsFromRmtDBV2 not working with actions
Data Distribution WS has been enhanced to handle both remote preactions and actions. This was done by replacing web request GetActionsFromRmtDBV2 with request GetActionsFromRmtDBV3.
Note: This requires web request GetActionsFromRmtDBV3 to be Published and Subscribed in all relevant locations.
GetStaffV2 response is not correct
Web request GetStaffV2 has been enhanced to include fields POS Menu Profile and POS Style Profile.
Note: This requires web request GetStaffV2to be Published and Subscribed in all relevant locations.
Fashion
Issue when running Purchase Order Matrix Report with Matrix Output Type
When running the Purchase Order Matrix report with Output Type set to Matrix, an error occurs if the Purchase Order consists of Purchase Lines with variant items. This has now been fixed.
POS
The following fixes have been implemented in the POS:
Calendar menu jumps many months on clicking next/previous month
The Calendar panel sometimes chose a wrong date for users on timezones reaching previous/next date.
Disabled POS buttons are no longer shaded
Buttons that only display information, like status for example, or do not have any text at all (blank buttons) are shaded (grayed), if they have the disabled property set to true. To revert the change, set the Disabled property to false. This has no side effect for these buttons as no functionality exists for them
Joining arrows disappear when menu is loaded without loading the joined buttons
An issue that caused the joining arrows to disappear when a menu was redrawn, has been fixed.
Replenishment
Default Replenishm. Grade Code field not visible on Location Card
When the Store Items Ranged By field in Replen. Setup is set to Item Category/Grade, the Default Replenishm. Grade Code field in the Replenishment FastTab in the Location Card was not visible. This issue has now been fixed.
Issue when running Replen. Update Out of Stock Report
An error that occured when running the Replen. Update Out of Stock report, caused by the Replen. Stock Out Scheduler job not being pre-configured in the system, has now been fixed.
Issues with Replenishment Journals when working with Planned Stock Demands
- When adding items to the Replenishment Journal with Planned Stock Demands, an error that occurred when there are multiple Planned Stock Demand lines having the same item, has now been fixed.
- When calculating the Transfer Replen. Journal with Planned Stock Demands having item variants, an issue where the transfer quantity of the item variants is not limited by the available warehouse effective inventory, has now been fixed.
Language-specific date formula issue in Allocation Rule pages
When certain non-English languages are used (for example fr-BE), an error occurred when updating the Date Formula for Start Date and Date Formula for End Date fields in the Allocation Rule and Allocation Rule Calculation pages. This has now been fixed.
Locking issue when running Replenishment Item Quantity Calculation in parallel
A locking issue that occurred on the Scheduler Job Header table when running the Replenishment Item Quantity (RIQ) calculation in parallel, has now been fixed. Additionally, the performance of the master job when assigning the item range to the linked Scheduler jobs, has been improved.
Overflow in Replen. Planned Events when linked to Discount Offer
When a Replen. Planned Event is linked to a Discount Offer with No. exceeding 10 characters, using the Update Lines action in the Replen. Planned Events page causes an overflow error. This has now been fixed.
Replen. Sales History Adjustment Calculation Rules using Planned Demand Event with Out-of-Stock Days
When creating the Sales History Adjustment (SHA) entries using the Replen. Sales History Adjustment Calculation Rule with Planned Demand Event type, the system now excludes the sales that occurred on an out-of-stock day from the average sales quantity calculation. This fixes an issue where the Adjusted Qty in the created SHA entries have a growing value on each subsequent day.
Also, if Stock Out Functionality is disabled in the Replen. Setup, the Out-of-Stock calculation results are disregarded in the Replen. Sales History Adjustment Rule calculation.
Replenishment Item Quantity not calculated for warehouse locations
When an item is set up with the Replenishment Calculation Type of Automatic - From Data Profile but is not assigned with a Replen. Data Profile, the Replenishment Item Quantity (RIQ) records are not calculated for the warehouse locations even when valid Item Store Record(s) exist for the store locations. This issue has now been fixed.
Store Group Filter in Replenishment Journal
There is an issue where the Store Group Filter set on the Replen. Template is not applied correctly when the Replenishment Journals are calculated with the scheduler job. This has now been fixed.
Restaurants
Producing recipes - message about posting
When checking availability for recipe ingredients, users are now asked if they are sure they want to produce items even if they have enough in stock.
Shopify
Shopify bug fixed
Price with or without VAT has been fixed.
Hotels for LS Central
Cancel Charge Value opens as non-editible on Open page
A bug occurred when users edited the Cancel Charge Value in the Cancellation Policy Line subpage, the field always opened as non-editable. This has now been fixed.
Cancellation Policy issues
The following issues with Cancellation Policy have been solved:
Cancellation Policy does not calculate penalty fee correctly
An issue occurred when setting a cancellation scenario over a number of days before arrival without specifying a top limit. Now, use 0 or blank to specify the period over the biggest No. of Days in the setup.
Also, the caption for the field Cancel No. of Days has been updated with Cancel within No. of Days for clarity. When a value is specified in that field, days from the arrival/confirmation date to the set value are included.
Cancellation policy prompt overwrites selection
Functionality has been changed, so that now when adding the reservation Extra item to the cancellation Fee, instead of combining it into one single DRE line, the original DRE lines of the selected Reservation Extra items are kept. This way, the correct TAX information is kept, based on the items, and it is clear what the guest has to pay and for what.
Confirmation message needs to be suppressed
Copying reservation comments to group comments has been fixed.
Customer discount fix
Customer discount was not changed when the customer was changed in reservation extra. This has been fixed.
Demo Data setup
The default value for the Account Method field in Hotel Setup(the Night Audit FastTab) has been changed from blank to Temp Balance.
Error in voiding a transaction
An issue with voiding a transaction with a deposit has been fixed. The payment entry was not reset correctly and gave an error when the user tried to pay again.
Extra lines with daily posting pattern not added with correct dates to DRE
Extra lines with a daily posting pattern were added to DREs with the date of the Reservation Extra Line instead of each day of the reservation. This bug has been fixed.
Issue in Demo Data with routing rule
An issue with folio templates for routing rule in Demo Data has been fixed.
Items added and paid on POS through Finalize Invoice not marked as paid in DRE
After extras were added in the POS and payed there, the corresponding DRE lines were not marked as paid. This has been fixed.
Reservation Extras cancellation amount not calculated correctly for daily posting pattern
A bug occurred in the cancellation fee when it included Daily Res. Extras. The amount did not include the real amount for all reservation days. This has been fixed.
Routing Rule validation
Routing Rule validation has been moved into the Hotel Invoice Management codeunit. It was exposed externally with the HotelInvoiceMgt_ValidateRoutingRule function in codeunit Hotel Integration.
Pax counter in Group Reservations
A bug occurred in the Pax counter in Group Reservations when a guest was deleted in the Guest List. The bug was fixed, and a drill-down action for the Reservation No. field was added to open the Guest List directly from the field.
When upgrading to another rate code the balance is calculated incorrectly
An issue that occurred when upgrading to another rate code caused some DRE activity lines to have an incorrect price. Now a functionality checks price consistency with related activity reservation.
Pharmacy for LS Central
Agent header in FMD requests
A user agent header was added to FMD requests for Solidsoft.
Change local property on event OnBeforeGetExternalWebPage
The property has been modified on event OnBeforeGetExternalWebPage.
Interaction Tables enhancements
The Issued Item and the Delivered Item are now shown in the Intervention Log list page. Minor enhancements have also been made to the ATC Interaction table.
Internal e-prescription upload can fail
Prescriptions uploaded to the demo gateway now have a unique prescription number and an Original Prescr. number.
SE comments enhancements
Changes have been implemented in the handling of SE comment fields in the Split process.
Missing code in W1 AL that was waiting for LS Central updates has now been added.
Supporting Functionality
Commerce Service for LS Central
The following fixes have been implemented:
- AL: Fix GetMemberContactInfo
Blocked info added to Member Contact information and password removed.
-
ReplEcommMember endpoint does not return Cards object
New OData Replication function GetContact2.
Kitchen Display System for LS Central
Fix BumpToPrinter in KDS and production times
Bump to Printer from a display station has been fixed.
Hotfixes
See the LS Central Help for information about hotfixes that have been released since the previous release.