-
Notifications
You must be signed in to change notification settings - Fork 199
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
No Customers Visible In Admin Backend After Migration #43
Comments
In the interest of getting more data here, I believe the problem is related to getting EAV values mapped correctly, but I'm a bit lost trying to figure out what is not mapping right. I have not touched the EAV mapping stuff in the migrator - just using the distribution defaults for them. Here is a complete list of the differences in table row counts from M1 to M2 post-migration. Some tables I expect to have different counts, others should not. I suspect the problem is that the data from eav_attribute is not moving from M1 to M2 correctly, so all the eav tables are messed up as a result. Help? |
A lot of attributes that were saved in the customer_entity_int and customer_entity_varchar tables in M1 are now stored in the customer_entity table in M2. I don't know why not all of your customer are migrated. I have the same issue migrating customers from 1.9.2.2. |
Hi, 1 2 |
Sweet! I can see my customers in the admin section now. However, whenever I try to edit a customer record, I get this error: "The configuration parameter "formElement" is a required for "enable" field." |
Here is the full error report, in case that is useful: a:4:{i:0;s:75:"The configuration parameter "formElement" is a required for "enable" field.";i:1;s:9772:"#0 /var/www/miridiatech/store/vendor/magento/module-ui/Component/Form/Fieldset.php(107): Magento\Ui\Component\Form\Field->prepare() |
@quangdog |
I'm migrating from 1.7.0.2 -> 2.0.0, and the migrator runs with no errors reported in the log. After migration, when I log into the backend of the store I see 0 customers in the admin panel. When checking the database tables, it appears that a bunch of data was not actually migrated:
customer_address_entity_text:
M1 database: 9989 rows
M2 database: 0 rows
customer_entity_int:
M1 database: 23585 rows
M2 database: 8286 rows
customer_entity_varchar:
M1 database: 47199 rows
M2 database: 4818 rows
These are just a few examples of differences... lots of other tables have what appear to be incorrect row counts. Shouldn't they all have the same number of rows?
The text was updated successfully, but these errors were encountered: