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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0016827
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 00. Application dictionarymajoralways2011-04-15 14:422011-04-19 00:00
ReportermaiteView Statuspublic 
Assigned Toalostale 
PriorityimmediateResolutionfixedFixed in Version3.0RC6
StatusclosedFix in branchFixed in SCM revisiona572df594b0f
ProjectionnoneETAnoneTarget Version3.0RC6
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product Version3.0RC5SCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0016827: Is not possible to make a field mandatory

DescriptionIs not possible to make a field mandatory
Steps To Reproduce1. Check Core module as "in development"
2. Go to Invoice table, POReference column and check "mandatory" checkbox
3. Compile invoice window
4. restart tomcat
5. Access to invoice window and realize that field does not appear as mandatory
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
duplicate of defect 00183543.0MP4 closedmtaal If you define a column as mandatory, the field is not mandatory in grid view 
related to defect 0009019pi closedmtaal Mandatory/not-null not set correctly in the Data Access Layer because Application Dictionary setting not correct 

-  Notes
(0035996)
hgbot (developer)
2011-04-15 16:20

Repository: erp/devel/pi
Changeset: a572df594b0f73bc15c111cea79d259e75bffc44
Author: Asier Lostalé <asier.lostale <at> openbravo.com>
Date: Fri Apr 15 16:19:01 2011 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/a572df594b0f73bc15c111cea79d259e75bffc44 [^]

fixed bug 16827: Is not possible to make a field mandatory

---
M modules/org.openbravo.client.application/src/org/openbravo/client/application/window/OBViewFormComponent.java
---
(0035997)
alostale (manager)
2011-04-15 16:32

The problem is column definition is read from in memory model which performs better than reading from AD, because of issue 0009019 mandatory fields were set regarding DB physical definition rather than AD. This caused AD mandatory value not to be used.
(0036009)
maite (developer)
2011-04-18 18:44

verified

- Issue History
Date Modified Username Field Change
2011-04-15 14:42 maite New Issue
2011-04-15 14:42 maite Assigned To => alostale
2011-04-15 14:42 maite Modules => Core
2011-04-15 14:57 maite Issue Monitored: networkb
2011-04-15 15:46 alostale Relationship added related to 0009019
2011-04-15 16:20 hgbot Checkin
2011-04-15 16:20 hgbot Note Added: 0035996
2011-04-15 16:20 hgbot Status new => resolved
2011-04-15 16:20 hgbot Resolution open => fixed
2011-04-15 16:20 hgbot Fixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/a572df594b0f73bc15c111cea79d259e75bffc44 [^]
2011-04-15 16:32 alostale Note Added: 0035997
2011-04-18 18:44 maite Note Added: 0036009
2011-04-18 18:44 maite Status resolved => closed
2011-04-18 18:44 maite Fixed in Version => 3.0RC6
2011-04-19 00:00 anonymous sf_bug_id 0 => 3289082
2011-08-29 17:09 alostale Relationship added duplicate of 0018354


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker