Importing Template

Once the data has been added to the downloaded template, the following steps are followed:

After updating your template file, go back to the Data Import form and attach the file by clicking on the Attach button. Attaching file for import
Select the template file and click on Upload.
After the upload is successful, click on Start Import.
Once the Sheet is uploaded, the system validates the sheet and gives the result on screen before importing the data *Data import *
Various validation cases can occur once the data has been imported, such as:

Duplicate Name - In case we try to add a record with a duplicate name, it will throw an error like this

Duplicate Name Error

Mapping of columns missed: When we had added additional columns while downloading the template, or we have renamed a column in the template we are importing, it may throw an error about not being able to match the columns. Validation of matching columns

To resolve this, we can click on the map columns and manually map the columns to the corresponding columns in the Document.

If there are any errors in your template, they will be shown in the Warnings section. The warnings will be categorized by Row or Column with their number so that you can easily track them down in the template and resolve them. You must resolve all the warnings before you can import the data.
After you have resolved the warnings, click on Start Import again to import the data. On successful import of the data, you'll see a log of each record that was created in the Import Log section.

Importing child records

Data in ERPNext is stored in tables like a spreadsheet with columns and rows of data. Each form likes Sales Order, has multiple fields like Customer, Company, etc. It also has tables like the item table, tax table, etc. In Data Import, the set of fields in the Sales Order is treated as the main table, and the rows inside the child table (item table) are treated as the child table for data import.

Each form in ERPNext can have multiple child tables associated with it. The child tables are linked to the parent tables and are implemented where there are multiple values for any property. For example, an Item can have multiple prices, a Sales Invoice has multiple Items, Taxes, and so on.

When you export a document with child tables, for e.g., each child row will appear on a separate row, but it is associated with a single parent row. The subsequent values in the parent columns will remain blank. You must ensure that this order is not broken when you are importing it via Data Import.

Child records importing