VM Import Issues

Hi,

1. The order history import is not supported by the import system.
If you need it, you would have to import the data manually with either a custom script.

2. Looking at the code of the import, the order_number from the VM order table is used for the order_number column of the HikaShop order table.
So I don't see why the order number wouldn't be correct. Are you sure you're not talking about something else like the order_id or another column of the order table of VirtueMart ? Which VirtueMart version were you using ?

Hi,

1/ I'm sorry but that's just a fact ; the import of the virtuemart order history is not supported by HikaShop 2.4.0
But it does not means that Nicolas didn't create a feature request ticket in our system for that
After that, even if we have a feature request ticket in our side, the feature could not be added in a short delay ; we are currently finishing the next HikaShop release and performing the tests.

2/ The Virtuemart "order number" is stored in the HikaShop "order number" and the Virtuemart "order id" is stored in the HikaShop "order_vm_id".
We can't set the "order_id" of HikaShop with the virtuemart "order_id".
The system plugin "vm_redirect" read the parameter "order_number" and will look at the corresponding order thanks to the "order_vm_id" ; so the fallback should work correctly and no information (order id / order number) is lost during the import.

Regards,

Hi,

2) I see what you means. The HikaShop search in the backend can't look into the VM field..
I don't know if the order number has an importance or not for you ; but you can see to copy the order_vm_id into the order_number if you want to use that id instead.

You can use a mass-action to perform the copy or you can use a query like that :

UPDATE #__hikashop_order SET order_number = order_vm_id WHERE order_vm_id IS NOT NULL AND order_vm_id != '';