TP Rel. 3.0 Tech part & Payment Request

How can I identify my co. data has some data exceptions after loading

• The hint *(e) Data exceptions exist" is visible from Gateway of TallyScreen
• The hint is to re-perform the actions of migration, repair, import & Synchronise of Data in TP Rel. 3.0 to know the data exceptions
• The hint is to check respective error log files and event log report

How can I resolve my co. data exceptions after loading

• Through Alt Y Data - All Exceptions
• Through migration, repair, import & Synchronise Data error summary report while performing this actions in TP Rel. 3.0
• Through F1 Help Troubleshooting Repair, migrate, Repair/Migration Exceptions

The Data exceptions are of

• Master- Related Exceptions
• Voucher Related- Exceptions
• Report Related- Exceptions

what happens if I don't resolve Data exceptions

• Vouchers and masters that are part of the exceptions report do not participate in your financial reports and Books of Account, until they are resolved.
• Vouchers and masters that are part of the exceptions reportwill participate in your financial reports and Books of Account, irrespective of resolving the data exceptions

In case Tally gets closed in the mid of the migration process then what happens and what has to be done?

• Once you open TP Rel. 3.0 application, company status shows as continue migration means it was in the process of migration & due to some unforeseen circumstances, it was stopped, but now you can continue migrating again.
• You must start the migration from the beginning and wait till it is completed
• It aborts the migration process and cannot use the data

How to configure TP Beta Rel. 3.0 license as I have a license running in TP Rel. 2.1

• Open TP Beta Rel. 3.0 and select the license configuration option "Use license from Network" this will point to TP Rel. 2.1 license
• Need to reactivate TP Rel. 3.0 after installing in a separate folder
• Need to work on TP Beta Rel. 3.0 in education mode till we do Gold release

On migrating my TP Rel. 2.1 data to TP Beta Rel. 3.0 I am not able to see nor access my original data of TP Rel.2.1

• On migrating TP Rel. 2.1 data to TP Beta Rel. 3.0 the co. data folder of TP Rel. 2.1 will be renamed to e.g. 10009-migrated-to-3.0 to access the same in TP Rel. 2.1 must rename as 10009
• Nothing to worry higher version or lower version data are made compatible in TP 3.0 to TP.2.0 and vice versa i.e. you can access the same data in both versions.
• As this is a beta version and it is a WIP product once you migrate earlier Rel. data it will remove the original data. We recommend to take a backup before migration

On migrating my TP Rel. 2.1 data to TP Beta Rel. 3.0 I see the co. data folder is increased from 5 digit to 6digit

• As TP Rel.3.0 carries various new capabilities to make earlier release data compatible there is a need of data file structure change.
• As TP Rel.3.0 carries various new capabilities to make earlier release data compatible there are chances of data files getting corrupted or deleted
• As TP Rel.3.0 carries various new capabilities and not make earlier release data compatible there is a need to change data file structure

Can the user roll back his data migrated to Rel. 3.0 to the older version of the TallyPrime?

• No, users cannot roll back on to an older release since we have migrated onto a 6-digit company data, which can be used from TP 3.0 onwards. The existing 5-digit company will remain as it is with a rename of migrated to 3.0.
• Yes, users can as same data can be accessible in both the releases

Data File extensions in TP Rel. 3.0

• .500 and TSM
• .600 and TSM
• . 900 and TSF
• . 1800 and TSF