OFBiz › OFBiz - User

feature category and feature configuration

‹ Previous Topic Next Topic ›
 
classic Classic list List threaded Threaded
♦
♦
 6 messages Options
Wai
Reply | Threaded
Open this post in threaded view
♦
♦
|

feature category and feature configuration

Wai
Take for example I have the following virtual products and associated variants with the shown features

polo shirt
  color:
      red...price $1
      green...price $2
  size:
      small...price $3
      medium...price $4
clown shirt
  color:
      red...price $5
      green...price $6
  size:
      small...price $7
      medium...price $8
dress pant
  color:
      red...price $9
      green...price $10
  size:
      small...price $11
      medium...price $12

All of these product variants use the same similar product feature categories 'color' and 'size' and the features have differing pricing depending on what virtual product it applies to.  Does that mean it is necessary to create separate feature categories and associated features for Polo shirt, Clown shirt, and dress pant as specified below?

ProductFeatureCategory:
  POLOSHIRT_COLOR
ProductFeature:
  POLOSHIRT_COLOR_RED
  POLOSHIRT_COLOR_GREEN
  POLOSHIRT_SIZE_SMALL
  POLOSHIRT_SIZE_MEDIUM

ProductFeatureCategory:
  CLOWNSHIRT_COLOR
ProductFeature:
  CLOWNSHIRT_COLOR_RED
  CLOWNSHIRT_COLOR_GREEN
  CLOWNSHIRT_SIZE_SMALL
  CLOWNSHIRT_SIZE_MEDIUM

ProductFeatureCategory:
  DRESSPANT_COLOR
ProductFeature:
  DRESSPANT_COLOR_RED
  DRESSPANT_COLOR_GREEN
  DRESSPANT_SIZE_SMALL
  DRESSPANT_SIZE_MEDIUM

If the above configuration is correct, does that imply that in practice, features and feature categories easily grow to be very large and difficult to manage?

Thanks
Wai
BJ Freeman
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: feature category and feature configuration

BJ Freeman
take a look at
http://demo-trunk.ofbiz.apache.org/ecommerce/products/200/202/p_WG-9943
and
https://demo-trunk.ofbiz.apache.org/catalog/control/EditProductAssoc?productId=WG-9943

=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation  <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com  <http://www.specialtymarket.com/>

Systems Integrator-- Glad to Assist

Chat  Y! messenger: bjfr33man
Linkedin
<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>


Wai Tam sent the following on 6/29/2010 11:58 AM:

>
> Take for example I have the following virtual products and associated
> variants with the shown features
>
> polo shirt
>    color:
>        red...price $1
>        green...price $2
>    size:
>        small...price $3
>        medium...price $4
> clown shirt
>    color:
>        red...price $5
>        green...price $6
>    size:
>        small...price $7
>        medium...price $8
> dress pant
>    color:
>        red...price $9
>        green...price $10
>    size:
>        small...price $11
>        medium...price $12
>
> All of these product variants use the same similar product feature
> categories 'color' and 'size' and the features have differing pricing
> depending on what virtual product it applies to.  Does that mean it is
> necessary to create separate feature categories and associated features for
> Polo shirt, Clown shirt, and dress pant as specified below?
>
> ProductFeatureCategory:
>    POLOSHIRT_COLOR
> ProductFeature:
>    POLOSHIRT_COLOR_RED
>    POLOSHIRT_COLOR_GREEN
>    POLOSHIRT_SIZE_SMALL
>    POLOSHIRT_SIZE_MEDIUM
>
> ProductFeatureCategory:
>    CLOWNSHIRT_COLOR
> ProductFeature:
>    CLOWNSHIRT_COLOR_RED
>    CLOWNSHIRT_COLOR_GREEN
>    CLOWNSHIRT_SIZE_SMALL
>    CLOWNSHIRT_SIZE_MEDIUM
>
> ProductFeatureCategory:
>    DRESSPANT_COLOR
> ProductFeature:
>    DRESSPANT_COLOR_RED
>    DRESSPANT_COLOR_GREEN
>    DRESSPANT_SIZE_SMALL
>    DRESSPANT_SIZE_MEDIUM
>
> If the above configuration is correct, does that imply that in practice,
> features and feature categories easily grow to be very large and difficult
> to manage?
>
> Thanks
> Wai
>

BJ Freeman
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: feature category and feature configuration

BJ Freeman
forgot this link
https://demo-trunk.ofbiz.apache.org/catalog/control/EditProductFeatures?productId=WG-9943

=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation  <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com  <http://www.specialtymarket.com/>

Systems Integrator-- Glad to Assist

Chat  Y! messenger: bjfr33man
Linkedin
<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>


