Not so New
My CSV file is generated from our master products database system. I can completely change the format with which the CSV is output as it’s a script I am developing in-house.
Say I have 5 websites + admin:
www_site1_com and www_site3_com already have product SKU ‘123456’ assigned.
I want to import SKU ‘123456’ via Magmi, so it’s assigned to www_site5_com AS WELL AS any existing sites.
Ideally, I would want to configure the CSV as:
Alas, I have tried this, but it doesn’t appear to accept ‘*’.
My data set will eventually have 1m+ products with a dozen or more websites, so I really need to be able to do this in an automated, scalable way, i.e.: manually editing the CSVs to edit the websites columns based on target sites is never going to be an option.
Does anyone know a way to do this via Magmi? Else I will have to look at querying Magento for every SKU, during my CSV creation process, and building an array of all currently assigned websites, to populate my ‘websites’ column’, which just seems sloppy – if it’s even possible.
the website column in magmi is no longer, you use the store heading which is where you put store view code in.
As the websites will be set up in magento separately with own root category meaning each website will have own store view and therefore the product will only be added to that store view.
To assigned products to different root categories [root category]/category/category and separate by ; or maybe ;; can’t remember of the top of my head if you need to assign products to more than one category
That’s using magento ce not ee
Hope that helps
Everyday is an opportunity to learn something new
Not so New
Thank you for your reply.
The websites column does work as we have tested it extensively and observed definite effects of using it. Dweeves also confirms that it was re-instated a while back here: https://github.com/dweeves/magmi-git/issues/23.
I can’t help thinking this is actually some kind of bug we’ve found, as we have noticed a number of people with similar problems/expectations regarding the ‘websites’ column. For instance:
As one poster noticed, if you specify a target website in your CSV and the SKU already exists in another website (e.g.: ‘site1’) then Magmi actually ‘moves’ the SKU to the targeted website from its existing website, i.e.:
We’d expect Magmi to just apply the updates to the SKU under that specific website/store, not actually move it!
Why Should You Join UnderstandingE?
- Access to over 500 step-by-step video tutorials
- +20 video courses available
- Magento, M2E Pro, Magmi, eBay, Amazon & Design all covered
- Everything is in 100% Plain English
- Learn how to build your own multi-channel software for eBay & Amazon
- Access to the community forums, meet fellow business owners like yourself
Join Now with 2 Clicks
Join now for less that £1 per day you can gain access to over 400 step-by-step video tutorials & learn how to build your very own multi-channel software.
Most Users Ever Online: 1012
Currently Browsing this Page:
Jim @ Moogento: 688
Steve Froggatt: 514
Badeth - UE: 513
Paul Cartwright: 414
Administrators: Matthew Ogborne: 4565, Dave Furness: 4606