Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0004416
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Openbravo ERP] A. Platformminoralways2008-07-15 18:322011-10-28 14:05
ReportergorkaionView Statuspublic 
Assigned Toiciordia 
PriorityhighResolutionopenFixed in Version
StatusscheduledFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSLinux 32 bitDatabasePostgreSQLJava version1.5.0_15
OS VersionGentooDatabase version8.3Ant version1.7.0
Product Version2.40SCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0004416: Autogenerate Search Key values

DescriptionIn 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 ReproduceGo 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 SolutionI 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.
Tags250MP1
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 00141262.50MP21 closediciordia A squence created for the value field of the partner is not applied automatically 
depends on backport 0004902 closedshuehner Autogenerate Search Key values 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2008-07-15 18:32 gorkaion New Issue
2008-07-15 18:32 gorkaion Assigned To => cromero
2008-07-15 18:32 gorkaion sf_bug_id 0 => 2018785
2008-07-22 09:02 cromero Status new => scheduled
2008-07-22 09:02 cromero Assigned To cromero => alostale
2008-07-22 09:02 cromero fix_in_branch => trunk
2008-12-10 09:58 alostale Assigned To alostale => iperdomo
2009-01-19 13:06 psarobe version => 2.40
2009-01-19 13:06 psarobe fix_in_branch trunk =>
2009-02-03 17:45 iperdomo Assigned To iperdomo => anthony_wolski
2009-04-16 13:23 iperdomo Assigned To anthony_wolski => iperdomo
2009-04-22 10:38 psarobe Priority normal => high
2009-04-23 16:05 psarobe Tag Attached: 250MP1
2009-11-24 11:43 iperdomo Assigned To iperdomo => shuehner
2010-05-10 17:43 shuehner Assigned To shuehner => iciordia
2010-08-09 11:34 psarobe Relationship added related to 0014126
2011-10-28 14:05 iciordia Type defect => feature request


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker