RO CSVI

04 December 2013 | RO CSVI

Basic XML

CSVI has the option to import and export products in the XML format. The XML format by itself is an open standard, this means it has no fixed structure. The structure is defined by the program itself and is called an XML schema. For CSVI the structure looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<channel>
<item>
</item>
</channel>

Every XML file needs to start with the line:

<?xml version="1.0" encoding="UTF-8"?>

This line tells the program it is an XML file and data is encoded in UTF-8.

The second line starts the group of data and looks like:

<channel>

Each set of data is contained in a node called “item”. The node starts like:

<item>

Now the data to import follows. Inside the node we use tags to identify the type of data that is being imported or exported. A tag is exactly the same as a column in a spreadsheet. A single tag looks for example like:

<product_sku>LAP01</product_sku>

• The opening tag is

  <product_sku>

• The data is CSVI101
• The closing tag is

  </product_sku>

It is important that each tag is closed otherwise the XML file is invalid.

After all the data is added to the node, the node also needs to be closed. Closing the node is done like this:

<item>

Either a new node can be opened now for the next set of data or the XML file can be closed. To close the XML file, first the channel needs to be closed by adding this line:

</channel>

The file is now complete and ready to be saved and processed.

An example XML file can look like this:

<channel> 
    <item>
        <product_sku>LAP01</product_sku>
        <product_name><![CDATA[Laptop Type 01]]></product_name> 
        <category_path>Computers/Laptops</category_path> 
    </item>
</channel>

This is a basic setup of an XML file. This example also shows the usage of the CDATA tag. This is a special tag and is used to tell the system that any data inside the CDATA tag is not to be read as XML data but as plain data. This is for example necessary when the data contains a special character like the ampersand (&). For full details, have a look at the Wikipedia XML page. On export, CSVI already adds the CDATA tag automatically to fields considered to usually have special characters. CSVI offers several XML export formats to serve for different shopping sites. These sites are:

• Beslist.nl
• Google Merchant

Each of these sites have their own XML schema and it is advised to read on how to use this. An example of this is the Google Base example template.

Advanced XML

CSVI can now import complex XML structures. To be able to import complex XML structures, you need to tell CSVI how your structure looks like. The structure is set in the XML Record Nodes field. This field must contain the blueprint of your XML structure.

Simple structure

The CSVI XML format uses a simple structure that looks like this:

<channel>
    <item>
        <product_sku></product_sku>
        <product_name></product_name> 
    </item>
</channel>

Every record is enclosed between the <item></item> tags. The XML Node field can then be filled like:

• <item></item>
• <item/> (self-closing)

Complex Structure

An XML file can also contain a complex structure like this:

<product>
    <id>A2045</id>
    <name>Great Product</name>
    <description_it>My great product</description_it>
    <price>10.52</price>
    <weight unit="kg">
        <unit>kg</unit>
    </weight>
    <images>
        <image1>myimage.jpg</image1>
    </images>
</product>

Every record is here enclosed between the <product></product> tags however the tagnames do not have a name according to the fields in the Available fields list. Further the image is contained in a subnode called <images>.

The field <weight unit="kg"> indicates there is a subnode called unit that is being matched to a fieldname called kg. Now the fieldname kg does not exist but it is called product_weight_uom. This we will need to adjust for the blueprint.

To make CSVI understand this format it is necessary to tell CSVI how to read the XML file. A blueprint of the above example will look like this:

<product> 
    <id>product_sku</id>
    <name>product_name</name>
    <description_it>product_desc</description_it>
    <price>product_price</price>
    <weight unit="product_weight_uom"></weight>
    <images>
        <image1>product_full_image</image1>
    </images>
</product>

The field to use must be placed between the node names for example <id>product_sku</id> will tell CSVI that the ID field is the product_sku field.

Special tags

Note: CSVI Pro 4.4 required

As of CSVI Pro 4.4, you can now also import XML structures with duplicate nodes by using special tags. These tags are:

• csvi="combine"
• csvi="add"

When using these special tags, you cannot use the template fields to match the structure of the XML file. However it is possible to add extra fields to the template and enable the option Add extra fields. These fields will be added to the end of each item. Give these fields a default value and they will be imported also. This can be used to publish your products immediately for example.

