Hi There,
I’m currently executing step 7 of the migration and presumably some of the data in my previous install is incomplete. I’ve tried looking through the tables but nothing seems apparent.
Where would I be getting this error -- and where should I look to correct it?
$ php bin/ubdatamigration run --step=7
Processing in step #7…………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………
Status: fail
Message: Mage2SalesOrder: Created At cannot be blank.
-- Updated At cannot be blank.
3 answers
Hi there,
Status: fail
Message: Mage2SalesOrder: Created At cannot be blank.
— Updated At cannot be blank.
The created_at and updated_at are required value fields as default rules of Magento database structure. But it was missed on some records in table sales_flat_order in your M1 database.
Let’s provide me the more information as followings:
+ Admin credentials and site URL
+ SSH credentials and web root path of your M2 instance.
I will check further and provide you a tweak code in our tool to handle for that cases.
Regards,
Mall.
Hi Mall,
Unfortunately this is all local at the moment. I managed to do a call trace from within yii and tracked down the offending record.
I guess what would really help in this situation is for the logging to be more verbose (such a the offending table and entity_id). In any case it’s all back up and running now -- thanks!.
2 million records later and we’ll see where we’re at 🙂
Thanks.
Nick.
Hi Nick,
Glad that you figured it out.
Anyway, it would be best if you could deploy an online instance where we could directly debug and provide you technical workaround for any issue you might have.
Wish you and your family a very Happy New Year!
Sincerely,
Ubertheme team
