On 8/15/16 13:03, Taher Alkhateeb wrote:
values do not change (the description remains the same and everything
else). So the logic around receiving input from users, validating it,
storing it, and fetching it later adds complexity that does not exist with
system-defined values.
Taher,
Thank
On 8/14/16 01:07, Taher Alkhateeb wrote:
I think perhaps what you are seeking is not related to the product data
model, instead, it is related to order.
Now, in your case this might be a bit too custom for your needs. I'm not
sure but I would suggest to store such values in OrderItemAttribute
A model question from the OfBizDatamodelBook PDFs and
https://cwiki.apache.org/confluence/display/OFBENDUSER/Product+Features
I believe I understand I can have a ProductFeatureType of "Brand" with
ProductFeatures of Hanes, American Apparel and Lacoste that could be
related to my Product.
Thanks Pierre and Taher for your responses, a couple of follow-ups below:
On 8/9/16 01:44, Pierre Smits wrote:
The one thing is related to creating a unique key based on the fromDate in
combination with the other elements of the primary key. As an example, have
a look at the following
I'm a big fan of Silverston and his UDM books and have been studying OfBiz
extensively. I was wondering if anyone can explain why his entities with
from/thru date use the from date instead of the thru date in the composite
keys? It seems like you would want to enforce only one version is ever
