For some reason Magmi is not importing a new configurable item.
In brief. Created Attribute, Created Attribute set, used an existing working template csv and added data.
In Magmi select “create New items only”, but then get message “Skipped 11 records”.
Have checked the progress file and it shows
“skip:skipping unknown sku:GB1205 – update mode set
itime:2 – 0.000956058502197 – 0.000817060470581″ etc.
I will email a zip file with the csv file and progress report to you, hope that’s okay.
Thanks for including the text, the bit that tells us what it is this this part:
When running that import, set the mode to “create and update” rather than just update. The mode above is the update mode and it’s skipping new products, the other mode will create and update them as desired.
Thanks for pointing that out. Not used Magmi for a week or 2 and got out of the swing of things.
I had been selecting the file to import, then selecting “create new items only”, and then clicking save profile to default, thinking that was the order of sequence.
Of course, this just refreshed the page so once I ran the import it was back on “Update existing items only”.
2 weeks out of the loop, 1 step out of sequence, and 3 hours on Friday night spent thinking why is this not working.
I know I should have just checked the video tutorial again (as I have now), but I was sure I was doing it correctly.
Hi Matthew – SKU numbers for some products where imported wrong. So I went a head and updated the SKU numbers with a query through MySQL in table catalog_product_entity.
All the revised SKUs show up in Magento back-end and front-end, but when I want to update the quantities for the revised SKUs through Magmi, I get the message “Skipped 490 records”. And in Magmi‘s progress.txt file I get the following errors:
“skip:skipping unknown sku:abc-01 – update mode set” 490 times
I have looked everywhere but I can’t find out why this is happening?
Does Magmi cache anything?
Why is it not seeing the SKUs in Magento?
Is there another method than MySQL query to update the SKUs?
Should I be updating another table?
Thank you in advance for your help.
I’m not sure on the implications of making that change has been.
One daft question/line of thought for you, have you set Magmi to skip existing records? That would explain that message.
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