> 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-duplicate.md).
# Ignore Duplicate
**YouTube:** [How to Ignore Duplicate Item Rows in Import PUV Configuration?](https://youtu.be/tuJdWHhG-SE)
## How to Ignore Duplicate Item Rows in Import PUV Configuration?
In this tutorial, we will learn how to use the **"Ignore Duplicate"** feature while importing a Purchase Voucher from an external file in Logic ERP.
This feature allows the system to ignore duplicate item entries during the Purchase Voucher import process and consider only the first occurrence of the item.
***
### 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 Duplicate"**
Before enabling this option, let's first understand its default behavior.
***
### Review the Purchase Excel File
Before importing the document, let's review the Purchase Excel file.
As you can see, the file contains **duplicate entries for the same item**.
For example:
* First entry: **Quantity = 50**
* Duplicate entry: **Quantity = 20**
Now, let's import the Purchase Excel file while **"Ignore Duplicate"** is disabled.
***
### Import with Ignore Duplicate Disabled
* Keep **"Ignore Duplicate"** disabled.
* Proceed with importing the Purchase Excel file.
#### System Behavior
As you can see, since the **"Ignore Duplicate"** feature is disabled, the system considers both entries for the same item.
The quantities are added together:
**50 + 20 = 70**
Therefore, the final quantity for the item is **70**.
***
### Let's Enable Ignore Duplicate
Now, let's enable the feature and observe the difference.
* Return to the **Configuration** window.
* Enable **"Ignore Duplicate"**.
* Save the configuration changes.
* Import the **same Purchase Excel file** again.
#### System Behavior
* As you can see, after enabling **"Ignore Duplicate"**, the system ignores the duplicate item entry and considers only the **first occurrence** of the item from the Excel file.
* In this example, the system considers the original quantity of **50** and ignores the duplicate quantity of **20**.
***
### 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 item quantity.
#### Result
As you can see, the purchase details have been successfully reflected in the **Purchase Voucher**, with the duplicate item entry ignored.
The system considers only the first occurrence of the item, with a quantity of **50**.
***
#### Final Outcome
By enabling **"Ignore Duplicate"**, Logic ERP prevents duplicate item entries from being considered during Purchase Voucher import. This ensures that only the first occurrence of a duplicate item from the external file is included in the imported purchase details.
---
# 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-duplicate.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.
