How can I do date-like filtering on ProductStoreShipmentMeth?
I see no fromDate/thruDate fields in ProductStoreShipmentMeth, ShipmentCostEstimate, CarrierShipmentMethod, nor ShipmentMethodType. How can I handle the cost estimates changing in the future, how can I cycle out old values, while still maintaining any existing database references? |
Hi Adam,
Go to catalog >> stores >> select a store say 9000 Go to Shipping we can remove the product store shipping association which will not expires but delete the record. Go to Shipping Estimates will give you opportunity to change the estimates. I think these business process will be able to handle all the scenarios you are talking about. Rishi Solanki Enterprise Software Developer HotWax Media Pvt. Ltd. On Tue, Mar 9, 2010 at 5:25 AM, Adam Heath <[hidden email]> wrote: > How can I do date-like filtering on ProductStoreShipmentMeth? > > I see no fromDate/thruDate fields in ProductStoreShipmentMeth, > ShipmentCostEstimate, CarrierShipmentMethod, nor ShipmentMethodType. > > How can I handle the cost estimates changing in the future, how can I > cycle out old values, while still maintaining any existing database > references? > |
Rishi Solanki wrote:
> Hi Adam, > Go to catalog >> stores >> select a store say 9000 > Go to Shipping we can remove the product store shipping association which > will not expires but delete the record. > Go to Shipping Estimates will give you opportunity to change the estimates. > I think these business process will be able to handle all the scenarios you > are talking about. Well, I'd like to see what the values were in the past, for historical reasons. This could be done like any other date-filter based entity. I do see that ProductStoreShipmentMeth(and it's ShipmentCostEstimate) is only used to provide a list of available shipment types, and once the order is created, it is never used again. OrderItemShipGroup just references CarrierShipmentMethod. I don't like deleting ProductStoreShipmentMeth. |
There are several entities which have from and thru date attributes but they
can be enable the record again in future. But once the shipment estimates is increase or company stop to use any shipment method due to any reason then record for them is none of use for the company. It is just my opinion because I'm not able to see the use of which shipment method company uses in past wanna to look at. I'm for the existing handling if it will change then also I do not have any problem, but I believe the OFBiz Data Model is design in such manner that all generic requirements can be handle using it. If we are changing it then it is our specific wish or requirement. Rishi Solanki Enterprise Software Developer HotWax Media Pvt. Ltd. On Tue, Mar 9, 2010 at 10:26 PM, Adam Heath <[hidden email]> wrote: > Rishi Solanki wrote: > > Hi Adam, > > Go to catalog >> stores >> select a store say 9000 > > Go to Shipping we can remove the product store shipping association which > > will not expires but delete the record. > > Go to Shipping Estimates will give you opportunity to change the > estimates. > > I think these business process will be able to handle all the scenarios > you > > are talking about. > > Well, I'd like to see what the values were in the past, for historical > reasons. This could be done like any other date-filter based entity. > > I do see that ProductStoreShipmentMeth(and it's ShipmentCostEstimate) > is only used to provide a list of available shipment types, and once > the order is created, it is never used again. OrderItemShipGroup just > references CarrierShipmentMethod. > > I don't like deleting ProductStoreShipmentMeth. > |
Free forum by Nabble | Edit this page |