BJ Freeman sent the following on 6/29/2010 1:26 PM:

> take a look at
> http://demo-trunk.ofbiz.apache.org/ecommerce/products/200/202/p_WG-9943
> and
> https://demo-trunk.ofbiz.apache.org/catalog/control/EditProductAssoc?productId=WG-9943
>
>
> =========================
> BJ Freeman
> http://bjfreeman.elance.com
> Strategic Power Office with Supplier Automation
> <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
> Specialtymarket.com <http://www.specialtymarket.com/>
>
> Systems Integrator-- Glad to Assist
>
> Chat Y! messenger: bjfr33man
> Linkedin
> <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>
>
>
>
> Wai Tam sent the following on 6/29/2010 11:58 AM:
>>
>> Take for example I have the following virtual products and associated
>> variants with the shown features
>>
>> polo shirt
>> color:
>> red...price $1
>> green...price $2
>> size:
>> small...price $3
>> medium...price $4
>> clown shirt
>> color:
>> red...price $5
>> green...price $6
>> size:
>> small...price $7
>> medium...price $8
>> dress pant
>> color:
>> red...price $9
>> green...price $10
>> size:
>> small...price $11
>> medium...price $12
>>
>> All of these product variants use the same similar product feature
>> categories 'color' and 'size' and the features have differing pricing
>> depending on what virtual product it applies to. Does that mean it is
>> necessary to create separate feature categories and associated
>> features for
>> Polo shirt, Clown shirt, and dress pant as specified below?
>>
>> ProductFeatureCategory:
>> POLOSHIRT_COLOR
>> ProductFeature:
>> POLOSHIRT_COLOR_RED
>> POLOSHIRT_COLOR_GREEN
>> POLOSHIRT_SIZE_SMALL
>> POLOSHIRT_SIZE_MEDIUM
>>
>> ProductFeatureCategory:
>> CLOWNSHIRT_COLOR
>> ProductFeature:
>> CLOWNSHIRT_COLOR_RED
>> CLOWNSHIRT_COLOR_GREEN
>> CLOWNSHIRT_SIZE_SMALL
>> CLOWNSHIRT_SIZE_MEDIUM
>>
>> ProductFeatureCategory:
>> DRESSPANT_COLOR
>> ProductFeature:
>> DRESSPANT_COLOR_RED
>> DRESSPANT_COLOR_GREEN
>> DRESSPANT_SIZE_SMALL
>> DRESSPANT_SIZE_MEDIUM
>>
>> If the above configuration is correct, does that imply that in practice,
>> features and feature categories easily grow to be very large and
>> difficult
>> to manage?
>>
>> Thanks
>> Wai
>>
>
>

Wai
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: feature category and feature configuration

Wai
In reply to this post by Wai
Hello,

Any takers for this question?

Thanks,
Wai
----------------------
Take for example I have the following virtual products and associated variants with the shown features

polo shirt
  color:
      red...price $1
      green...price $2
  size:
      small...price $3
      medium...price $4
clown shirt
  color:
      red...price $5
      green...price $6
  size:
      small...price $7
      medium...price $8
dress pant
  color:
      red...price $9
      green...price $10
  size:
      small...price $11
      medium...price $12

All of these product variants use the same similar product feature categories 'color' and 'size' and the features have differing pricing depending on what virtual product it applies to.  Does that mean it is necessary to create separate feature categories and associated features for Polo shirt, Clown shirt, and dress pant as specified below?

ProductFeatureCategory:
  POLOSHIRT_COLOR
ProductFeature:
  POLOSHIRT_COLOR_RED
  POLOSHIRT_COLOR_GREEN
  POLOSHIRT_SIZE_SMALL
  POLOSHIRT_SIZE_MEDIUM

ProductFeatureCategory:
  CLOWNSHIRT_COLOR
ProductFeature:
  CLOWNSHIRT_COLOR_RED
  CLOWNSHIRT_COLOR_GREEN
  CLOWNSHIRT_SIZE_SMALL
  CLOWNSHIRT_SIZE_MEDIUM

ProductFeatureCategory:
  DRESSPANT_COLOR
ProductFeature:
  DRESSPANT_COLOR_RED
  DRESSPANT_COLOR_GREEN
  DRESSPANT_SIZE_SMALL
  DRESSPANT_SIZE_MEDIUM

If the above configuration is correct, does that imply that in practice, features and feature categories easily grow to be very large and difficult to manage?

Thanks
Wai
BJ Freeman
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: feature category and feature configuration

BJ Freeman
data model book Vol I page 76-79.


=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation  <http://www.businessesnetwork.com/automation/viewforum.php?f=52>
Specialtymarket.com  <http://www.specialtymarket.com/>

