Developer forum

Hi Casper,

 Do you have a group hierarchy, or just a flat structure directly below the shop?

Regards /Snedker

Hi Morten

Our group hierarcy is like this:

- Catalogue
   - Main group 1
      - Sub group 1.1
      - Sub group 1.2
      - Sub group 1.3
   - Main group 2
      - Sub group 2.1
      - Sub group 2.2

The products is placed in the sub groups. Each main group has a unique set of category fields (Product Category), which is used for all underlying sub groups. And for each sub group we have an CSV data file with products, including category field data (each category field has it's own column in the CSV).

Best regards
Casper

If you have nested groups you'll need two CSV's: one with products, another with groups:

 

PRODUCTS

ProductID;This;That;Groups

12345;value 1;value 2;My Group

 

GROUPS

GroupID;GroupName;ParentGroups

1;Parent;

10;My Group;1

 

In the column Groups of the products.csv, you may reference either the group name or the groupID. However, if referencing group name it will take use of the first group it finds with that name. So if you have multiple groups with same name you should reference the Id of the group.

 

Let me know if this helps.

 

Regards /Snedker

Hi Morten,

Thanks.

I understand your suggestion - that will work fine.

But my problem is the import of category group field values.

My CSV files hold all the data including category field values, in seperate columns, but how do I map these data into eCom products? The eCom product table holds only one single XML based coulm for "ProductCategoryFieldValues" - but in my CSV these values has seperate columns (no XML). It seems very cumbersome, if I first have to convert all of these category fields into XML, before I can start the import with the Data Integration module?

Best regards,
Casper Stendal

 Hi Casper,

 

Unfortunately we don't support this in an intuitive way.

 

The ProductCategoryFieldValues are stored as XML in the column of the same name. The only way for you to import this information, is to have the entire XML in a CSV column.

 

But we are aware of the problem, and in a later DW release we will change this, so that ProductCategoryFieldValues are moved to table structure instead. This will probably not be until the release following 8.2.

Regards /Snedker

Hi again,

Thanks for your explanation - now my headache has decreased a little.

Even though the problem is still there, it's nice to know that it's not just me, who couldn't find the solution.

What would be your rough estimate for a DW release, with the new and optimized table structure? 1, 2, 3, 6 or 12 month?

Best regards,
Casper Stendal