> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/datanorm-item-import/datanorm_en_us/operations-and-troubleshooting/faq.md).

# FAQ

## Import

<details>

<summary>Do I have to set the DATANORM version before importing?</summary>

No. The version is detected from the file's header record. The **Default DATANORM Version** setting only applies to export.

</details>

<details>

<summary>In what order should I import the files of a delivery?</summary>

`.WRG` and `.RAB` (groups) first, then `DATANORM.001` and any follow-up files, and `DATPREIS.001` last. See [Import Process](/datanorm-item-import/datanorm_en_us/importing-datanorm-files/import-process.md).

</details>

<details>

<summary>Can I import the same catalogue more than once?</summary>

Yes. Set **Duplicate Handling** to **Update** and existing items are overwritten rather than duplicated.

</details>

<details>

<summary>How large can a file be?</summary>

Catalogues with several thousand articles are normal. Above the **Background Threshold** the app processes the file in the background.

</details>

<details>

<summary>Does importing change my item master straight away?</summary>

No. The data lands in staging first. Only synchronisation writes items – unless you enabled **Auto-Sync to Items**.

</details>

## Vendor

<details>

<summary>How do I assign an import to a specific vendor?</summary>

A vendor selection dialog appears on manual import. Afterwards, use **Assign Vendor** on the import session. See [Manual Import and Vendor Assignment](/datanorm-item-import/datanorm_en_us/importing-datanorm-files/manual-import.md).

</details>

<details>

<summary>Why does an SFTP import land on the default vendor?</summary>

Because nobody can confirm a dialog during automatic collection. Correct the assignment on the import session.

</details>

<details>

<summary>Two suppliers use the same article numbers. What now?</summary>

Leave **Match Duplicates per Vendor** enabled. The app then only compares within the same vendor.

</details>

## Duplicates

<details>

<summary>Why are so many articles reported as duplicates?</summary>

Usually the file has already been imported, or an older session is sitting unsynchronised in staging and is being checked too. See [Duplicates and Validation](/datanorm-item-import/datanorm_en_us/importing-datanorm-files/duplicates-and-validation.md).

</details>

<details>

<summary>With DATANORM 4 I expected twice as many rows. Is something missing?</summary>

No. The A and B record of an article are merged into one record. The **Merged Source Records** field shows the number of source lines.

</details>

## Prices

<details>

<summary>Where does the app write purchase prices?</summary>

Into a DATANORM purchase price list for the relevant vendor, for example `DN-PUR-10000`. That way standard purchase price calculation applies.

</details>

<details>

<summary>Why were no price lines written?</summary>

Usually the articles are not synchronised yet, or the selected price source holds no value. See [Purchase Price Lists](/datanorm-item-import/datanorm_en_us/prices/purchase-price-lists.md).

</details>

<details>

<summary>Are sales prices calculated automatically?</summary>

No. The app can take the list price as a sales price but applies no mark-up. See [Sales Prices and Discount Groups](/datanorm-item-import/datanorm_en_us/prices/sales-prices-and-discount-groups.md).

</details>

<details>

<summary>Why do all discount groups show 0%?</summary>

Because the supplier does not include the discounts in the file. That is common and not an import error.

</details>

## Part lists

<details>

<summary>What kind of BOM is created?</summary>

An assembly BOM on the set item. Production BOMs are not created.

</details>

<details>

<summary>Why were lines skipped?</summary>

No item exists for the component, or it is an optional line while **Include Optional Set Lines** is off. Synchronise the items and run **Build Part Lists** again.

</details>

<details>

<summary>Do my own changes to a DATANORM BOM survive?</summary>

No. A repeat import replaces the BOM entirely, because DATANORM always delivers sets in full. Keep bundles of your own on a separate item.

</details>

## Operations

<details>

<summary>Do I need the Azure Function?</summary>

Only for SFTP import. Manual import works without it.

</details>

<details>

<summary>What happens when the licence expires?</summary>

For an installation from AppSource the term follows your subscription there. Only trial and sandbox builds handed over directly carry a fixed expiry date; once it has passed, import and synchronisation stop with a message. Data already imported stays intact.

</details>

<details>

<summary>Can I undo an import?</summary>

Not automatically. That is why you review in staging before approving, and trial new supplier files in a sandbox.

</details>

<details>

<summary>How do I verify that the app is configured correctly?</summary>

Run the built-in tests, see [Built-in Tests](/datanorm-item-import/datanorm_en_us/operations-and-troubleshooting/built-in-tests.md).

</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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.solutioo.de/datanorm-item-import/datanorm_en_us/operations-and-troubleshooting/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.