Skip to content
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

New Orders are not in Order grid after data migration from M 1.7.0.2 to M 2.1.7 #10185

Closed
joergmaertin opened this issue Jul 7, 2017 · 8 comments
Labels
bug report Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development

Comments

@joergmaertin
Copy link

joergmaertin commented Jul 7, 2017

Preconditions

  1. PHP 5.6 latest FPM
  2. MySQL 5.6.19
  3. Running Magento CE 1.7.0.2, database replicated, no problems here.
  4. Fresh Magento CE 2.1.7 with Luma Theme
  5. Datamigration Tool 2.1.7
  6. vendor/magento/data-migration-tool/etc/ce-to-ce/1.7.0.2/config.xml Datamigration

Steps to reproduce

  1. Migrate Data from 1.7.0.2 to Magento 2.1.7
  2. Place order as guest in Magento 2.1.7
  3. Choose internal Payment method "Check/Money order" or "Bank transfer"
  4. Finish order

Expected result

  1. The customer should get an email about the order
  2. The order should be visible in order grid
  3. The order should be visible in dashboard

Actual result

  1. The Customer gets an email with correct content of order and order no. that is in line with the order no. in general
    2. But the order is not visible in order grid, it seems not being saved here
  2. The order is visible with entry "Guest" in Dashboard. Magento 1.7.0.2 saved the name of the customer here even as guest.

The issue has been first reported in #4431 which was closed. Again reported in #10128, on request the issue has been specified here.

I have included logs in #10128. I'd like to include my datamigration config files here to review. Maybe there is something important missing in my files, which also need to be migrated.

@joergmaertin joergmaertin changed the title Orders are not in order grid after data migration from M 1.7.0.2 to M 2.1.7 New Orders are not in Order grid after data migration from M 1.7.0.2 to M 2.1.7 Jul 7, 2017
@ihor-sviziev
Copy link
Contributor

Hi @joergmaertin,
For data migration tool we have separate repository, so you should ask it there:
https://github.com/magento/data-migration-tool

Did you ran reindex from cli after migration? Reindex of grids in m2 is async and it runs during cron execution. Did you configured cron jobs?

@joergmaertin
Copy link
Author

joergmaertin commented Jul 8, 2017

@ihor-sviziev I indeed ran reindex from CLI and also now from cron. The result is the same: nothing in order grid.

@magento-engcom-team magento-engcom-team added G1 Passed bug report Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed and removed G1 Passed labels Sep 5, 2017
@magento-engcom-team
Copy link
Contributor

Hi @joergmaertin
Please report migration related issues to the migration tool repository: https://github.com/magento/data-migration-tool
Thank you

@ihor-sviziev
Copy link
Contributor

I got the same issue after upgrading from M1 to M 2.1.9. Issue is not actually related to data migration tool, but it caused by incorrect sorting by order id field in order grid. It sort as string, but not as a number. Issue appeared because in M1 we had 9 symbols for order number, while in M2 it use 10. I didn't found any related issues, except this one. And this issue is already closed because it looked as data migration issue, but it isn't.

Workaround sort by Purchase Date field:
capture 2017-10-05 at 9 21 13

@okorshenko
Copy link
Contributor

Hi @ihor-sviziev
The column ID renders the data from DB column increment_id (varchar(50)). So it is string by design. Also we have a feature that allows you to change order id generation pattern (see the table select * from sales_sequence_profile;). You can add suffix, prefix, step and etc. This is a requirement dictated by law in some countries.
If you would like to change pattern for Order ID generation you can customize it via DI for the class \Magento\SalesSequence\Model\Sequence. By default we are using %s%'.09d%s but it is customizable.
So I would say that from the Magento prospective this is not a bug. This is expected system behavior. Order ID (increment_id) is a string by default. If you will add prefix/suffix you can not sort the orders by ID as int value.

@magento-team
Copy link
Contributor

Internal ticket to track issue progress: MAGETWO-83084

@magento-team magento-team added 2.2.x Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development labels Nov 2, 2017
@magento-team
Copy link
Contributor

Internal ticket to track issue progress: MAGETWO-83155

@magento-team
Copy link
Contributor

Internal ticket to track issue progress: MAGETWO-83154

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development
Projects
None yet
Development

No branches or pull requests

6 participants