Anonymous | Login

Project:

News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ]

[ Issue History ] [ Print ]

ID

0017008

Type

Category

Severity

Reproducibility

Date Submitted

Last Update

defect

[Openbravo ERP] A. Platform

major

have not tried

2011-05-04 17:07

2011-05-27 11:37

Reporter

AinhoaPagola

View Status

public

Assigned To

maite

Priority

urgent

Resolution

no change required

Fixed in Version

Status

closed

Fix in branch

Fixed in SCM revision

Projection

none

ETA

none

Target Version

3.0MP0

OS

Linux 32 bit

Database

PostgreSQL

Java version

1.5

OS Version

Ubuntu 8.4

Database version

8.3

Ant version

1.7

Product Version

pi

SCM revision

Review Assigned To

Web browser

Modules

Core

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

No

Summary

0017008: Not possible to set a column different to the ID with OBUISEL selectors

Description

For 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 [^] [^]

Tags

No tags attached.

Relationships [ Relation Graph ] [ Dependency Graph ]

related to	defect	0017010	3.0MP0	closed	iperdomo	Default Expression in new selectors not working for search reference type column
depends on	defect	0017011	3.0MP0	closed	iperdomo	Filter expression in OBUISEL selectors not filtering
related to	defect	0016980	3.0MP0	closed	iperdomo	Property field for OBUISEL selectors not visible in grid
related to	defect	0016979	3.0MP0	closed	iperdomo	Property path in OBUISEL selectors fields is not working
related to	defect	0017006	3.0MP0	closed	iperdomo	New selector not refreshing properly data
related to	defect	0017121		closed	iperdomo	Display Field in OBUISEL selector showing UUID

Notes
(0037414) iperdomo (reporter) 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 (developer) 2011-05-27 11:37	Goal can be achieve defining custom Query selector

Issue History
Date Modified	Username	Field	Change
2011-05-04 17:07	AinhoaPagola	New Issue
2011-05-04 17:07	AinhoaPagola	Assigned To	=> alostale
2011-05-04 17:07	AinhoaPagola	Modules	=> Core
2011-05-04 17:32	AinhoaPagola	Relationship added	related to 0016980
2011-05-04 17:33	AinhoaPagola	Relationship added	related to 0016979
2011-05-04 17:34	AinhoaPagola	Relationship added	blocks 0017006
2011-05-04 17:34	AinhoaPagola	Relationship deleted	blocks 0017006
2011-05-04 17:34	AinhoaPagola	Relationship added	related to 0017006
2011-05-04 17:36	AinhoaPagola	Issue Monitored: networkb
2011-05-04 17:37	AinhoaPagola	Relationship added	related to 0017010
2011-05-04 17:37	AinhoaPagola	Relationship added	depends on 0017011
2011-05-05 09:06	alostale	Target Version	=> 3.0RC8
2011-05-05 09:06	alostale	Assigned To	alostale => iperdomo
2011-05-05 09:07	alostale	Status	new => scheduled
2011-05-05 10:27	gorka_gil	Target Version	3.0RC8 => 3.0MP0
2011-05-11 14:01	AinhoaPagola	Steps to Reproduce Updated	View Revisions
2011-05-11 16:44	maite	Issue Monitored: maite
2011-05-17 09:15	iperdomo	Priority	urgent => normal
2011-05-17 13:41	iperdomo	Priority	normal => urgent
2011-05-25 11:12	iperdomo	Note Added: 0037414
2011-05-25 11:16	iperdomo	Status	scheduled => feedback
2011-05-25 11:17	dalsasua	Assigned To	iperdomo => maite
2011-05-27 10:57	iperdomo	Relationship added	related to 0017121
2011-05-27 11:37	maite	Note Added: 0037654
2011-05-27 11:37	maite	Status	feedback => closed
2011-05-27 11:37	maite	Resolution	open => no change required

Copyright © 2000 - 2009 MantisBT Group