Openbravo Issue Tracking System - Openbravo ERP | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0033432 | Openbravo ERP | A. Platform | public | 2016-07-05 13:37 | 2022-02-01 08:09 |
| Reporter | NaroaIriarte | ||||
| Assigned To | Triage Platform Base | ||||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | acknowledged | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Review Assigned To | |||||
| OBNetwork customer | |||||
| Web browser | |||||
| Modules | Core | ||||
| Support ticket | |||||
| Regression level | |||||
| Regression date | |||||
| Regression introduced in release | |||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0033432: Wrong data can be saved when using fields with display logic. | ||||
| Description | If there is a field with a display logic, it can occur that sometimes wrong data is saved in some records. If for example there is a field "A" which has a display logic based on another field "B", and the field "A" is displayed when the field "B" is checked. If there is a saved record, you open it to edit it and uncheck the "B" field, you can already see the "A" field and modify it, this is not right. If you save that record, the data of the display logic field will be also stored. | ||||
| Steps To Reproduce | 1-Install retail modules. 2- Login the ERP with the System Admin role. 3- Go to modules and sete the "org.openbravo.retail.config" in development. 4-Go to 'Windows, Tabs and Fields' window. 5-Search Assortment window and select the Product tab. 6-Then add new record in Field tab. 6.1- Name: Stocked. 6.2- Property: product.stocked 6.3- Save. 7-Edit Bestseller field. 7.1- Display Logic: @inp_propertyField_stocked_IsStocked@=true 7.2- Save. 8-Logout, restat tomcat and compile the app. 9- Login to the ERP as the "The White Valley Goup Admin- The White Valley Group" role. 10- Go to Assortment window an select White Valley Group Product List. 11- Go to Product tab and click on create new product in form view. 12- In the product dropdown select "Alpine skiing backpack 27 L" and save the record. 13- Realize that the bestseller field is shown, because the stocked field is checked. 14- Now, edit the same record and choose "Gift Card Infinite". Realize that the bestseller field is already shown, this is normal because it will not change untill we save, but realize also that you can modify the value of that field. 15- Save the record an realize that the "bestseller" field is no longer shown. But you have been able to modify the data and that is not correct. | ||||
| Proposed Solution | Maybe create an event handler to handle the fields in these cases. The value of the display logic field should be a default value defined in the database. | ||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2016-07-05 13:37 | NaroaIriarte | New Issue | |||
| 2016-07-05 13:37 | NaroaIriarte | Assigned To | => platform | ||
| 2016-07-05 13:37 | NaroaIriarte | Modules | => Core | ||
| 2016-07-05 13:37 | NaroaIriarte | Triggers an Emergency Pack | => No | ||
| 2016-07-06 08:59 | NaroaIriarte | Proposed Solution updated | |||
| 2016-07-08 07:43 | alostale | Status | new => acknowledged | ||
| 2016-07-08 07:43 | alostale | Type | defect => design defect | ||
| 2022-02-01 08:09 | alostale | Assigned To | platform => Triage Platform Base | ||
| There are no notes attached to this issue. |