LS One 2017.2 Service pack

 

After the LS One 2017.2 release some bugfixes and changes have been made, here below is a description of these changes.

If this service pack is to be applied as an update to a customer already running version 2017.2 then the entire LS One suite needs to be updated i.e. Site Manager, POS, Site service and the OMNI server (if applicable)

 

If this service pack is to be applied as an update to a customer already running version 2017.2 and using data replication the database design needs to be updated.

Site manager improvements

When the Site Manager is started now a splash dialog with a spinner is displayed while the Site Manager is checking the license. The license dialog that was always displayed if the user had a demo license is not displayed anymore. To activate the Site Manager the user must now select to activate it.

When deleting the audit logs from Site Manager and if an error happens during the deleting (f.ex. a time out) the user is now notified of the error. Before no indication was displayed.

A hyperlink that opens the buy LS One licenses page will be shown on the login screen of the POS or Site Manager when the license expiring message is shown.

When importing information using Excel import all string values from the Excel document are now trimmed.

The user can now configure the system to allow manual entry of gift card IDs (numbers). When this is set a new option is added to the Gift cards view (in the Action box) where new gift cards with specific numbers can be created.

Fixed an issue where cash or credit card amounts would not be shown correctly in a posted statement when viewed from the store level.

When creating a purchase order before the user needed to have Edit retail item permission. This has been changed and now the user only needs "Manage purchase order" permission.

Added a new action in the stock counting items view which allows aggregating all items based on id, unit and area.

A new field was added to the barcode table. An issue that was causing barcodes to not be replicated when edited needed this change.

Operations auditing view had some search issues that have been fixed. A new topic has also been created in the development help explaining the configurations for the operations auditing.

When creating a stock counting journal from an existing journal the item lines still had line status of posted. This has now been fixed

A bug has been fixed in Site Manager where inventory on hand was calculated incorrectly after returning the item and statement posting

A new configuration that sets when the periodic discount cache is cleared. The default configuration is "Before each sale" but it can be set to be reset after 60 minutes for example. These configurations are available in the Discount settings tab on the Administration view

A bug has been fixed in Site Manager where the default purchase price for vendor item was not updated when importing the items from an Excel file

When importing items and you have a vendor set on the item, that vendor will now be set as the default vendor for that item.

An error was thrown when selecting an item that was a variant item in one of the goods receiving dialog. This has been fixed

Purchase order report was missing from the System report package. The package has been updated to include this report

When importing a stock counting journal through Excel the staff ID was not updated

When creating a stock counting journal using a filter an error was thrown. This has now been fixed.

An issue has been fixed where errors were being thrown when editing the description of an inventory template area line.

When editing a discount offer line an error was thrown. This has now been fixed.

RMS Migration plugin now includes fixes done in previous versions where the item ID from RMS is used when creating the items in LS One

New Extra Info variables have been added to all section of the form layouts; header, lines and footer

LS One POS improvements

In some cases the POS was not enabling the "synch locally saved customers with head office" button in the customer search dialog even if there were locally saved customers in the database. This has now been fixed

If the user selected to edit a customer that had never been saved centrally (because the Site service was not operation when the customer was created on the POS) the POS would throw an error. This has been changed to save the customer centrally, mark it as not being locally saved anymore and then the user can edit the customer information as is needed.

A hyperlink that opens the buy LS One licenses page will be shown on the login screen of the POS or Site Manager when the license expiring message is shown.

Added the total amounts box to the dual display. New system styles have been added for the total amounts in the dual display. The layout in the dual display is now the same as the one on the POS.

Total amounts are now displayed with and without tax on the receipt panel on the POS layout and the Journal dialog if the Store is configured to not display total with tax

Fixed an issue causing the declare start amount operation to not display the correct amount after performing a float entry operation.

Tender declaration now allows entering of negative amounts.

Added a section to Z-report with over/short amounts for each tender that requires counting.

A bug fixed in the line display where price per unit was not correctly displayed

The POS now displays the correct list of users on login, depending on the store that is attached to the their profile (if the POS is configured to display a list of employees at logon)

Fixed an issue causing a wrong error message to be displayed when a customer exceeds it's max purchase discount on a sale.

Fixed a bug causing the POS app to crash at startup when Business Day is not set.

Fixed a bug causing the discount to be applied on items with the "No discount allowed" flag set to true.

When updating an existing customer a bug was causing the transaction to be removed from the POS before the user had the chance to make additional payment. This has been fixed

Fixed a bug where the POS user with login names longer than 10 characters do not get correct user profiles

Fixed an issue where price calculation was triggered for all items on a transaction after adding an item with zero price valid or overriding the price of an item

Issue fixed when using an OPOS scanner items were added two and three times to a transaction after EOD & Z-Report was printed.

Unload/Load devices when user is logging back on to the POS is now disabled. Changes due to support issue LSTS-2515

A bug has been fixed in LSOne POS where the quantity of a returned linked item was incorrect if the returned item was the first item in the transaction

When an item already added to the POS has it's Unit of Measure and Qty changed, the price did not take effect immediately. This has now been fixed

Fixed an issue where the entered quantity on the numpad was not cleared when the user selected the C button on the numpad

Open menu operation (previously only accessible from the POS UI) can now be run from code in a customization

When an item that has linked items is voided the linked items are now also voided automatically.

When the user is doing a permission override in the POS, the POS now correctly checks if the account is disabled.

If the user runs operation Inventory lookup before adding any items the POS doesn't discard the transaction anymore. This means that if the terminal is configured to log out after each transaction the POS will remain in the POS layout

Site service improvements

The Site Service had some issues with speed and performance especially when posting inventory documents that have thousands of items in them. Changes were done in the Stock counting functionality to fix this performance issue there. The other inventory documents still work the same as before but these performance issues will be addressed in the entire inventory functionality within LS One in the next release.

A topic has been created in the development help on how to change a report to be a "Site Servicereport" i.e. all information is retrieved from the central head office database.

Mobile inventory app changes

When receiving items through the inventory app and the items didn't have a default vendor on them those items were not posted and the user was not notified. The items are still not posted but the user is notified that there are items that don't have a vendor on them and that this needs to be changed before posting.

Sending stock counting journals from the mobile inventory will no longer create duplicate journals. Instead, if there is an existing open stock counting journal created from the mobile inventory app that is related to the same template, sending items from multiple devices will aggregate the items into the same journal.

Fixed an issue causing items to be added to the first stock counting journal created in the mobile inventory app, based on a template set on all stores, when sending items from multiple stores.

If an inventory template was configured to be for "all stores" the inventory app could not display it properly. This has now been fixed.

Fixed an issue causing barcode information to be missing when adding items to a purchase worksheet from the mobile inventory.

Fixed an issue causing documents to not be loaded when receiving documents that have multiple variant items with the same header items.

Fixed an issue causing the item's default vendor to be missing when sending a purchase worksheet from the mobile inventory app.

When a stock counting journal is sent from the inventory app now the stock counting lines and journal information is saved to the OMNI server database. Then the OMNI server starts a background thread to process the journal lines so that the inventory app does not need to wait for the update to the stock counting journal to finish. The background process will process the lines in batches of 500.

Please note that if something happens during this stock counting journal process and not all the lines have been added to the stock counting journal in the Site Manager the information still resides on the OMNI server and the process can be started again simply by adding one line to the same stock counting journal and the OMNI server will then start the background thread again. The process will pick up any remaining stock counting lines for the journal being updated regardless of when they were created.

Development notes

Please see a specific section in the development notes for changes