Synchronisation

51887

• The name of the client company was not being displayed in Tally.imp file, resolved: When the name of the client company was created in Arabic, the same was not being displayed in the Synchronising data From line of Tally.imp file. The name of the company was being displayed as ??????.

  Now, the name of the client company is displayed in Tally.imp file. The Tally.imp file is created with complete details when the option Enable Detailed log(tally.imp) is enabled in Advanced Configuration screen. This file will be created at both client and server end.

63823

• Tally clock was stopping after synchronisation, resolved: Tally clock stopped working at the server end after synchronisation due to which the time at client and server were differing.

  The Tally clock will now run continuously, and not stop after synchronisation in server machines.

32118

• A provision is made to synchronise masters that have no transactions: An option has been provided while creating sync rule, to synchronise masters that do not have transactions.

68616

• Cheque reused in server was not getting synchronised to client, resolved: When a cancelled transaction is synchronised from client to server, the respective cheque if reused at server was not being synchronised back to client.

  Now, elements from cancelled transactions can be reused and synced.

52206

• Bank ledgers having only opening balance or opening BRS were not being transferred from client to server during synchronisation, resolved: During synchronisation from client to server, the bank masters with only opening balances or opening BRS defined, and not having any transactions, were not being transferred.

  Now, bank ledgers with opening balance, opening BRS, and with unreconciled transactions in Opening Bank Allocation, will be updated during synchronisation.

49744

• An error message was being displayed at client, while synchronising data with server containing multiple currencies, resolved: When synchronising data from a server company containing multiple currencies to a client machine with single currency, the error message Currency Already Exists was being displayed at client end. This occurred when the foreign currency in the server company was the base currency in client company.

  Now, synchronisation between server companies with multiple currencies and client companies has been handled to recognise the appropriate currency during synchronisation.

59482

• Cancelled Voucher was not getting synchronised, resolved: If a voucher was created with the option Synchronise after save enabled, and if this voucher was cancelled later, the cancelled voucher was not getting synchronized immediately. It had to be synchronised manually.

  Now, as soon as the voucher is cancelled, it is synchronised.

See also: