Digitec Galaxus continuously checks the received data for structural and technical correctness according to the defined parameters in this documentation. All error messages are sent back to the partner as an automated e-mail in English. The e-mail contains a detailed error description and possible solutions.
We report 2 types of errors back to our partner.
Import Error → These are structural errors in the file or major changes in the file size, which prevent a successful import on our side. We are thus unable to use the complete data until the error is fixed. Accordingly, these errors have a HIGH PRIORITY
.Validation Error → These are content errors in the file, which prevent us from processing individual data rows (records per ProviderKey) of the imported file. In most cases, a large part of the data can be used despite the error. Validation errors have a low priority.
We expect a direct solution of the errors. If you have any questions, please feel free to reply to the corresponding mail.
In the following the possible errors are presented as well as recommendations for action.
Following a list of all import problems which are communicated by us with German explanation.
In the mail several errors can be communicated at the same time. This can also concern several files/feeds.
| Expand | ||
|---|---|---|
| ||
File name/location: Price_DG_CH/StockData_Supplier.csv File content: Stock → Affected feed/file Error date: 2025-04-10 11:07:58 → ErrorDate Error type: Csv could not be parsed → Import Error Error message: → Description of import error Csv could not be parsed (at line #6877): The CSV appears to be corrupt near record '6889' field '2259 at position '2259'. possible resolution step(s): → Description Suggested solution Please check the structural integrity and the formatting of your file, to see if it follows our PDI 4.0 guideline.. |
Error Message | Import error in German | Suggested solution |
|---|---|---|
Csv could not be parsed (at line #xxx) | Csv could not be masked (at line #xxx) | We received a warning from our system that your file could not be parsed. Please check the structural integrity and formatting of your file to see if it meets our PDI 4.0 policy. For descriptions and product titles, it is especially important that they are enclosed in quotes as they may contain characters that also act as delimiters (semicolons, commas, pipes) and/or line breaks that, if unmasked, will prevent import. Below is an example of how to properly mask INCH characters from your product data to avoid parsing errors. longDescription_en: " TV with size 46"" and stand with white inscription ""Kings of E-Commerce"". Our Feedchecker app will show you in which line the parsing error occurred and give a description of the cause of the problem. If you have further questions, please contact the person in the CC of this email. Once the file is adjusted, the import of the data will continue. |
Current file size is ~xxKB and is ~xx% smaller than the previous one. (threshold: xx%) | Current file size is ~xxKB and is ~xx% smaller than the previous one. (threshold: xx%) | We have received a warning from our system that your file has significantly decreased in size. We are sending you this notification email to see if this is intentional or not. If it is indeed an error, we ask that you restore the file to its original size If it is not and the change was intentional, please contact the person in the CC of the email. Once the file is resized, the import of the data will run by itself. |
The following configured headers (columns) are missing in file: [Name:header/Index:ColNo.], ... | The following configured headers (columns) are missing in file: [Name:header/Index:ColNo.], ... | We have received a warning from our system that the column headers of your feed are missing in the last scanned version of the file. Please check if you:
If you have intentionally changed the file, please let us know by contacting the person in the CC of the email so we can adjust the change in our system as well. Please do not attempt to make such changes to your files, as any changes will cause the import of the data to stop and we will not have the latest data on your products. Once the file is adjusted, the data import will continue. |
This file is not sorted by provider key | This file is not sorted by provider key | We have received a warning from our system that the specification file is not sorted by ProviderKey. Please check the file and make sure that it is sorted by ProviderKey. Also check if there are duplicate ProviderKeys in the file itself. If so, remove them from the SpecificationFile. Once the file is adjusted, the import of the data will continue. If you have any further questions, please contact the person in the CC of the e-mail. |
The file is missing columns: SpecificationKey, SpecificationValue, ProviderKey. | The file is missing columns: SpecificationKey, SpecificationValue, ProviderKey. | We have received a warning from our system that the columns in the specification file are not named according to our guide. Please check the column header(s) and enter the following names for the columns: ProviderKey, SpecificationKey, SpecificationValue All information about the specification file can be found in File Format. Once the file is customized, the import of the data will continue. If you have any further questions about this error, please contact the person mentioned in the mail. |
File could not be read as xml! | File could not be read as xml! | We have received a warning from our system that the XML file cannot be read. Please check the file for structure and character errors and adjust the file. Let us know as soon as the file is adjusted so that we can adjust it in our system as well and proceed with the import. Once the file is adjusted, the import of the data will continue. |
Can not read Excel file! | Excel file cannot be read! | We have received a warning from our system that your Excel file cannot be read. Please check the following points:
You can find all information about the data format in our PDI 4.0 guide. Once the file is adjusted, the import of the data will continue. If you have further questions about the error, please contact the person in the CC of the e-mail. |
FileNotFound | FileNotFound | We have received a warning from our system that your file cannot be found. Please check if your current file is available on the FTP server. If you have changed the name of the file, please change it back according to our PDI 4.0 guide. Once the file is adjusted, the import of the data will continue. If you have any further questions about the error, please contact the person listed in the CC of the email. |
FileSizeZero | FileSizeZero | We have received a warning from our system that the size of your file is zero. Please check if the latest version of your file is available on the FTP server and if it is not empty. Once everything is adjusted, the import of the data will continue. If you have any further questions about the error, please contact the person listed in the CC of the e-mail. |
AccessDenied | AccessDenied | We have received a warning from our system that access to your file has been denied. Please check if our IP address has been blacklisted on your end: 35.189.218.3. If so, please whitelist again. If you have further questions about the error, please contact the person in the CC of the email. |
EndpointNotAvailable: This user is not allowed to connect from this IP | EndpointNotAvailable: This user is not allowed to connect from this IP | We have received a warning from our system that access to your file has been denied. Please check if our IP address has been blacklisted on your end: 35.189.218.3. If yes, please whitelist again. If you have further questions about the error, please contact the person in the CC of the email. |
File contains duplicated headers | File contains duplicated headers | We have received a warning from our system that the current version of your file contains duplicate headers. Please check the file and remove or correct all duplicate headers. Once everything is adjusted, the import of the data will continue. If you have any further questions about the error, please contact the person listed in the CC of the e-mail. |
Below is a list of all validation issues we communicate with German explanation. Each validation error refers to an article number. Accordingly, several errors can be communicated at the same time. You can see them in the exact list in the attachment of the mail.
| Expand | |
|---|---|
|
|
| |
 |
Error message (Description) | Possible cause of error | Possible solution | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ProviderKey appears multiple times in file!
| There are several identical rows in the file. These rows have identical provider keys and identical product data; pricing data; stock data and media data.
| Please check both the validation log and your file. As soon as you found the duplicate ProviderKey (your item no.) in your file, please remove the whole line(s), so that you are left with unique lines with unique ProviderKey's only.
| |||||||||||||||
There are several rows in the file, which have identical provider keys, albeit with different pricing data, stock data, product data or media data
| Please check the validation log thoroughly and look for the mentioned duplicate ProviderKey (your Art-No.) in the affected rows. Then check if the supplied data is correct and if it is possible to give each row a unique ProviderKey. If this is not possible, please remove all the lines with the duplicate ProviderKey until you can use the data. If you fail to do this, our system might create incorrect quotes or prevent it from creating products.
| ||||||||||||||||
Found 0 () mapped provider keys, could not create a Dg. ImportContext. Domain. CustomInterface. LineMapping. MappedCustomInterfaceLine
| The provider key is present in the file, but you are still getting this error message. Other data is also present alongside the provider key.
| This error usually occurs when a letter/symbol in the ProviderKey is not in ASCII format 32-126. As a result, our system cannot validate the value of the provider key and therefore returns a validation error for the entire line. Some examples of characters that are not allowed: Umlauts - ä, ö, ü, letters like š, ø, ñ or Cyrillic, Chinese, Japanese, Arabic script and similar. This can also happen if the maximum allowed number of characters (max. 100 characters) for the ProviderKey is exceeded. You can use this free online tool for counting characters tool: | |||||||||||||||
The affected rows have no provider key, but instead, they are notes, comments, intentional or accidental empty rows due formatting errors or design choices (in excel, csv)
| This error occurs when the file accidentally or intentionally contains blank rows, or rows that are comments, notes or formatting errors. Please check the whole file and remove all hidden rows, comments, notes and please fix formatting problems like hidden rows in Excel or similar. The hidden rows in Excel sometimes become import errors when the Excel file is converted to a CSV file, as the hidden rows can ruin that of the file. | ||||||||||||||||
The provider key is indeed missing, but other data is present
| Please enter the missing ProviderKey in the affected line or delete the line until you have a ProviderKey ready to use. | ||||||||||||||||
No values except ProvideyKey provided
| The affected row has only a provider key, while other data is missing.
| Please fill in the rest of the missing data or remove the whole row if there is no other data. Other data besides the ProviderKey can be added. | |||||||||||||||
The affected row has a provider key and other data alongside the provider key, but the error message still appears
| This validation error usually occurs when additional data beside the provider key is ignored by our validation and only the provider key remains as valid data in the whole row. The file usually has only 2 or 3 columns per row. Please note that depending on the attribute different values are accepted like integer, decimal or boolean's.
| ||||||||||||||||
CannotConstruct TypedSpecificationLine without a de key. (Key-Value Specifications File)
| The specification key is missing in the affected row.
| If you have rows that do not have specification keys (and/or specification values), please fill in the keys or remove these rows from the file as they cause validation errors.
| |||||||||||||||
Specification key is present in the affected row, but it is not listed under the German specification key column.
| If you already provide the correct data in a specification file with multiple language variants of specification key and values, but under the wrong column headings (under a specification key for a language other than German), please correct the specification key headings or list the specifications under the German specification key and value column if they are indeed German. If there is no German Key-Value specification pair, adding the German equivalent would be a great addition to the data quality of a product. | ||||||||||||||||
Cannot construct TypedSpecificatio nLine without a value. (Key-Value Specifications file)
| The affected row has a provider key and a specification key, but the specification value is left blank.
| Please add a property value to the corresponding column or remove the row if no property value should be added. | |||||||||||||||
The specification value is present alongside the provider key and the specification key, but you are still getting this error message.
| Please check if the specification value (property value) has more than 200 characters. If yes, please truncate the value, otherwise it will be ignored. Please also check if the specification value contains HTML tags. If yes, please remove them as HTML tags as the value will be ignored otherwise. You can use this free online character counting tool: | ||||||||||||||||
Missing columns: ProviderKey(Key-Value Specifications file)
| The provider key is missing, but the specification keys and specification values are present
| Please either fill in the missing ProviderKey or remove the whole line if this is not possible. not possible. | |||||||||||||||
The provider key is present in the file, however, you still get the validation error message
| This error usually occurs when a letter/symbol in the ProviderKey is not in ASCII format 32-126. Therefore our system cannot validate the value of the provider key and returns a validation error for the whole line. Some examples of characters that are not allowed: Umlauts - ä, ö, ü, letters like š, ø, ñ or Cyrillic, Chinese, Japanese, Arabic script and similar. This can also happen if the maximum allowed number of characters (max. 100 characters) for the ProviderKey is exceeded. You can use this free online tool for counting characters tool: | ||||||||||||||||
Missing provider key. (In a column variant specification file)
| This error happens in a column variant specification file, which is missing the provider key.
| Please remove the entire row or add the missing ProviderKey if some of the information is present. |