We will use this example node:

<product>
    <id>R254617</id>
    <name>Printer</name>
    <features>
    <feature>Multi-color - Yes</feature>
    <feature>Condition - Refurbished</feature>
    <feature>Speed - 5ppm</feature>
    </features>
    <images>
    <image id='1'>
    <url><![CDATA[http://www.example.com/image1.jpg]]></url>
    <primary>1</primary>
    </image>
    <image id='2'>
    <url><![CDATA[http://www.example.com/image2.jpg]]></url>
    <primary>0</primary>
    </image>
    </images>
</product>

Combine

The combine option is used to combine duplicate nodes into 1 field. Look at the example node, this printer has 3 features. The next printer in the import file might have 5 features. Since these features are variable, it is not possible to match them with different fields in CSVI. The combine option will make it possible to match them with 1 field, for example the product description. By setting the combine tag on the feature node, CSVI will merge all fields that match the <features><feature> path.

Add

The add option is used to import duplicate nodes into different fields. Look at the example node, this printer has 2 images. The add option will make it possible to match them with a field of your choice. By setting the add tag on the image node, CSVI will match all next nodes to the given fieldname. All fields that match the <images><image> path will be handled by the add option.

The blueprint for this XML node will look like this:

<product>
    <id>product_sku</id>
    <name>product_name</name>
    <features><feature csvi="combine">product_desc<feature></features>
    <images>
    <image id='skip'>
    <url csvi="add">file_url</url>
    <primary>skip</primary>
    </image>
    <image id='skip'>
    <url>file_url_thumb</url>
    <primary>skip</primary>
    </image>
    </images>
</product>

Custom XML

The custom XML export gives you the flexibility of exporting any kind of XML layout.

Setting Up The XML Layout

The XML layout has 3 parts that needs to be set up. The parts are:

• Header
• Body
• Footer

Header

The header contains the start of the XML file. Example:

<?xml version="1.0" encoding="UTF-8"?>
<channel>

Body

The body contains a single node that will be duplicated for every export item. A node is build up from several sections:

1. Opening tag
   The opening tag starts the node, for example: <product>
2. Fields
   The fields specify what information is going to be exported, for example:

   <id>[product_sku]</id>
   <name>[product_name]</name>
   <description_it>[product_desc]</description_it>
   <price>[product_price]</price>
   <weight unit="[product_weight_uom]">[product_weight]</weight> 
   <images> 
       <image1>[picture_url]</image1>
   </images>

   A field is constructed of 3 different parts:
   1. Start tag
      <id>
   2. Field to be exported. The field that is going to be exported must always be enclosed in square brackets.
      [product_sku]
   3. Closing tag
      <id>
3. Closing Tag
   The closing tag closes the node, for example: </product>

Each field that is going to be exported needs to be added to the list of fields to be exported on the Export tab. Example:

<product>
    <id>[product_sku]</id>
    <name>[product_name]</name>
    <description_it>[product_desc]</description_it>
    <price>[product_price]</price>
    <weight unit="[product_weight_uom]">[product_weight]</weight> 
    <images>
        <image1>[picture_url]</image1>
    </images>
</product>

Footer

The footer closes the XML file. Example:

</channel>

Output File

The above example will generate the following output file:

<channel>
    <product>
        <id>P01</id>
        <name><![CDATA[Chain Saw]]></name>
        <description_it><![CDATA[
<ul>
<li>Tool-free tensioner for easy, convenient chain adjustment </li>
<li>3-Way Auto Stop; stops chain a fraction of a second </li>
<li>Automatic chain oiler regulates oil for proper chain lubrication </li>
<li>Small radius guide bar reduces kick-back </li>
</ul>
<p><br /> <strong>Specifications</strong><br /> 12.5 AMPS   <br /> 16" Bar Length   <br /> 3.5 HP   <br /> 8.05 LBS. Weight</p>
]]></description_it>
        <price>2,99</price>
        <weight unit="pounds">10.0000</weight>
        <images>
            <image1>http://www.example.com/components/com_virtuemart/shop_image/product/c3a5bf074da14f30c849d13a2dd87d2c.jpg</image1>
        </images> 
    </product>
</channel>

Read more ...

28 July 2019 | RO CSVI

Set the absolute path of import file to load directly from server. The path will be set under Load from server field. Test Path button is used to check if the path is valid or not. This option is very useful when running the import as cron so RO CSVI can load the file automatically for cron import.

If the path is not a valid path, a message is shown as

If the path is a valid path, a message is shown as

Read more ...

30 July 2019 | RO CSVI

Updating CSVI is easy using Joomla installer.

Getting the Download ID

The first thing to get is the download ID. You can get the Download ID by following these steps:

1. Log in to the website https://rolandd.com
2. After you have logged in, click the My Subscriptions link
3. You will then find the Download ID for each subscription
   

Setting up the Download ID

With the Download ID, go to your website and follow these steps:

1. Go to Components -> and click on RO CSVI
2. You are now on the dashboard
3. Click on the Options icon in the toolbar
4. You can fill in the Download ID
   
5. Click on Save & Close
6. The Download ID is now set

Updating CSVI

You can now update CSVI using the Joomla updater.  Go to Joomla Extensions Menu >> Manage. Click on update on the left sidebar. New versions of RO CSVI will be listed here if available. 

Select the RO CSVI extension from the list and click on update button on top left corner.

If needed, click on the Find update Button to get the latest information.

After the update has finished you can return to RO CSVI.

Read more ...

04 December 2013 | RO CSVI

Often it is almost impossible to know if your CSV file has been encoded as UTF-8. Programs cannot tell you for certain because there is no setting in the file that contains this information. The closest to come to determining a file's encoding is an educated guess or ask the person who created the file. Usually the person creating the file doesn't know either. All is lost then? Not really, you can create your own file and save it with a known encoding.

The choice of spreadsheet in this case is OpenOffice or LibreOffice. If you use Excel to do all your work in, you are out of luck as Excel has no option for enforcing an encoding when saving a file as CSV. This does not mean you can no longer use Excel but when saving the file for CSV open your Excel file with OpenOffice or LibreOffice.

Start OpenOffice/LibreOffice

In this example I will be using LibreOffice (the screens are the same for OpenOffice).

Open the file

Click on Open and select the file on your computer that you want to save as UTF-8 encoded file.

Save the file

We are not going to use CTRL-S to quickly save the file but we choose File -> Save As (CTRL-SHIFT-S) and then you get this screen:

There are a few things that are important:

1. Give your file a name
2. Save as type must be set to Text CSV (.csv)
3. You must enable the Edit filter settings

After that is done click on Save.

Setting the filter settings

After you have clicked on Save, LibreOffice will ask you what settings you want to use for the file.

The character set must be set to Unicode (UTF-8) as this is what we want to achieve, a UTF-8 encoded file.

The field and text delimiter you can set as you wish or leave it as it is, all other settings can be left unchanged.

After that is done, click on OK.

You now have a UTF-8 encoded file.

Read more ...

19 November 2015 | RO CSVI

Required fields

• CSVI Pro 6.0+
• Joomla 2.5 /3.x

When an export template is created, in the fields tab, there are two options Group by and Sort by fields that can be set. Here we will explain what is the use and how to use them.

Group by Fields

Often when we do exporting data from database tables, there is always chance of seeing duplicate rows getting exported. By setting group by fields this can be avoided. Say for example, if we are exporting Virtuemart product and we need unique product name to be exported,  simply by setting the product_name field in group by field will do the trick.

Also, grouping will be done in the order of fields added. In this example  first grouping will be done using product_name and then with the retrieved result again grouping will be done with the second field, here it is category_id and so on. 

Multiple fields can be added/deleted by clicking "+/-" next to each field. Dont forget to save the fields by clciking Save button.

Sort by Fields

Not only we can group by data but we can even sort them as required. Sort by will sort string type fields in alphabetical order and by default in number type fields in ascending order. It depends on type of field added for sorting.

For example, in Virtuemart product export template to sort by product_name and product_price simply add the fields as shown. Multiple fields can be added/deleted  by clicking "+/-" next to each field

Same like groupby, sorting is also done based on the order of fields added. As per the example here Sorting is first done using product_name field and the result will be again sorted using product_price fields and so on.

Read more ...