search

commercetools / sphere-node-product-csv-sync

Component to import, export and update your SPHERE.IO products via CSV.
https://impex.sphere.io
MIT License
13 stars 11 forks source link

Export of the product categories in all languages in one product export file #114

Open CT-Szilvia opened 8 years ago

CT-Szilvia commented 8 years ago

Dear team,

I would like to export the product categories in all possible languages within one product export file. One of our customer has 5 languages, so my product export template would look like (just as an example): productType,id,sku,variantId,categories.en,categories.de,categories.it,categories.es,categories.fr.

It would be nice to have this feature, because sometimes we need to map some data by the csv-mapper. Now I need to export products 5 times in 5 languages to have the slug or the name path. It would be much easier, if I could do this directly in one product file. For the first it would be enough to have the name path like product,xxxx,I00123,1,Men>Pants>Chino, Men>Hosen>Chino,Uomo>Pantaloni>Chino,Hombre>Pantalones>Chino,Homme>Pantalons>Chino

Many thanks and happy about your feedback!

Regards, Szilvia

adnasa commented 7 years ago

@hisabimbola @wizzy25 Is this still relevant? close?

hisabimbola commented 7 years ago

I think the issue is still valid though not sure if relevant.

Not sure if we should abandon though

adnasa commented 7 years ago

hmmm... exporting category data associated to the product in the product export command, sounds overkill IMO, since this essentially means that we leverage the expand GET query through product projections. This would end up in a pretty massive request/response to handle.

One thing I'm worried about is that if we do this, we're extending the boundary of product export command, which is not really necessary.

possibility

  1. This would be possible if the product export command leverages our graphql endpoint though
    • 👍🏽 because of the nature of graphql, it should be pretty easy to map the column defined in the template being uploaded to selectable graphql fields.
    • Unfortunately this requires quite the re-factoring on the product export csv package.
    • 👎🏾 this introduces a side effect and expand the boundary of what the product export is built for. Requires a decision before we proceed.
  2. Use the expand GET query
    • 👎🏾 massive request/response, expanding the entire (not only bound to) category reference only to select specific fields that are localized.