Hello,

I have created 2 importers (one for products and one for product nodes).
I run importer for products and it's creating my products without any issues.
I run importer for product nodes and it's not throwing any errors and I can see in the database that the nodes have been created.
But I can't see the product nodes in /admin/commerce/products.

Since /admin/commerce/products is actually the view Commerce Backoffice: Products (Content), I tried to check there what is the problem.
And here is the error: SQLSTATE[42000]: [Microsoft][SQL Server Native Client 10.0][SQL Server]Column 'node.title' is invalid in the select list because it is not contained in either an aggregate function or the GROUP BY clause.

If I remove the Content: Product relationship then there is no error thrown and the view works.
If I put back the relationship the above error is showing up and the view is not working.

So I guess my importers are missing something.
I have mapped SKU for GUID for both products and product nodes (set unique for both as well) and also for product nodes I have mapped SKU to Product: SKU.
Is there anything I'm missing here?
Do I need to have a special mapping for this to work?

Comments

virusakos’s picture

I have tried my importers and the CSV with my data on a commerce kickstart installation using mysql and everything works fine.
The installation I'm having issues with is not a commerce kickstart installation and it's using sqlserver.
I will try to have a commerce kickstart installation using sqlserver to see if there is a compatibility issue with the database.
If it's not a database compatibility issue then probably it's a configuration issue.

virusakos’s picture

Status: Active » Closed (works as designed)

I have tested my scenario with commerce kickstart installation using sqlserver database.
I get the sql error mentioned in my first post.
So it looks like a database compatibility issue of Commerce Backoffice (or rather compatibility issue with Views).
Not a bug in commerce feeds.

ndiSIGN’s picture

Hi, although watching the video (https://vimeo.com/22731881) on how to set up both importers, i've still been struggling a while with this getting to work properly also.

At first I was getting the [Not Importing: Required product SKU is missing], everything in the CSV file and mapping was set up the right way. This was proven right once I changed the delimiter from , into ; and the product import error message dissapeared. It suprised me to find out a comma seperated value could be devided by ; from default.

But then I could not find the products in the product list. A quick look in the Database showed me the new products, so why didn't they show up in the backend. After a while I noticed the tab [Display Manager] on the admin/commerce/products page. At the bottom of this list I found, by accident, my newly imported products. You can Edit (this you can use to check your mapping settings) or Delete them. The header of this section of the list is called: Products not assigned to any display mode. So they do exist, but won't show up because the import proces is not finished yet. You need the display importer also.

After importing the product display I ended up with some nodes, but without a product connection. The imported products from the previous step, stayed in the [Display Manager] list. I could open the nodes in the backend and everything (from the node) was imported correctly (if not, you can use this check to fintune your mapping), but the product info was still missing from the node.

I already mapped the Product SKU (sku) to the sku (in the CSV file) and made this Unique in the Product importer.
In the Display importer, I mapped the GUID (guid) to the sku (in the CSV) and made this one also Unique, but still no connection.

Then I read something about mapping the sku to the SKU in Display importer, so I added [Product(s): SKU (field_product:sku)] and mapped it to the sku (in the CSV) and it suddenly worked. The products where moved to the product list and the product info was present in the fields in the display node.

Hopefully somebody finds this helpfull.