Systems Integrator-- Glad to Assist

Chat  Y! messenger: bjfr33man
Linkedin
<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>


Wai Tam sent the following on 6/30/2010 8:13 AM:

>
> Hello,
>
> Any takers for this question?
>
> Thanks,
> Wai
> ----------------------
> Take for example I have the following virtual products and associated
> variants with the shown features
>
> polo shirt
>    color:
>        red...price $1
>        green...price $2
>    size:
>        small...price $3
>        medium...price $4
> clown shirt
>    color:
>        red...price $5
>        green...price $6
>    size:
>        small...price $7
>        medium...price $8
> dress pant
>    color:
>        red...price $9
>        green...price $10
>    size:
>        small...price $11
>        medium...price $12
>
> All of these product variants use the same similar product feature
> categories 'color' and 'size' and the features have differing pricing
> depending on what virtual product it applies to.  Does that mean it is
> necessary to create separate feature categories and associated features for
> Polo shirt, Clown shirt, and dress pant as specified below?
>
> ProductFeatureCategory:
>    POLOSHIRT_COLOR
> ProductFeature:
>    POLOSHIRT_COLOR_RED
>    POLOSHIRT_COLOR_GREEN
>    POLOSHIRT_SIZE_SMALL
>    POLOSHIRT_SIZE_MEDIUM
>
> ProductFeatureCategory:
>    CLOWNSHIRT_COLOR
> ProductFeature:
>    CLOWNSHIRT_COLOR_RED
>    CLOWNSHIRT_COLOR_GREEN
>    CLOWNSHIRT_SIZE_SMALL
>    CLOWNSHIRT_SIZE_MEDIUM
>
> ProductFeatureCategory:
>    DRESSPANT_COLOR
> ProductFeature:
>    DRESSPANT_COLOR_RED
>    DRESSPANT_COLOR_GREEN
>    DRESSPANT_SIZE_SMALL
>    DRESSPANT_SIZE_MEDIUM
>
> If the above configuration is correct, does that imply that in practice,
> features and feature categories easily grow to be very large and difficult
> to manage?
>
> Thanks
> Wai

Scott Gray-2
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: feature category and feature configuration

Scott Gray-2
In reply to this post by Wai
Have you tried setting the amount field on the ProductFeatureAppl records?  There really isn't any need to have separate features that represent the same thing just to get separate prices.

Regards
Scott

HotWax Media
http://www.hotwaxmedia.com

On 1/07/2010, at 3:13 AM, Wai Tam wrote:

>
> Hello,
>
> Any takers for this question?
>
> Thanks,
> Wai
> ----------------------
> Take for example I have the following virtual products and associated
> variants with the shown features
>
> polo shirt
>  color:
>      red...price $1
>      green...price $2
>  size:
>      small...price $3
>      medium...price $4
> clown shirt
>  color:
>      red...price $5
>      green...price $6
>  size:
>      small...price $7
>      medium...price $8
> dress pant
>  color:
>      red...price $9
>      green...price $10
>  size:
>      small...price $11
>      medium...price $12
>
> All of these product variants use the same similar product feature
> categories 'color' and 'size' and the features have differing pricing
> depending on what virtual product it applies to.  Does that mean it is
> necessary to create separate feature categories and associated features for
> Polo shirt, Clown shirt, and dress pant as specified below?
>
> ProductFeatureCategory:
>  POLOSHIRT_COLOR
> ProductFeature:
>  POLOSHIRT_COLOR_RED
>  POLOSHIRT_COLOR_GREEN
>  POLOSHIRT_SIZE_SMALL
>  POLOSHIRT_SIZE_MEDIUM
>
> ProductFeatureCategory:
>  CLOWNSHIRT_COLOR
> ProductFeature:
>  CLOWNSHIRT_COLOR_RED
>  CLOWNSHIRT_COLOR_GREEN
>  CLOWNSHIRT_SIZE_SMALL
>  CLOWNSHIRT_SIZE_MEDIUM
>
> ProductFeatureCategory:
>  DRESSPANT_COLOR
> ProductFeature:
>  DRESSPANT_COLOR_RED
>  DRESSPANT_COLOR_GREEN
>  DRESSPANT_SIZE_SMALL
>  DRESSPANT_SIZE_MEDIUM
>
> If the above configuration is correct, does that imply that in practice,
> features and feature categories easily grow to be very large and difficult
> to manage?
>
> Thanks
> Wai
> --
> View this message in context: http://ofbiz.135035.n4.nabble.com/feature-category-and-feature-configuration-tp2272592p2272736.html
> Sent from the OFBiz - User mailing list archive at Nabble.com.


smime.p7s (3K) Download Attachment
Free forum by Nabble Edit this page