Openbravo Issue Tracking System - Openbravo ERP | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0018295 | Openbravo ERP | Z. Others | public | 2011-08-16 19:28 | 2011-08-29 16:30 |
| Reporter | Xpand-IT | ||||
| Assigned To | marvintm | ||||
| Priority | low | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | 3.0MP1 | ||||
| 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 | 0018295: Add some validations when upgrading to OB 3.0 targeting application dictionary metadata problems | ||||
| Description | When there's a field, table, or column with wrong metada, it should be raised a warning when upgrading to OB 3.0. Or maybe the warning should be raised when compiling the window. | ||||
| Steps To Reproduce | Example: A field with "diplaylength" null, which will cause an error when trying to access the window in OB 3.0, should raise a warning. | ||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2011-08-16 19:28 | Xpand-IT | New Issue | |||
| 2011-08-16 19:28 | Xpand-IT | Assigned To | => jonalegriaesarte | ||
| 2011-08-16 19:28 | Xpand-IT | Modules | => Core | ||
| 2011-08-29 16:30 | jonalegriaesarte | Assigned To | jonalegriaesarte => marvintm | ||
| There are no notes attached to this issue. |