I have product definition with couple of variant property. Now I have situation where some products wont have any variants but I want to create them usign above product definition is this possible ? or I must create additionaly product definition which have the same properties but non of them are variant ?
Unless Soren knows better (and he usually does) I think you will have to recreate the product definitions as non-variant properties and assign the product to that definition.
hi, we are using a syncscript in C# for this so creating a different Product Definition would make it difficult when a product suddenly gets a new variant we need to change the product definition. That's why we decided to always create a model and a variant for every product.
In fact we don't need to create variants if we just create a new product for every product/variant. The disadvantage of this solution is that we need to reinvent the variants system ourselfs in code.
Do you think creating variants for every product will result in some bad consequences? What are the best practices with variants? We want pictures with every variant so we are putting all the images in the media folder with some properties on them to link the images to the right product.
As long as you don't create any variants on the product you should be fine. The safest approach is to create two separate definitions, but as I mention it should work.
Product Family instance
Hi,
I have product definition with couple of variant property. Now I have situation where some products wont have any variants but I want to create them usign above product definition is this possible ? or I must create additionaly product definition which have the same properties but non of them are variant ?
Unless Soren knows better (and he usually does) I think you will have to recreate the product definitions as non-variant properties and assign the product to that definition.
hi, we are using a syncscript in C# for this so creating a different Product Definition would make it difficult when a product suddenly gets a new variant we need to change the product definition. That's why we decided to always create a model and a variant for every product.
In fact we don't need to create variants if we just create a new product for every product/variant. The disadvantage of this solution is that we need to reinvent the variants system ourselfs in code.
Do you think creating variants for every product will result in some bad consequences? What are the best practices with variants? We want pictures with every variant so we are putting all the images in the media folder with some properties on them to link the images to the right product.
Thanks
As long as you don't create any variants on the product you should be fine. The safest approach is to create two separate definitions, but as I mention it should work.
is working on a reply...