Transaction Restore Cutoff Date Behavior in Store/Offline POS Database Backup

Transaction Restore Cutoff Date Behavior in Store/Offline POS Database Backup

Product Version: 

6.6

Product Query: 

Customers raised a query regarding 'Transaction Restore Cutoff Date' Behavior in Store/Offline POS Database Backup

Proposed Solution: 

The “Transaction Restore Cutoff Date” option available during New Store / Offline POS Database Backup generation is designed to include transaction data after the selected cutoff date in the generated Store backup.

Info
Transaction Cutoff Date : Enter the date after which the transactions will be restored at the selected store.

    • Related Articles

    • Offline POS

      Introduction The offline POS feature allows the terminal POS to function even if the connectivity between the terminal POS and the store server is interrupted. The Offline POS feature has to be enabled via the iVend Retail Management Console. Note: ...

    • Enable Offline POS

      Offline POS Introduction The Offline POS is related to a Store - in the same way as a Store is related to the Enterprise. This means that the replication dashboard if accessed from the On-premises Store will list all the offline POS terminals ...

    • Offline Terminal POS Data Sync with Store

      iVend Retail - Offline Terminal POS Data Synchronisation with the Store server This document describes the Offline Terminal POS feature and the data synchronisation with the Store Server. · This feature allows the Terminal POS to function even if the ...

    • Replication skipped from offline POS to the Store Database

      Product version: iVend 6.5 updates 6 with offline POS Problem Statement: Replication skipped from offline POS to the Store Database. Proposed Solution/Workaround: It was a known issue with a dated version on iVend using offline POS with replication ...

    • Problem In Store Database Backup Restore.

      Problem : Unable to Create Store Database from HO Management console. Script.xml is not created in the backup file. Reason : Earlier backups were corrupts because following SQL statement was throwing error as: Select A.* From InvSerial A ...