Resolved Change column headers

Hello Lorenzo,

With RO CSVI you can give your column headers any name you like. However, I am more worried about the data in your files. First thing I notice is the sequence number, this does not strike me as a field from HikaShop but rather a custom field. Is that correct? RO CSVI does not have such a field.

Could you share how the export is build now? Is it another extension where you can just pick the fields or is it an SQL query?

We would need to see if you can get the same data out of your HikaShop as now.

Let me know and we can check further.

Hi Roland,
thanks again for your prompt reply. I apologize for the confusion in my previous message; I mistakenly attached only the delivery service's csv files and forgot to attach Hikashop csv file.
The files I've attached are only those that the delivery service makes available and which must be filled in before being loaded onto their delivery platform.

To recap, I'm hoping to use RO CSVI to achieve the following:

- Create custom fields in Hikashop (if necessary) to capture the data required by the delivery service.
- Modify the Hikashop CSV file to match the header structure of the delivery service's csv file.

First thing I notice is the sequence number, this does not strike me as a field from HikaShop but rather a custom field. Is that correct?

The "sequence number" is a field in the delivery service's csv file, not in Hikashop.
Here's an overview of the column headers in the delivery service's csv file (sorry, it's in Italian, but I think it's not so difficult to translate just to understand the meaning of the header).

Could you share how the export is build now?

Are you referring to the Hikashop export? In the meantime, here's an export of a simple Hikashop order + a simple csv file to fill in from the delivery service (it's the same as one of those I sent you in my first message).

Thanks again,
Lorenzo

Hello Lorenzo,

- Create custom fields in Hikashop (if necessary) to capture the data required by the delivery service.

Yes, you can create custom fields in HikaShop and run the update of available fields in RO CSVI. You will be able to add these custom fields to export template after that.

- Modify the Hikashop CSV file to match the header structure of the delivery service's csv file.

In template fields page when you add a new export field you can set Your field to the header you need. You can also run a sample export on our demo site and check for column headers.

Hi and thanks for your reply Tharuna, so I guess Roland's doubts about my example have been clarified.

It's clear that RO CSVI is a fairly complex component, but I think it's the only extension that can help me to load orders from Hikashop to the delivery service.

One question about automation. I believe it's possible to automate this task? To clarify, instead of importing the csv file from Hikashop into RO CSVI for subsequent export, RO CSVI would directly handle the export upon order submission.
But perhaps I should take a closer look at how your component works...

In any case, I'm meeting with the delivery service team on Monday to discuss their csv file requirements in more detail. This will help me better understand how to make the two components work together.

Thanks again,
Lorenzo

Hello Lorenzo,

It's clear that RO CSVI is a fairly complex component

Correct, RO CSVI has somewhat of a learning curve but that comes with the territory However we do supply example templates that can serve as a starting point.

One question about automation. I believe it's possible to automate this task?

Yes, RO CSVI can be run as a cronjob provided you have enabled cron in the template. For Joomla 4/5 we include a task to run it through the Joomla CLI.

RO CSVI would directly handle the export upon order submission.

That is possible as well. Have a look at the Export HikaShop order after an order is created document. That may be something you are after.

Let us know if you have any further questions.