Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0036164 | Openbravo ERP | A. Platform | public | 2017-06-01 13:32 | 2022-02-01 08:08 |
|
Reporter | alostale | |
Assigned To | Triage Platform Base | |
Priority | normal | Severity | major | Reproducibility | have not tried |
Status | acknowledged | Resolution | open | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
Target Version | | Fixed in Version | | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | No |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0036164: non-existing columns can be included within validation rules |
Description | A validation rule that depends on a column that doesn't exist on any field for the tab that is used in. Is ignored in FIC and considered as parameter to be obtained from session. When executed, depending on the SQL, it can fail or to be simply ignored.
This should be somehow validated to display a proper error message. |
Steps To Reproduce | - |
Proposed Solution | |
Additional Information | |
Tags | No tags attached. |
Relationships | related to | defect | 0036163 | | closed | alostale | val rule referring non-existent col fails if there's a property field with same name |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2017-06-01 13:32 | alostale | New Issue | |
2017-06-01 13:32 | alostale | Assigned To | => platform |
2017-06-01 13:32 | alostale | OBNetwork customer | => No |
2017-06-01 13:32 | alostale | Modules | => Core |
2017-06-01 13:32 | alostale | Triggers an Emergency Pack | => No |
2017-06-01 13:33 | alostale | Status | new => acknowledged |
2017-06-01 13:33 | alostale | Relationship added | related to 0036163 |
2022-02-01 08:08 | alostale | Assigned To | platform => Triage Platform Base |