Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0017008Openbravo ERPA. Platformpublic2011-05-04 17:072011-05-27 11:37
ReporterAinhoaPagola 
Assigned Tomaite 
PriorityurgentSeveritymajorReproducibilityhave not tried
StatusclosedResolutionno change required 
PlatformOS20OS VersionUbuntu 8.4
Product Versionpi 
Target Version3.0MP0Fixed in Version 
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
Summary0017008: Not possible to set a column different to the ID with OBUISEL selectors
DescriptionFor example, it is not possible to define a selector for m_transaction table that sets the m_attributesetinstance_id field instead of the m_transaction_id field.

It is not possible to save the value selected with the selector if the display field is not the ID of the table.

When the value is selected using the selector, it is not possible to save the record because the value of the field is not valid.
Steps To Reproduce* To test this issue at least 2 products are needed. This products must have an Attribute set. And some transactions with these products are needed. For example, "vino tinto" and "vino blanco".

1) Create a new selector as defined in [1]
- In Defined Selector tab set:
  * Table: "M_transaction"
  * HQL where clause: e.attributeSetValue!='0'
- In Defined Selector Field create 4 new fields:
  * Movement date - Property: movementDate
  * Identificator - Property: _identifier
  * Attribute - Property: attributeSetValue
  * Article - Property: product. Default Expresion: OB.getParameters().get('inpmProductId'). With this default expresion, the filter should show only the attributes of the selected product.
For all the fileds check central maintenance, sortable, filtable and show in grid.

2) Go to Tables and Columns and select OrderLine table.
- Select M_AttributeSetInstance_ID column and change its reference to OBUISEL_Selector Reference.
- Set Reference Serach Key to the new selector.

3) Change to Admin rol. Go to Saler Order. Create a new header. Create a new line selecting the product "vino tinto". The attribute selector will be displayed. Select one of the records. Try to save the line.

Note: If in Reference | Defined Selector, the field "value" is blank, the user will be able to select a value and try to save. An error will be displayed. It says that the Foreing Key is not respected (because the ID of the transaction is been inserted in the attribute field!)
Instead, if the attribute field of the selector is chosen in the "value field", the user won't be able to even select a value, as it wil be reseted to blanck even after choosing one.


[1] http://wiki.openbravo.com/wiki/Projects/Selector/Developers_Manual#Step_1:_Define_a_Reference [^] [^]
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 00170103.0MP0 closed iperdomo Default Expression in new selectors not working for search reference type column 
depends on defect 00170113.0MP0 closed iperdomo Filter expression in OBUISEL selectors not filtering 
related to defect 00169803.0MP0 closed iperdomo Property field for OBUISEL selectors not visible in grid 
related to defect 00169793.0MP0 closed iperdomo Property path in OBUISEL selectors fields is not working 
related to defect 00170063.0MP0 closed iperdomo New selector not refreshing properly data 
related to defect 0017121 closed iperdomo Display Field in OBUISEL selector showing UUID 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-05-04 17:07AinhoaPagolaNew Issue
2011-05-04 17:07AinhoaPagolaAssigned To => alostale
2011-05-04 17:07AinhoaPagolaModules => Core
2011-05-04 17:32AinhoaPagolaRelationship addedrelated to 0016980
2011-05-04 17:33AinhoaPagolaRelationship addedrelated to 0016979
2011-05-04 17:34AinhoaPagolaRelationship addedblocks 0017006
2011-05-04 17:34AinhoaPagolaRelationship deletedblocks 0017006
2011-05-04 17:34AinhoaPagolaRelationship addedrelated to 0017006
2011-05-04 17:36AinhoaPagolaIssue Monitored: networkb
2011-05-04 17:37AinhoaPagolaRelationship addedrelated to 0017010
2011-05-04 17:37AinhoaPagolaRelationship addeddepends on 0017011
2011-05-05 09:06alostaleTarget Version => 3.0RC8
2011-05-05 09:06alostaleAssigned Toalostale => iperdomo
2011-05-05 09:07alostaleStatusnew => scheduled
2011-05-05 10:27gorka_gilTarget Version3.0RC8 => 3.0MP0
2011-05-11 14:01AinhoaPagolaSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=1963#r1963
2011-05-11 16:44maiteIssue Monitored: maite
2011-05-17 09:15iperdomoPriorityurgent => normal
2011-05-17 13:41iperdomoPrioritynormal => urgent
2011-05-25 11:12iperdomoNote Added: 0037414
2011-05-25 11:16iperdomoStatusscheduled => feedback
2011-05-25 11:17dalsasuaAssigned Toiperdomo => maite
2011-05-27 10:57iperdomoRelationship addedrelated to 0017121
2011-05-27 11:37maiteNote Added: 0037654
2011-05-27 11:37maiteStatusfeedback => closed
2011-05-27 11:37maiteResolutionopen => no change required

Notes
(0037414)
iperdomo   
2011-05-25 11:12   
I have tested and this is not a regression. In 2.50 we have the same behavior. The default selector is to pick the primary-key value of the referenced table, not any other column.

The final goal could be achieved using a 'Custom Query' based selector, and defining a HQL that filters by product.
(0037654)
maite   
2011-05-27 11:37   
Goal can be achieve defining custom Query selector