Project:
| View Revisions: Issue #31901 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0031901: decimal value can't be changed by trigger/observer after manual edition in form view | ||
| Revision | 2016-01-19 11:07 by alostale | ||
| Steps To Reproduce | 1. Install attached module [1] 2. Open Platform Issues window 3. In form view create a new record and save (leave all fields as empty) 4. Edit description and save -> all 4 numeric fields are set to 0: OK (trigger and observer set 0) 5. Edit the 4 numeric fields setting 100 to all of them and save -> all 4 numeric fields are updated to 110: OK (trigger and observer add 10 to current value) 6. Edit description and save -> decimal fields (BD1 and BD2) remain as 110: ERROR they should have been updated to 120, note N1 and N2 value is now 120 7. Any subsequent description update remains these fields with 110 value -> ERROR: they should be updated on each description modification as N1 and N2 do Observe that: * Request for step 4 does not send textualValue for numeric fields as they have not been edited yet * Request for step 5 sends 100 as textualValue * Subsequent requests send 100 as textualValue [1] Module description Adds simple window (Platform issues) with 4 numeric fields * N1 Integer: updated on each modification by an persistence event observer * N2 Integer: updated on each modification by a trigger * BD1 BigDecimal: updated on each modification by an persistence event observer * BD2 BigDecimal: updated on each modification by a trigger |
||
| Revision | 2016-01-18 21:29 by rbianchini | ||
| Steps To Reproduce | 1 - Add the event handler attached to modules folder, add the src folder to buildpath and compile. 2 - Enabling some elements used by the Event Handler 2.A - Enable the "UOM" tab in "Product" window 2.B - Select the product "Red Wine" and add the "Kilogram" uom in the new tab "UOM" 2.C - Enable the "Conversion" tab in "Unit Of Measure" window 2.D - In "Unit Of Measure" window, select the "Unit" UOM and in the "Conversion" tab, add a conversion to "Kilogram" 2.E - Enable the fields "Order UOM" and "Order Quantity" in "Sales Order Line" tab 2.F - Delete the call out associated to the field "Order Quantity" in "Sales Order Line" tab 3 - Creating the Sales Order and reproducing the bug 3.1 - Create a new "Sales Order" 3.2 - Create a new "Sales Order Line" with: Product = "Red Wine", Ordered Quantity = 50, Order UOM = "Kilogram", Order quantity 60 and save it 3.3 - Modify the "Order Quantity", set to 61 and save (Observes that the "Ordered Quantity" has changed to 60) 3.4 - Modifi again the "Order Quantity", set to 80 and save ERROR: Observe that the "Ordered Quantity" has change to 50 and "Order Quantity" to 51 (the initial state) The event.currentstate in the second execution is wrong. (see the If you refresh the window or you change the tab between modifications, the issue don't occurr. See the video: https://drive.google.com/open?id=0BzLQwOL5Uu8zdlQ3bElFTXV6XzA [^] |
||
| Revision | 2016-01-15 13:27 by rbianchini | ||
| Steps To Reproduce | Add the event handler attached to modules folder, add the src folder to buildpath and compile. Enable the UOM tab in product window select the product Red Wine and add the kilogram uom in the new tab UOM Enable tab conversion in unit of measure window select the unit UOM and in the conversion tab, add a conversion to kilogram Enable the fields order UOM and Order Quantity in sales order line tab delete the Order Quantity's call out create a new sales order create a new line with product = red wine, orderer quantity = 50, Order UOM = kilogram, Order quantity 60 and save it modify the Order Quantity, set to 61 and save Observes that the Ordered Quantity has changed to 60 modifi again the order quantity, set to 80 and save ERROR: observe that the ordered quantity has change to 50 and order quantity to 51 (the initial state) The event.currentstate is wrong. If you refresh the window or you change the tab, the issue don't occur |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |