Value of QuantityBreak and QuantityBreakType entities?

2014-03-24 Thread Christian Carlow
Can someone explain the value of the QuantityBreak and QuantityBreakType 
entities?  Is the QuantityBreakType entity necessary?  Why wouldn't the 
same quantity range be used regardless of the break types?  Also, I 
noticed that the Shipping Estimates tab on the Catalog-Store app 
doesn't even reuse existing quantityBreaks with the same range and 
type.  Isn't the point of having the QuanitityBreak entity to reuse the 
ids existing ranges? I'm trying to implement quantity ranges for 
QuoteItems and the QuantityBreak entities are introducing more 
complexity than seems necessary.  I think I remember someone mentioning 
on JIRA that QuantityBreaks were something that should possibly be 
cleaned up.


Re: Value of QuantityBreak and QuantityBreakType entities?

2014-03-24 Thread Jacques Le Roux

I think this seed data give an idea of what is QuantityBreakType and 
QuantityBreak

QuantityBreakType description=Shipping Weight Break 
quantityBreakTypeId=SHIP_WEIGHT/
QuantityBreakType description=Shipping Quantity Break 
quantityBreakTypeId=SHIP_QUANTITY/
QuantityBreakType description=Shipping Price Break 
quantityBreakTypeId=SHIP_PRICE/
QuantityBreakType description=Price Component Quantity Break 
quantityBreakTypeId=QUANTITY/
QuantityBreakType description=Price Component Order Value Break 
quantityBreakTypeId=ORDER_VALUE/

For me it comes down to this http://markmail.org/message/bta245fsl7nylkuj
But I could be wrong, I never used QuantityBreakType and QuantityBreak in 
production. Seems Nicolas has a clear idea about it

Jacques

Le 24/03/2014 13:43, Christian Carlow a écrit :
Can someone explain the value of the QuantityBreak and QuantityBreakType entities?  Is the QuantityBreakType entity necessary?  Why wouldn't the 
same quantity range be used regardless of the break types?  Also, I noticed that the Shipping Estimates tab on the Catalog-Store app doesn't even 
reuse existing quantityBreaks with the same range and type.  Isn't the point of having the QuanitityBreak entity to reuse the ids existing ranges? 
I'm trying to implement quantity ranges for QuoteItems and the QuantityBreak entities are introducing more complexity than seems necessary.  I think 
I remember someone mentioning on JIRA that QuantityBreaks were something that should possibly be cleaned up.