Offline DB may not always have the same requirements as the channel DB.

Currently the two are interlinked and it is difficult for an ISV to add and control their content for the offline scenario.

This will also impact bandwidth usage for a store given the same packages are synchronized to the RSSU & any offline terminal.

The ability to separate out the schema from the channel DB to limit what is synchronized to an offline DB is beneficial and will reduce load on the CDX process.



Ideas Administrator

Functionality now exists to select jobs and sub-jobs to be excluded from the offline DB.  Further, with usage of separate Channel database groups, entire packages can be reduced or even removed.



Hi Warren, the main issue to make databases different can be standard POS logic - Microsoft POS does not have separate logic for channel and offline DB - so what will happen, if you remove some important configuration data from there?

Category: Data management and synchronization