Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0015951 | Openbravo ERP | A. Platform | public | 2011-02-11 09:17 | 2022-02-01 08:08 |
|
| Reporter | rafaroda | |
| Assigned To | Triage Platform Base | |
| Priority | normal | Severity | major | Reproducibility | always |
| Status | new | Resolution | open | |
| Platform | | OS | 30 | OS Version | Professional Appliance |
| Product Version | 2.50MP23 | |
| 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 | 0015951: Dataset application to exclude active check-boxes |
| Description | Imagine that you spend a long time deactivating Spanish taxes that you installed via the Spanish taxes dataset, to show your customer only few taxes that he needs (keep only 4 or 40). Every time that you update your Spanish taxes dataset, the taxes will be set to active again, and you will have to do the exercise of deactivating them again, which is time wasted. |
| Steps To Reproduce | |
| Proposed Solution | If there could be a way to update datasets, without overwriting Active check-box info of datasets installed to avoid this situations, it would be great. |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | related to | feature request | 0019295 | | new | ioritzCia | Localization Pack: Spain | to apply a dataset update, if you have deactivated a tax of dataset, it is activate again | | related to | design defect | 0021594 | 3.0MP16 | new | Triage Omni OMS | Openbravo ERP | Core update turns inactive report template into active in Document type window | | related to | feature request | 0022127 | | new | AugustoMauch | Openbravo ERP | Ability to define datasets as "not updateable", so that they are initially created but afterwards not updated |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2011-02-11 09:17 | rafaroda | New Issue | |
| 2011-02-11 09:17 | rafaroda | Assigned To | => alostale |
| 2011-02-11 09:17 | rafaroda | Modules | => Core |
| 2011-02-16 12:29 | rafaroda | Issue Monitored: rafaroda | |
| 2016-02-29 17:51 | ngarcia | Relationship added | related to 0019295 |
| 2016-02-29 17:51 | ngarcia | Relationship added | related to 0021594 |
| 2016-02-29 17:52 | ngarcia | Relationship added | related to 0022127 |
| 2017-04-10 14:35 | alostale | Assigned To | alostale => platform |
| 2022-02-01 08:08 | alostale | Assigned To | platform => Triage Platform Base |