> 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/universal-import/universalimport_en_us/troubleshooting-and-support/faq.md). # FAQ ### File upload
“Please select a mapping first” Before you can upload a file, an import mapping must be selected. First select the appropriate mapping from the list, then upload the file again.
“The file does not match the mapping type” The file type of your file does not match the format defined in the mapping. For example, you uploaded a CSV file, but the mapping was created for Excel. Create a mapping for the actual format or select the appropriate existing mapping.
“No Excel file found” The uploaded file could not be read as a valid Excel file. Check whether it is actually a supported Excel format, such as `.xlsx`, whether the file is corrupted, and whether you have not accidentally selected a different file extension.
### Column mapping
“No columns mapped” No file columns have been mapped to the target fields in Business Central yet. Upload a file and assign a target field to each relevant column before continuing with the preview or import.
“Only X of Y columns mapped” This is an **informational message**: Not all columns from the file have been assigned to a mapping. You can continue; however, data from unmapped columns will not be imported. Add the missing mappings if all columns should be imported.
Columns are displayed, but target fields are missing Check whether the **correct target** table has been selected in the mapping. Only fields from the selected table are available as targets. Change the target table if you want to import into a different table.
### Import errors
“The record already exists” You are probably using “Insert Only” mode while the record already exists in Business Central. If existing records should be updated, switch to “Insert & Update” mode. See also Import Modes.
“The enum element does not contain the value X” This error may occur if option or enum values are corrupted or invalid. This issue was fixed in an earlier app version. Make sure that your environment is using the latest version of the extension, and then run the import again.
Fields are empty after the import Check the “Validate fields” setting: If it is disabled, dependent fields are not filled automatically. In addition, the “If empty” option applies per column — depending on the setting, empty source values may either skip or clear existing values. See Field Validation and Empty Values.
“Asset Type must have a value” or similar required-field errors This is often caused by a field dependency: required fields such as source type or asset type must be populated before the regular file columns are processed. Use virtual columns for these fields — virtual columns are automatically processed **before** the columns from the file. For more information, see Virtual Columns.
“The correct row is not found in the target table.” In the *“Select Target Table”* window, a filter is set by default to display the most commonly used entries. To display all entries, click the arrow to the right of *“Table ID”* and select *“Clear Filter*” from the drop-down menu that opens.
### Decimal numbers & formatting
Prices or amounts are displayed incorrectly Check the decimal separator for each column: German files often use a comma (`1.234,56`), while US files use a period (`1,234.56`). The setting must match the format of your source file. See Decimal Separators.
Thousands separators cause errors Set the correct decimal separator. Thousands separators are usually removed automatically, provided that the decimal separator clearly matches the file format.
### Quick Import
“No matching template found” No matching import mapping was found for the column headings in your file. Create the mapping manually once and save it; Quick Import can then recognize the same structure in future files with similar headers. See Quick Import.
“Multiple templates found” Multiple mappings meet the detection criteria. A list is displayed for selection — choose the appropriate mapping. More precise names for your mappings will make it easier to keep track of them later.
Quick Import detects the wrong mapping or no mapping at all Automatic mapping is based on a threshold: at least approximately 50% of the mapped columns must match the file. If the column names in your file differ significantly, detection will fail. In this case, select the mapping manually or adjust the column names.
### Item attributes
Attribute values are not mapped Check whether “Use alias” is enabled in the mapping line. If your file uses different names than the attribute values in Business Central, set up aliases on the Item Attribute Values page. For details, see Item Attributes.
--- # 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/universal-import/universalimport_en_us/troubleshooting-and-support/faq.md?ask=&goal= ``` `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.