Hi Adrian, Why not replace it with a ProductFeatureContent entity (PK=productFeatureId:contentId:fromDate), that would follow the pattern commonly used throughout OFBiz.
Regarding your example, it would seem more appropriate to link your images directly to the product, I don't see the justification for needing to link it to the product feature. Even if you justify it, the best place for meeting that need would probably be the ProductFeatureAppl entity. I'm not a huge fan of overly flexible entity definitions because they can lead to inconsistent usage across the codebase as different developers shoehorn it to fit their specific use cases. Regards Scott On 19/07/2011, at 12:22 AM, Adrian Crum wrote: > I would like to use the ProductFeatureDataResource entity to connect an image > to a product feature, but I don't see how that can be done with the way the > ProductFeatureDataResource entity is constructed. There seem to be fields > missing, and the way the primary key is set up there is no way to connect a > data resource to a product + product feature combination. > > Example: I have two products - 8 1/2 by 11 paper and a ball point pen. I also > have a product feature - color: blue. I need to link product 8 1/2 by 11 > paper + color blue to an image of blue paper, and I need to link product ball > point pen + color blue to an image of a blue ball point pen. The current > ProductFeatureDataResource entity does not support that. > > It seems to me this entity should be set up more like the PRICE COMPONENT > entity in the DMRB - where various fields can be filled in to connect a data > resource to a product, or a product feature, or product + product feature, or > other combinations of product/order related criteria. > > A better version of the ProductFeatureDataResource entity might be: > > prodFeatDataResId* id-ne > dataResourceId id-ne > productId id > productFeatureId id > productCategoryId id > geoId id > partyId id > partyTypeId id > fromDate date-time > thruDate date-time > > This version would meet the needs of my example, plus it provides the > flexibility to connect data resources to other combinations of product/order > related data. > > What do you think? > > -Adrian >
smime.p7s
Description: S/MIME cryptographic signature
