OroCommerce Forums

Covering OroCommerce topics, including community updates and company announcements.

Forums Forums OroCommerce Product import error

This topic contains 5 replies, has 2 voices, and was last updated by  matthew.brookes 5 years, 7 months ago.

Starting from March 1, 2020 the forum has been switched to the read-only mode. Please head to StackOverflow for support.

  • Creator
    Topic
  • #37307

    matthew.brookes
    Participant

    Hi

    now I have the product import working I have hit a new error, I can not update products via the admin. I receive the following error:

    Error in row #1. sku: This value is already used.”

    any ideas why this would occur?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Author
    Replies
  • #37312

    Andrey Yatsenko
    Moderator

    Generally, an error appears when you are trying to create a product with the SKU that already used for another one.

    The fix depends on how your import files look like.
    Can you share the import file, just a few lines that cause errors so we can validate it?

    #37317

    matthew.brookes
    Participant

    Hi Andrey

    thanks for coming back to me the file looks like the below, we are using the built in product importer with some custom attributes and need to update the products that have changed. :

    attributeFamily.code sku status type inventory_status.id primaryUnitPrecision.unit.code primaryUnitPrecision.precision primaryUnitPrecision.conversionRate primaryUnitPrecision.sell additionalUnitPrecisions:0:unit:code additionalUnitPrecisions:0:precision additionalUnitPrecisions:0:conversionRate additionalUnitPrecisions:0:sell names.default.fallback names.default.value names.English.fallback names.English.value names.English (United Kingdom).fallback names.English (United Kingdom).value shortDescriptions.default.fallback shortDescriptions.default.value shortDescriptions.English.fallback shortDescriptions.English.value shortDescriptions.English (United Kingdom).fallback shortDescriptions.English (United Kingdom).value descriptions.default.fallback descriptions.default.value descriptions.English.fallback descriptions.English.value descriptions.English (United Kingdom).fallback descriptions.English (United Kingdom).value variantFields variantLinks.1.product.sku variantLinks.1.visible availability_date Capacity Colour_new Guarantee featured material newArrival Power ProductFeatures Product_Type weight metaDescriptions.default.fallback metaDescriptions.default.value metaDescriptions.English.fallback metaDescriptions.English.value metaDescriptions.English (United Kingdom).fallback metaDescriptions.English (United Kingdom).value metaKeywords.default.fallback metaKeywords.default.value metaKeywords.English.fallback metaKeywords.English.value metaKeywords.English (United Kingdom).fallback metaKeywords.English (United Kingdom).value metaTitles.default.fallback metaTitles.default.value metaTitles.English.fallback metaTitles.English.value metaTitles.English (United Kingdom).fallback metaTitles.English (United Kingdom).value slugs.1.localization.name slugPrototypes.default.fallback slugPrototypes.default.value slugPrototypes.English.fallback slugPrototypes.English.value slugPrototypes.English (United Kingdom).fallback slugPrototypes.English (United Kingdom).value category.default.title isUpcoming
    default_family WAF1U2 enabled simple in_stock each 1 1 1 item 0 5 0 WAFFLE MAKER WAFFLE MAKER WAFFLE MAKER WAFFLE MAKER Description one main descriptions 2018-08-31T00:00:00+0000 1L Stainless Steel 1yr 0 Stainless Steel 0 1000 Watts features Waffle Maker 3.08Kg Sage 1

    #37319

    Andrey Yatsenko
    Moderator

    Do you have an existing product with exact same SKU “WAF1U2” and same case?

    #37320

    matthew.brookes
    Participant

    yes there is an existing product with exactly the same SKU. We are looking to update the product details using the importer. rather than just create a new product. My understanding was that the importer would update a product with the new details in the CVS if the SKU matched.

    #37336

    matthew.brookes
    Participant

    Hi

    we eventually tracked this down to the message queue having too many jobs in it (oro_message_queue_job) and not able to process them. We have cleared this down and now things look back to normal.

    thanks for you guidance though.

Viewing 5 replies - 1 through 5 (of 5 total)

The forum ‘OroCommerce’ is closed to new topics and replies.

Back to top