Openbravo Issue Tracking System - Openbravo ERP | ||||||||||||
| View Issue Details | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | |||||||
| 0004902 | Openbravo ERP | A. Platform | public | 2008-09-09 17:26 | 2009-11-24 12:36 | |||||||
| Reporter | gorkaion | |||||||||||
| Assigned To | shuehner | |||||||||||
| Priority | normal | Severity | minor | Reproducibility | always | |||||||
| Status | closed | Resolution | out of date | |||||||||
| Platform | OS | 20 | OS Version | Gentoo | ||||||||
| Product Version | 2.40 | |||||||||||
| 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 | 0004902: Autogenerate Search Key values | |||||||||||
| Description | In old versions of Openbravo (checked that is working in OB 2.22) you could left null the Search Key (for example in Product window) and the application when the new entry is saved generates a new value. Looking in the sources and in database everything is prepared, but as the field is mandatory it is not possible to left blank the search key. If we set the field as not mandatory and recompile the sources changes and doesn't generate anything. | |||||||||||
| Steps To Reproduce | Go to Product window and try to enter a new product with null Search Key. You can't because the field is mandatory. Modify in the Application Dictionary the column Value of the M_Product table and compile the Product window. Now you can save with a null Search Key but you get a database error because the Value column is mandatory in database. | |||||||||||
| Proposed Solution | I see 2 possible solutions: 1) enable the possibility of inserting null Search Keys, changing wad to include the code that calls the getDocumentNo method always when it is a Value column, or inserting a rule to set in the html the field as not mandatory so you can left the Search Key null. 2) modify the Search Key fields to be like the DocumentNo fields. So when it is inserted a new record the application suggest a new number ('<000000001>'). I prefer this solution. | |||||||||||
| Additional Information | ||||||||||||
| Tags | platform1_sprint1 | |||||||||||
| Relationships |
| |||||||||||
| Attached Files | ||||||||||||
| Issue History | ||||||||||||
| Date Modified | Username | Field | Change | |||||||||
| 2008-09-09 17:26 | anonymous | New Issue | ||||||||||
| 2008-09-09 17:26 | anonymous | Assigned To | => alostale | |||||||||
| 2008-09-09 17:26 | anonymous | Status | new => scheduled | |||||||||
| 2008-09-09 17:26 | anonymous | fix_in_branch | => 2.40 | |||||||||
| 2008-12-12 12:13 | alostale | Tag Attached: platform1_sprint1 | ||||||||||
| 2009-01-09 12:07 | psarobe | Assigned To | alostale => iperdomo | |||||||||
| 2009-01-09 12:07 | psarobe | Steps to Reproduce Updated | ||||||||||
| 2009-01-19 13:06 | psarobe | version | => 2.40 | |||||||||
| 2009-02-03 17:45 | iperdomo | Assigned To | iperdomo => anthony_wolski | |||||||||
| 2009-04-16 13:23 | iperdomo | Assigned To | anthony_wolski => iperdomo | |||||||||
| 2009-11-24 11:43 | iperdomo | Assigned To | iperdomo => shuehner | |||||||||
| 2009-11-24 12:36 | shuehner | Note Added: 0022135 | ||||||||||
| 2009-11-24 12:36 | shuehner | Status | scheduled => closed | |||||||||
| 2009-11-24 12:36 | shuehner | Resolution | open => out of date | |||||||||
| Notes | |||||
|
|
|||||
|
|
||||