Wrong columns in massaction export

Hi,

There is no mechanism to select the order of the columns. The order is basically how they are stored in the mass action data.
The simplest I think would be to edit the data of the mass action in the hikashop_massaction table in your PHPMyAdmin and check the order of the columns in the serialized data.
Ideally, it would be best to not rely on the order of the columns when handling a CSV but rather the name of the columns. That's what we do for the import in HikaShop and how I've seen it anywhere I've had to import CSV files.

Hi,

Ok, I see what you mean now.
I tried to reproduce the problem on my end but I wasn't able to.
So there must be something specific to your setup which led to this issue.
Could you provide a backend access, a FTP access, the name of the mass action to use for my tests and a link to this thread for reference via our contact form so that I can look into it ?
www.hikashop.com/support/contact-us.html

Thanks. Looking at the situation on your website, I found that you had selected the "order_id" in the order_product selector, not in the "order" selector. And that caused the issue with the XLSX.
I was then able to reproduce the problem on my local test website.
That way I was able to do some debugging and found what was the problem.
I've made a patch and it is now working fine for me.
I've included the patch on our end. To get it on your website, download the latest version install package of HikaShop on our website and install it on yours.

Hi,

Disable the order_id column from the order_product area and activate it in the order area and you'll have only one order_id column.

Hi,

It's not really a duplication. The first one is the order_id from the hikashop_order table. The second one is the order_id from the hikashop_order_product table.
When you export an order without any products, the first one will have the id of the order while the second one will be empty.

The first one is added to all the export files. I'm not sure why this is done. I suppose it is used in some cases to link the other data of the order with the order itself.
However, removing it doesn't cause any issue in the tests I did. So we probably could remove it. The column was actually added to the export in a wrong way when it was first added, 10 years ago. Recently, I stubbled on that piece of code and saw the code was incorrect and thus I fixed it, which led to the column being in the CSV even if you don't select it.

I suppose it would make sense to not have it since it can be selected anyways and it doesn't cause any issue not having it as far as I can see.
For that, remove the line:

$params->action['order']['order_id'] = 'order_id';