The most common catalog upload errors

Images are not uploaded

Have you followed this instruction closely? Upload and assign images to catalog items

value must be a number with decimal separator represented by dot

change format of ArticlePrice in excel template to text

not every atricle is listed in CSE

Check the approval column, problems sometimes arise here when files are uploaded that already have an approval status -> set all to pending and upload again

the nameMapping array and the sourceList should be the same size (nameMapping length = 44, sourceList size = 3)

In your CSV file you have a different amount of header columns (nameMapping lenght) and the columns for your items (sourceList size). Maybe you have a seperator character too much or too few, So for one or more items you have a different amount of columns then the header columns are.

ERROR - NEW_BMECAT_CONVERTER ->WstxValidationException: Validation error, encountered element <FORDER> as a child of <FEATURE>: Expected <FVALUE> or <VARIANTS>
at [row,col {unknown-source}]: [22941,11] : null

Your BMECat has a problem in row/line 22941 and col/character 11. This error occurs, when a tag is missing or too much. This error message tells you, that the tag/element <FORDER> is wrong. The system needs the element <FVALUE> or <VARIANTS> instead of <FORDER> in this position/line.

ERROR - EvaluationException: EL1011E: Method call: Attempted to call method matches(java.lang.String) on null context object in product with SupplierAID: XXXXX

If your BMECat / Excel has some tags/ fields, which belong as a pack together, this error can occur, for example if you miss one of the four Mime parts.

File prepared for indexing has exceeded the maximum limitation of: 3000 MB. Please reduce the number of items or specify less details. Current file size is: 4159 MB.

Your content is to big for one catalogfile. Your file must not be larger than 3 GB. Please check if you can shorten your catalog.

ERROR - Invalid white space character (0x2) in text to output (in xml 1.1, could output as a character entity) in product with SupplierAID: XXXXXX
ERROR - Invalid white space character (0x1a) in text to output (in xml 1.1, could output as a character entity) in product with SupplierAID: XXXXXX

Please check your DescriptionShort or DescriptionLong. There is a white space character, so a character which is not visible but there. Copy your DescriptionLong text into an editor and then copy it back.
Please check under Mime.Source Link whether it is an unsuported character.

NEW_BMECAT_CONVERTER ->WstxValidationException: Attribute 'type': Invalid enumerated value '': has to be one of (buyer_specific, duns, iln, supplier_specific)

at [row,col {unknown-source}]: [XX,XX] :

BUYER_ID type cannot be empty. It needs to be filled out. Example:

<BUYER_ID type=”buyer_specific”>12345</BUYER_ID>

Wrong format. ArticlePriceDetails.ArticlePrice.1.PriceAmount in cell: AO is wrong. Value must be a number with decimal separator represented by dot

In cell ArticlePriceDetails.ArticlePrice.1.PriceAmount must the cell formated as text. It has to be just two number after (comma , or dot . ) for example (100,22 or 100.22 ). It has to be all values this cell either with a comma ( , ) or a dot ( . ).

ERROR - Exception: SAX parser appears to be broken -1

This parse_error can be found in the header of the Excel catalogue. Please use our template Excel (Header) as it is and don't change the language or add different new symbols.

ERROR - NEW_BMECAT_CONVERTER ->CharConversionException: Invalid UTF-8 middle byte 0x3c (at char #65787553, byte #66063930) : null

This parse_error means that the UTF-8 encoding does not work. To solve this problem, you need to download the catalog, open it with the notepad editor and then save it as .xml and select encoding: UTF-8.

ERROR - System could not process validation rule (id: 9100001684) in product with SupplierAID: ( )

This BMECat parse_error means that this Validation Rule ID: does not supported (\+","%2b) these characters in Mime Source link.

Missing target classification system: #NAME (this value depends on the customer settings)

In column Classification.n.ClassificationSystem you have to populate the value #NAME

ClassificationID error empty

Please fill in a correct ClassificationId from the ClassificationSystem #NAME (depends on the customer settings)

Code doesn't exist in classification: #NAME

Maybe you have used a wrong ClassificationId, which is not part of the classification #NAME. Please doublecheck on the ids.

Same SupplierAID exist in row: 123 for SupplierID: 123123

Do not use duplicate SupplierAIDs in your catalog

ValidEndDate in history

Issue can be a false date spelling. Our system support YYYY-MM-DD (e.g. 2021-12-31)

QuantityMin valid error

ArticleOrderDetails.QuantityMin must not be less than ArticlePriceDetails.ArticlePrice.1.LowerBound!

Related product doesn't exist

in german: "Zusatzartikel existiert nicht"

Download the relation log from your catalog. This will give you information of which articles haven`t been assigned properly to a related product. Download the catalog file from your catalog. Search in Column SupplierAID if you can find misspelled articles. The SupplierAID has to exactly match the data on Relation SupplierAID, otherwise it cannot match the value.

Images are not displayed and the ValidationLog shows the MimeSource with a point (.) without having this point in the BMECat

Your BMECat has the tag <MIME_ROOT>.</MIME_ROOT>. Please leave this tag empty: <MIME_ROOT></MIME_ROOT>. The system will then not append the point before your MIME_SOURCE.