[jira] Created: (OFBIZ-735) Change to the pk of ProductStoreShipmentMeth and related logic

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (OFBIZ-735) Change to the pk of ProductStoreShipmentMeth and related logic

Nicolas Malin (Jira)
Change to the pk of ProductStoreShipmentMeth and related logic
--------------------------------------------------------------

                 Key: OFBIZ-735
                 URL: https://issues.apache.org/jira/browse/OFBIZ-735
             Project: OFBiz (The Open for Business Project)
          Issue Type: Improvement
          Components: product
            Reporter: Jacopo Cappellato
         Assigned To: Jacopo Cappellato
            Priority: Minor


I will contribute soon an major change for the ProductStoreShipmentMeth entity and related business logic.

Change the primary key of the ProductStoreShipmentMeth from:

productStoreId
shipmentMethodTypeId
partyId
roleTypeId

to:

productStoreShipMethId (new field)

I did it some time ago for a customer with the need to express rather complex shipping rules where:

1) the order amount was used to determine the shipping cost estimate
2) the postal address and weight were used to select the available shipping options

For #1 the existing shipping estimate and quantity breaks entities were perfect.
For #2 I had to change the primary key for the ProductStoreShipmentMeth entity because I had to associate the same "shipment method|carrier" to the store many times for different combinations of geo and weight.

For example:
* USPS is available in NY if weight is less than 30kg
* UPS is available in NY if weight is more than 30kg
* UPS is the only available method in LA
etc...

I will commit a patch that it will address all the business logic changes (and ui changes) needed to support the different pk (that are really very few); and the modified system is much more flexible and is working fine.


--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Closed: (OFBIZ-735) Change to the pk of ProductStoreShipmentMeth and related logic

Nicolas Malin (Jira)

     [ https://issues.apache.org/jira/browse/OFBIZ-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacopo Cappellato closed OFBIZ-735.
-----------------------------------

    Resolution: Fixed

This is now implemented in rev. 511250

> Change to the pk of ProductStoreShipmentMeth and related logic
> --------------------------------------------------------------
>
>                 Key: OFBIZ-735
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-735
>             Project: OFBiz (The Open for Business Project)
>          Issue Type: Improvement
>          Components: product
>            Reporter: Jacopo Cappellato
>         Assigned To: Jacopo Cappellato
>            Priority: Minor
>
> I will contribute soon an major change for the ProductStoreShipmentMeth entity and related business logic.
> Change the primary key of the ProductStoreShipmentMeth from:
> productStoreId
> shipmentMethodTypeId
> partyId
> roleTypeId
> to:
> productStoreShipMethId (new field)
> I did it some time ago for a customer with the need to express rather complex shipping rules where:
> 1) the order amount was used to determine the shipping cost estimate
> 2) the postal address and weight were used to select the available shipping options
> For #1 the existing shipping estimate and quantity breaks entities were perfect.
> For #2 I had to change the primary key for the ProductStoreShipmentMeth entity because I had to associate the same "shipment method|carrier" to the store many times for different combinations of geo and weight.
> For example:
> * USPS is available in NY if weight is less than 30kg
> * UPS is available in NY if weight is more than 30kg
> * UPS is the only available method in LA
> etc...
> I will commit a patch that it will address all the business logic changes (and ui changes) needed to support the different pk (that are really very few); and the modified system is much more flexible and is working fine.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.