> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/utilities/import-masters-transactions-from-external-files/import-purchase-vouchers-from-external-file/import-purchase-vouchers-configuration/ignore-column-caption-first-row-in-file.md).
# Ignore Column Caption (First Row in File)
**YouTube:** [How to Ignore the Header Row in Import PUV Configuration?](https://youtu.be/Ui8qOxzXZuE)
## How to Ignore the Header Row in Import PUV Configuration?
In this tutorial, we will learn how to use the **"Ignore Column Caption (First Row in File)"** option while importing a Purchase Voucher from an external file in Logic ERP.
This option allows the system to ignore the column headings in the first row of the external file and begin importing the purchase data from the following row.
***
### Access to the Import Configuration
To access the required option:
* Navigate to **Import Purchase Vouchers from External File**.
* Open the **Configuration** window.
* Locate the option labeled as:
> **"Ignore Column Caption (First Row in File)"**
Before enabling this option, let's first understand its default behavior.
***
### Review the Purchase File
* Before importing the document, let's review the purchase file.
* As you can see, the **first row contains the column headings** that identify the different fields in the file.
Now, let's import the file while **"Ignore Column Caption (First Row in File)"** is disabled.
***
### Import with the Option Disabled
* Keep **"Ignore Column Caption (First Row in File)"** disabled.
* Proceed with importing the Purchase Excel file.
**System Behavior**
Since the option is disabled, the system considers the **first row, including the column headings, as part of the purchase data** during the import process.
This means the system attempts to process the first row along with the actual purchase details.
***
### Let's Enable Ignore Column Caption
Now, let's enable the option and observe the difference.
* Return to the **Configuration** window.
* Enable **"Ignore Column Caption (First Row in File)"**.
* Save the configuration changes.
* Import the **same purchase file** again.
**System Behavior**
As you can see, the system now **ignores the first row containing the column headings**.
The import process starts from the **next row**, which contains the actual purchase details.
***
### Verify the Imported Purchase Voucher
Now, let's proceed with importing the document.
* Complete the import process.
* Open the **Purchase Voucher** module.
* Open the imported Purchase Voucher.
* Verify the imported purchase details.
**Result**
As you can see, the purchase details have been successfully reflected in the **Purchase Voucher**, while the first row containing the column headings has been excluded from the imported data.
***
### Final Outcome
By enabling **"Ignore Column Caption (First Row in File)"**, Logic ERP skips the header row of the external file and starts importing the purchase data from the next row. This is useful when the first row of the file contains column headings rather than actual purchase data.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/utilities/import-masters-transactions-from-external-files/import-purchase-vouchers-from-external-file/import-purchase-vouchers-configuration/ignore-column-caption-first-row-in-file.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
