This version was released in August 2021 and includes the following improvements and bug fixes.
LSTS-16187: Update fail for Extension tables
Update records in extension tables caused records to be skipped instead of updated.
LSTS-16262: Remote update fix
Remote update Data Director used wrong parameters for updating Central Add-ins files. Add option to update DD Web Service.
LSTS-15492: Ignore unpublished Central app tables
Ignore all tables for Central App Extensions that have been unpublished.
LSTS-15492: Non Unicode parameter values in Linked table
Unicode data used to map linked tables caused failure in Linked table look up.
LSBS-416: Web Service replication
Fix Insert issue and DateTime look up in query.
LSTS-16226: Missing file in LS One Scheduler
Missing System.Memory error when running normal job from LS One.
CEN-6877: Jobs ignore default Compression and ISO mode settings
There was bug in LS Central Scheduler codeunit where it did not handle default modes for Compression and ISO Mode. This fix needs also codeunit from 18.3.
CEN-6877: Web Service Filter error
Web Service Replication with filter gave error or ignored the filter.
Return address when source is localhost
If Source host name was set as localhost, the job got stuck at source host with status None as destination host could not send back any result messages due to unknown return host.
Configuration Tool crashes when open Queues
Pressing Queue or Global Queue button cause Configuration tool to hang or crash.
Unicode Data when replicate from Nav 2009 to Central
Data replication from older LS Nav system and cfront that do not support Unicode data to newer LS Central system using Unicode cause data to appear as random text.
Identity field as primary key fails with Extension Tables
ERROR: Table xxx does not have the identity property. Cannot perform SET operation.
If Identity field is used as primary key, it caused error when updating extension tables, as the field is not marked as Identity field in the Extension tables.
Action Delete job deleted all records at destination
When sending Action job with delete actions, it caused all records to be deleted at destination.