Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001830Openbravo ERP03. Procurement managementpublic2007-08-27 09:312008-06-19 12:32
Reportergalderromo 
Assigned Togorkaion 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Version 
Target Version2.40Fixed in Versionpi 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0001830: Null is accepted as attribute value
Description1-Create a product with an attribute set (Expiration date)
2-Create a shipment (for example purchase) with this product. (Do not set the attribute value por the product)
3-Try to complete the Shipment. It troughs a exception.
4-Go to the lines, open the attribute selector an press accept without setting any values
5-Complete the shipment, and "Build succesfull"

If you have a look at the database, you can see this shipmentline has an attribute with value "(null)". This means that OB understands null as a value, when it is not a value.

R2.33
Oracle-xe
Gentoo
Steps To Reproduce
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to feature request 0004066 closed pjuvara Mandatory attributes 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-06-13 19:26cromeroStatusnew => scheduled
2008-06-13 19:58cromeroTarget Version => 2.40
2008-06-19 12:32gorkaionStatusscheduled => closed
2008-06-19 12:32gorkaionNote Added: 0007863
2008-06-19 12:32gorkaionResolutionopen => no change required
2008-06-19 12:35gorkaionRelationship addedrelated to 0004066

Notes
(0005419)
user71   
2005-06-01 00:00   
(edited on: 2008-06-12 09:43)
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis.

You can see the original bug report in:
https://sourceforge.net/support/tracker.php?aid=1782329 [^]
(0001879)
gorkaion   
2007-10-19 13:20   
(edited on: 2008-06-12 09:20)
Logged In: YES
user_id=1500690
Originator: NO

There are two main rules around the attributes.

1st, if a product has an associated attribute set all its transactions must have an attribute set instance.
2nd, an attribute can be optional, so it is possible that its value be null.

Summing up this two rules it can be possible to have an attribute set with all its attributes optional and an instance of that attribute set with all its values null.
(0007863)
gorkaion   
2008-06-19 12:32   
Null values in the attribute set instances are not an error as all the attributes are considered as optionals at this moment.

Note that when you reproduce the steps of the description you are getting a new attribute set instance id different than zero that is what it is considered as null.

It is different to have a null attribute set instance (m_attributesetinstance_id null or zero) or to have null attribute values in an attribute set (m_attributesetinstance_id not null and different than zero).

There has been created a new Feature Request (0004066) to develop the possibility to check some attributes as manadatory.