Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
backport[Openbravo ERP] A. Platformmajoralways2013-03-12 19:032013-03-25 16:25
ReportercaristuView Statuspublic 
Assigned ToAugustoMauch 
PriorityurgentResolutionfixedFixed in Version2.50MP50
StatusclosedFix in branch2.50Fixed in SCM revision6592e5263279
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product Version2.50MP49SCM revision 
Review Assigned Tomarvintm
Web browser
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0023301: Columns with Price reference can't be used as filter columns

DescriptionIf we check a column that uses a price reference to use it as filter column, is not possible to execute the filter because of a javascript error occurs: the system has generated a field that only must be generated with Amount reference paramsData[count++] = new Array("inpParamPriceStd_f", frm.inpParamPriceStd_f.value); it uses a range to filter (maximum and minimum).
Steps To Reproduce1) In [Tables and Fields] check the "used as filter column" for any column that uses a Price reference. (For example PriceStd column in m_productprice table)
2) ant smartbuild
3) restart tomcat
4) Go to the window that contains the field related to the column, and try to filter
Proposed SolutionNot generate that field for Price reference
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
blocks defect 0023289 closedAugustoMauch Columns with Price reference can't be used as filter columns 

-  Notes
hgbot (developer)
2013-03-14 11:14

Repository: erp/stable/2.50
Changeset: 6592e5263279d020a148f718672299faee3504e3
Author: Augusto Mauch <augusto.mauch <at>>
Date: Thu Mar 14 11:14:32 2013 +0100
URL: [^]

Fixes issue 23301: Price reference columns can be sed as filter columns

Price columns, as opposed to Amount and Number columns, do not have a minimum and maximum range when they are filtered, only a minimum value [1]. The UIPrice reference has been changed so that it behaves this way.

[1] [^]

M src/org/openbravo/reference/ui/

- Issue History
Date Modified Username Field Change
2013-03-14 11:06 AugustoMauch Type defect => backport
2013-03-14 11:06 AugustoMauch fix_in_branch => 2.50
2013-03-14 11:07 AugustoMauch Issue Monitored: alostale
2013-03-14 11:08 AugustoMauch Review Assigned To => alostale
2013-03-14 11:14 hgbot Checkin
2013-03-14 11:14 hgbot Note Added: 0057248
2013-03-14 11:14 hgbot Status scheduled => resolved
2013-03-14 11:14 hgbot Resolution open => fixed
2013-03-14 11:14 hgbot Fixed in SCM revision => [^]
2013-03-25 16:23 marvintm Review Assigned To alostale => marvintm
2013-03-25 16:23 marvintm Status resolved => closed
2013-03-25 16:23 marvintm Fixed in Version => 3.0MP22
2013-03-25 16:25 AugustoMauch Fixed in Version 3.0MP22 => 2.50MP50

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker