This log message informs you that an automatic clean-up of statuses in your system could not be fully completed because certain data is still linked together. This is a normal technical process and has no negative impact on your data or the stability of your PlentyONE system.Cause of the messageThe message SQLSTATE[23000]: occurs when the system tries to delete outdated entries in the plenty_catalog_statuses table. However, since these statuses are still referenced in the plenty_catalog_channel_maps (the links between your catalogues and the marketplaces), the database prevents deletion in order to maintain data integrity.The error message specifically names the affected link: CONSTRAINT plenty_catalog_channel_maps_status_id_foreign FOREIGN KEY (status_id) REFERENCES plenty_catalog_statuses (id)This simply means: A status cannot be removed as long as it is still assigned to a Channel Map.Impact on the systemYou do not need to take any action:No data loss: No active or required data is damaged.For information only: The message merel...

With the formula function, you can automatically adjust and recalculate numerical values of PlentyONE data fields during export. The basic arithmetic operations are available for the formulas.Requirements and basic principleData field type: This function only works with data fields that contain numerical values.Principle: You specify that the numerical value of a PlentyONE data field is recalculated during export based on the formula you entered. The calculation is performed during the next export.Step-by-step guide to creating a formula assignmentClick on the Assignment tab next to the sales channel data field on + Add data field.On the left, the list of available PlentyONE data fields appears as groups.Click at the very top next to Formula (calculate) on the plus symbol.The data field Formula is inserted into the field on the right.Click into the Formula data field.The Change value window is displayed.Create formula: Enter numbers and mathematical operators either using the displayed calculator or via the keyboard.Add PlentyONE d...

If you are sure that the same value should be transferred for a sales channel data field for all variants of your catalogue, you can use a custom value mapping. You specify a fixed value that will then be exported for all variants of the catalogue.Basic principleYou specify that the value entered in the Custom value field is exported for the sales channel data field.Important: With this type of mapping, the entered value is always exported. This also applies to complex mappings where normally the value of the sales channel would be exported. Therefore, make sure that the value you enter as a custom value is accepted by the sales channel.Step-by-step instructions for creationClick on the Mapping tab next to the sales channel data field on + Add data field.The list of available PlentyONE data fields appears on the left as groups.Click the plus symbol at the very top next to Custom value.The field for the custom value is added to the view.Enter the desired value in the input field below.This value will now be exported for all variants...

In a 1:n assignment, you assign multiple PlentyONE data fields to a single sales channel data field. These PlentyONE data fields are combined during export and connected by a delimiter of your choice.Basic principleWith this type of assignment, you specify that the sales channel data field is filled with the combined data from two or more PlentyONE settings (e.g. to generate a title from item name and additional).Step-by-step guide to creationClick on the Assignment tab next to the sales channel data field on + Add data field.On the left, the list of available PlentyONE data fields appears as groups.Select the desired group and click the plus next to the first PlentyONE data field.Click on Confirm.Click on Add data field to the right of the data field you just assigned.The list of PlentyONE data fields will be displayed again on the left.Assign one or more additional PlentyONE data fields to the sales channel data field as described and click on Confirm.Click on Settings at the far right of the sales channel data field row.Select a...

In a 1:1 mapping with fallback data fields, you assign a primary PlentyONE data field to the sales channel data field and additionally define one or more alternative data fields. These fallback data fields ensure that the system continues searching if the primary data field for a variant is missing or empty.How the fallback principle worksThe system checks the assigned PlentyONE data fields in the order in which they were assigned in the catalogue:First data field (Primary): The value is transferred if the data field is filled.Fallback data field 1: Is checked if the first data field meets the defined fallback condition (e.g. null or empty). If a value is found, it is transferred.Fallback data field 2: Is checked if fallback data field 1 also meets the condition, and so on.Important: For each variant, only one value is transferred in the end.The two fallback conditionsFallback conditionMeaningSuitable for PlentyONE data fieldsnull (default)The fallback data field is used if the data field above is assigned in the catalogue but not ...

Complex 1:1 mappings are necessary whenever there are various possible values for a sales channel data field and you need to inform the system which of your PlentyONE values corresponds to which value of the sales channel.Basic principle of the complex mappingIn complex mappings, you assign individual values of data fields or attributes, rather than just the PlentyONE setting itself. For example, the sales channel cannot know which PlentyONE shipping profile belongs to its shipping method, so you must explicitly map the values.Identification: You can recognise complex mappings by the fact that there is an input field below the name of the sales channel data field. When you click in this field, the possible values for the sales channel data field are displayed (e.g. for categories, brands, shipping method).Step-by-step guide to creationClick in the input field for the sales channel data field.A list of the available sales channel values will be displayed.Select the sales channel value to which you want to assign a PlentyONE data fie...

If there is no suitable PlentyONE standard data field to fill a mandatory field of the sales channel (e.g. Amazon), you can use an attribute. With attributes, you can store any additional information on your variants and then assign them in the catalogue.RequirementFirst, you need to create the required attribute with the necessary values.Step-by-step guide to 1:1 mapping with attributesClick on Mapping tab of the catalogue next to the desired sales channel data field on + Add data field.A list of available PlentyONE data fields divided into groups appears on the left.Expand the group Attribute.The attribute groups are displayed.Expand the desired attribute group.Click the plus icon to the right of the desired attribute.Select the language from the dropdown list Language in which you want to export your data to the sales channel.Click Confirm.The attribute is assigned to the sales channel data field.

A simple 1:1 mapping links a single sales channel data field directly with a PlentyONE data field or a PlentyONE property. It defines that the sales channel data field should be populated with data from the PlentyONE setting.Important noteIf the assigned PlentyONE data field is empty for a particular variant, no value will be exported for this variant to the sales channel.Step-by-step guide to creating the simple 1:1 mappingClick on the Mapping tab of the catalogue next to the desired sales channel data field on + Add data field.A list of available PlentyONE data fields divided into groups will appear on the left.Click on the desired group (e.g. Prices, Item master data).The PlentyONE data fields of the selected group will be displayed.Click the plus symbol next to the desired PlentyONE data field.The PlentyONE data field will be inserted into the right field.Click on Confirm.Option if PlentyONE data field is missingIf there is no suitable setting in PlentyONE for the required data, you can alternatively create a property and assig...