Magento Magmi: Solving Attribute Import Issues Across Multiple Stores/languages
Magento’s Mass Global Management Interface (MAGMI) is an incredibly powerful tool for bulk data imports and exports in your e-commerce store. One of the key features of MAGMI is its ability to handle multi-language attribute translations effortlessly, which can save hours of manual work when managing large catalogs.
Understanding Multi-Store Attribute Translations
Let’s start by understanding how Magmi handles translated attributes across multiple stores or language scopes. As per the official MAGMI Wiki (which I recommend bookmarking for future reference), there is a specific syntax to follow when importing admin values and their corresponding translations:
- First, import your admin values using the following structure:
"store","sku","myselect"
"admin","sku001","adminval1"
"admin","sku002","adminval2"
"admin","sku003","adminval3"
In this example, “myselect” is your attribute, and the admin values are being imported for each SKU.
- Next, import the translations using the correct syntax:
"store","sku","myselect"
"store1","sku001","store1val1::[adminval1]"
"store2","sku001","store2val1::[adminval1]"
"store1","sku002","store1val2::[adminval2]"
"store2","sku002","store2val2::[adminval2]"
Notice the syntax for each translated value: translated_value::[admin_value]. This tells Magmi to translate the attribute based on the admin value.
Solving Your Translation Muddling Issue
You mentioned that after following this syntax, your attributes ended up “muddled” (see here). This is likely due to a common misconception about Magmi’s import order and how it handles multi-store data.
The key lies in the order you perform your imports. Here are the steps to follow:
-
Import Admin Values: Start by importing the admin values for each attribute using the first syntax provided above. Ensure the store is set to “admin” for all lines in this import file.
-
Wait: After the admin import is complete, Magmi stores these as base values that will be used for translation later on.
-
Import Store Values: Once you have the admin values imported, proceed with importing the translated values using the second syntax. Set the “store” column to your desired storeview (e.g., “deutsch”) and provide the corresponding translations in the required format (
translated_value::[admin_value]). -
Use the Magmi Compatibility Mode: If you’re still facing issues, ensure that your Magmi version supports multi-language attribute translation. As of writing this post, the latest stable release (v0.7.18) should have no compatibility issues with Magento 2.x.
Conclusion
Multi-store and multi-language attribute management is a powerful feature in Magento, and tools like MAGMI make it much more efficient. The key lies in understanding the correct syntax for import files and ensuring you follow the right order: admin values first, then translations.
Remember to always use the latest stable Magmi version compatible with your Magento setup to avoid any compatibility issues. If you’re still facing difficulties after following these steps, don’t hesitate to reach out for further assistance or consult the extensive Magmi Documentation and Community Forums.
Happy importing!