Import Data – Errors & Resolutions
This page lists errors and exceptions related to importing data in TallyPrime.
Cause: Error message in case Import from Row starting value is greater than value after to
Solution:
- Press Alt+O (Import) > Manage > Mapping Templates > Masters or Transactions > Alter, and select the template to alter.
- In the Import data from row and to fields:
- Ensure to enter whole numbers
- Ensure that the value in the to field is greater than or equal to the value in Import data from row field.
Cause: Error message in case Import from Columns starting value is greater than value after to.
Solution:
- Press Alt+O (Import) > Manage > Mapping Templates > Masters or Transactions > Alter, and select the template to alter.
- Ensure that the value in the to field is greater than or equal to the value in Import data from row field.
Cause: Error message in case User comes back to row no for column headers and specifies value greater than import data from row.
Solution:
- Press Alt+O (Import) > Manage > Mapping Templates > Masters or Transactions > Alter, and select the template to alter.
- Ensure that the value in the Row no. for column headers field is lesser than the value in the Import data from row field.
Cause: Error message in case the value for Import data from row is given as lesser than the Row no for column headers.
Solution:
- Press Alt+O (Import) > Manage > Mapping Templates > Masters or Transactions > Alter, and select the template to alter.
- Ensure that the value in the Import data from row field is greater than the value in the Row no. for column headers field.
Cause: Error message if Excel File cannot be read.
Solution: Select a valid Excel file and try again.
Cause: Excel application is missing in the User’s system.
Solution:
Install the application or check the extension of the file.
Cause: When the destination file is already opened in the User’s system, or the location given is inaccessible.
Solution: Check the location or whether the file is open in the system.
Cause: Failed to Construct Map before import.
Solution:
Check the existing Map File or the mapping of Tally fields to the Excel columns.
Check the Event Log to know the reason for errors.
Cause: Missing structure in the map (maybe a missing field). *What is missing will be displayed in the calculator panel.
Solution: Check the mapping.
Cause:
Any one of these two “Unique On” is missing.
- Unique On row
- Unique On column.
Solution: Check the mapping.
Cause: When the entire mapping template is empty.
Solution: Enter the details and map the Tally fields to the Excel columns.
Cause: User has entered the end column number greater than max limit.
Solution: Enter a value from A to ZZ and try again.
Cause: When start row/column is greater than end row/column.
Solution: Enter a value for start row/column lower than end row/column.
Cause: Disc memory is missing to store the file into the system.
Solution: Restart TallyPrime or clear the space in your system.
Cause: Unable to open the given file.
Solution: Select a valid file and try again.
Cause: Invalid Excel Sheet Name.
Solution: Select a valid Worksheet Name and try again.
Cause: Unable to set active sheet.
Solution: Ensure that the file exists on the selected folder path and has the read permission enabled.
Unable to save the mapping template, as one or more fields are not mapped correctly in the template.
Cause: User has provided wrong Tally field to Excel Column mapping.
Solution: Ensure that the mapping is correct and save again.
Master-Related Exceptions
This section lists master-related exceptions that might occur when you perform import, migration, and repair of your company data, in TallyPrime Release 3.0 and later.
To resolve this issue, perform the following:
- Drill down from the exception. Press Enter twice.
- Select the exception and update the Parent Group.
- Press Multi-Alter. Alternatively, press Update Details.
- Select the Parent Group, for example Sundry Debtor, and save.
The exception is resolved.
To resolve this issue, perform the following.
- Drill down from the exception. Press Enter twice.
- Press Alt+H (Multi-Alter) > select the required Attendance Type and Unit where applicable.
- Enter Y or press Ctrl+A to save.
The exception is resolved.
To resolve this issue, perform the following:
- Drill down from the exception to open the Pay Head LAteration (Secondary) screen.
- Select a valid Production Type from the List of Production Types.
- Press Enter or Ctrl+A to save.
The exception is resolved.
To resolve this issue, perform the following:
- Drill down from the exception. Press Enter twice.
- Select the exception and update the Unit.
- Press Alt+H (Multi-Alter).
- Alter or update the Unit from the list of Units, and save.
The exception is resolved.
To resolve this exception, perform the following:
- Drill down from the exception to open the Budget Alteration screen.
Note that the From date is later than the To date.
- Update the From date or To date, as needed. Ensure that the From date is earlier than the To date.
- As always, press Ctrl+A to save the master.
The exception is resolved.
To resolve this exception, perform the following:
- Drill down from the exception to open the Budget Alteration screen.
Note that the From date and To date are empty.
- Update the From date or To date, as needed. Ensure that the From date is earlier than the To date.
- As always, press Ctrl+A to save the master.
The exception is resolved.
To resolve this exception, perform the following:
- Drill down from the exception. Press Enter twice.
Note that the Formal Name contains invalid characters.
- Press Alt+H (Multi Alter) to edit the Formal Name field.
- Update the Formal Name with a valid value, for example Rupees, Dollar, or so on.
- Press Enter or Ctrl+A to save.
This exception is resolved.
To resolve this exception, perform the following:
- Drill down from the exception to the Voucher Type Alteration (Secondary) screen.
- Enter a valid Name and save the voucher type.
This exception is resolved.
To resolve this exception, perform the following:
- Drill down from the exception. Press Enter twice.
Note that the Symbol and the Formal Name are the same.
- Press Alt+H (Multi Alter) to update the Formal Name, and press Enter.
Press Backspace to update the Symbol, if needed.
- Press Enter or Ctrl+A to save.
This exception is resolved.
To resolve this exception, perform the following:
- Drill down from the exception to the Ledger Alteration (Secondary) screen.
- Click on the Opening Balance Dr field and press Enter.
The Bill-wise breakup sub-form opens. - Modify the Date as required and save.
This exception is resolved.
To resolve this exception, perform the following:
- Drill down from the exception. Press Enter twice.
- Press Alt+H (Multi Alter) to update the Parent Group.
- Select the appropriate Parent Group from the List of Employee Groups.
- Press Enter or Ctrl+A to save.
This exception is resolved.
To resolve this exception, perform the following:
- Drill down from the exception to open the Unit Creation screen.
- Enter the correct Unit details.
- Press Enter or Ctrl+A to save.
This exception is resolved.
To resolve this issue, perform the following:
- Drill down from the exception. Press Enter twice.
- Select the exception and update the conversion factor of the compound unit.
- Press Alt+H (Multi Alter).
- Update the conversion factor.
- Press Ctrl+A to save the master.
The exception is resolved.
To resolve this issue, perform the following:
- Drill down from the exception and accept the query as given below.
The exception is resolved.
To resolve this exception, perform the following:
- Drill down from the exception to go to the Attendance/Production Type Alteration (Secondary) screen.
- Change the Name to ensure that the name of the master and aliases (one or multiple) used are all unique.
- Press Enter or Ctrl+A to save the master.
This exception is resolved.
To resolve this issue, perform the following:
- Drill down from the exception. Press Enter twice.
- Select the exception and update the name of the master.
- Press Alt+H (Multi Alter).
- Update the Name of the master.
- Press Enter or Ctrl+A to save the master.
This exception is resolved.
To resolve this issue, perform the following:
- Drill down from the exception. Press Enter twice.
- Select the exception and update the number of decimal places.
- Press Alt+H (Multi Alter).
- Update the Number of decimal places to less than or equal to 4.
- Press Enter or Ctrl+A to save the master.
This exception is resolved.
To resolve this issue, perform the following:
- Drill down from the exception. Press Enter twice.
- Select the exception and update the Master’s Name.
- Press Alt+H (Multi Alter).
- Enter the Master’s Name, and save.
- Press Ctrl+A to save.
The exception is resolved.
Voucher-Related Exceptions
This section lists voucher-related exceptions that might occur when you perform import, migration, and repair of your company data, in TallyPrime Release 3.0 and later.
To resolve this exception, perform the following:
- Drill down from the exception to open the Payment voucher.
- Continue to press Enter in the voucher to open the Bank Allocations screen.
- Update the Cheque Range and the Instr No. and save.
- Ensure that the Instr No. is updated as per the Cheque Range provided.
- Ensure that the Instr No. is updated as per the Cheque Range provided.
- As always, press Ctrl+A to save the voucher.
This exception is resolved.
To resolve this issue, perform the following:
- Drill down from the exception to open the voucher.
- Update the voucher with the missing inventory or accounting entries.
- Press Ctrl+A to save.
The exception is resolved.
To resolve this issue, perform the following:
- Drill down from the exception to open the voucher.
- Select the item and press Enter.
Item Allocations for: screen opens.
- Enter the Due on date as required and save the screen.
- Press Ctrl+A to save the voucher.
The exception is resolved.
To resolve this issue, perform the following:
- Drill down from the exception to open the voucher alteration screen.
- Select the final Amount of the voucher and press Enter.
The Bank Allocations for: screen opens.
- Select the correct ledger under Ledger Name and save the screen.
- Press Ctrl+A to save the voucher.
The exception is resolved.
