Multi store import issues with Magento 1.9.2.2 & Magmi 0.7.23

[pixiemediaweb]

Hi,

We're migrating a site from Magento 1.7 to 1.9.2.2 and have upgraded Magmi in the process, but we're having an issue with the imports on the new version where the site allocation of a product is being overwritten with each subsequent import, eg;

~store~,~websites~,~tax_class_id~,~sku~,~name~ ~admin,gb_en_dealer~,~gb~,~2~,~nowyouseeme~,~TESTING~

Product imports fine, default values are set and it is available in the gb store.

Then when we add it to the Italian store, like this;

~store~,~websites~,~tax_class_id~,~sku~,~name~ ~it_it_dealer~,~it~,~2~,~nowyouseeme~,~TESTING~

The import succeeds, but now the product has been removed from the GB store and is available in the Italian store only. Previously, Magmi would append the product allocation so the product would be available in both stores.

I've read that the websites column was retired and re-instated, but just to be sure, i deleted the test product and tried the above again with the websites column removed.

The results of that test the product is added to the GB store on the first import, then the second import appears to do nothing. The product remains on the GB store only.

Any ideas?

[pixiemediaweb]

Just made another test. It seems if you declare all the stores the first time you import the product it adds them, eg;

~store~,~tax_class_id~,~sku~,~name~ ~admin,gb_en_dealer,it_it_dealer~,~2~,~test1234~,~GB TEST~

That product is now available in the GB and IT stores. Running a further import like this;

~it_it_dealer~,~2~,~test1234~,~IT TEST~

Updates the product name in the IT store. If I then want to add it to the German store;

~de_de_dealer~,~2~,~test1234~,~DE TEST~

Does nothing.

Is there a configuration for this?

[pixiemediaweb]

Any feedback on this issue would be greatly appreciated

[dweeves]

Hi , indeed , magmi does not "add existing products to new store" for existing products. the store colum is here to define on which scope the values are te be applied. so for an existing product, putting a store on which the product does not exist won't do anything.

[pixiemediaweb]

Thank you very much for the feedback dweeves

Can you asvise the correct way to add an existing product to a new store?

[pixiemediaweb]

worth noting that adding existing products to new stores works on the older version of magmi - version was 0.7.18beta1

[frshjb373]

Can you asvise the correct way to add an existing product to a new store?

I'm running into same issue on my end too. Any help or resource is much appreciated.

[Jeeva-Rathinam]

How can i import images using by magmi for my multi store Magento? As a single store its working fine, after added additional store, magmi image not working. csv screen shot : https://snag.gy/Ju6MbK.jpg if i did any error, pls let me know and demo CSV sheet.

[Quazz]

I would just like to comment on this, because the explanation doesn't fully stack up with other capabilities of Magmi.

I can, for example, assign an existing product to a category in a store of a website it 'doesn't exist yet'.

This works fine, but of course you can't actually see the product due to magento thinking it doesn't exist on the website. (activating the checkbox and saving manually, does fix this, however)

If you are able to assign it to a different store root, then surely, that website should also activate as per expected result? Otherwise, I don't much see the point in being able to update category structure in that fashion.

[pixiemediaweb]

Hi Quazz, adding a product to a category wouldn't (for us anyway) necessarily mean you want the product live on all the websites that happen to use that category tree. In one of our installs we have a category tree of 2000 categories which are shared across 25 websites, each with a single storeview. It's really important for our project to be able to manage products store availability using magmi with the store column, which we do using the old version i mentioned above that does allow existing products to be added to new stores. Category allocation is global so would not allow the flexibility we need. Only slight drawback is we need to use additonal csv's to disable products in stores if they become unavailable for that storeview, but this is totally manageable and we use magmi to maintain a catalogue of 50,000 products in 25 storeviews as a nightlly process

[Quazz]

Perhaps bringing back the websites column as an optional parameter would be interesting. This way people could continue to use Magmi as they were and also have the option to move existing products around if needed.