-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Record structure does not contain field "is_configurable": #595
Comments
Hi @lokisp The error is thrown by Map step. Check your map.xml file contain
|
I am getting an identical error except I am migration from Enterprise 1.14.1.0 to Enterprise 2.2.6. However the field that is not apart of the Record Structure is the Edit, I have found a column in |
…r during migration with -auto option #595
Hi @lokisp @dsmithhayes |
Hi Victor, |
Thank you. I have noticed that the fields in my Magento 1 (Enterprise 1.14.1.0) are the result of custom modules appending columns to tables. I have noted other tables with issues in regards to non-matching fields:
Common characteristics between each un-mappable field is they are not nullable and from third party sources. The list of fields is long and relevent to our third party extensions but I am willing to provide that information with you. I would also like to note that The Data Migration Tool versioned |
Confirmed 13728b3 fixed the problem on 2.2.6 also |
I have problem when migration data from magento1 to magento2.
It show Record structure does not contain field "is_configurable":
Preconditions
https://prnt.sc/kzgbj8
Steps to reproduce
Expected result
Actual result
https://prnt.sc/kzgbj8
It shows : Record structure does not contain field "is_configurable"
Actually, I checked database of magento1. It is default column magento.
However, I add additional ignore in file map-eav.xml:
<ignore> <field>eav_attribute.is_configurable</field> </ignore>
My config file:
However I still meet same problem. If I run again. It will show default attribute exist (I must reinstall and try again but nothing help)
The text was updated successfully, but these errors were encountered: