[ 
https://issues.apache.org/jira/browse/OFBIZ-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14525725#comment-14525725
 ] 

Jacques Le Roux commented on OFBIZ-6323:
----------------------------------------

Hè having participed to build the lookup mechanims as it is now I know how it 
works ;) By the way I prefer to call them layered lookups than ajaxLookup , see 
[my somehow related 
comment|https://issues.apache.org/jira/browse/OFBIZ-4183?focusedCommentId=14525722]
 in OFBIZ-4183

Now specifically about LookupProductAndPrice, this feature is wanted as the 
user might not want to only use the default price. So it might look confusing 
for you but it's a feature which is moreover maybe exploited in custom 
projects. If you want your own it's OK, but we will not change OOTB. I close as 
invalid.

> LookupProductAndPrice ajaxLookup should only return DEFAULT_PRICE rather than 
> all the price types
> -------------------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-6323
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-6323
>             Project: OFBiz
>          Issue Type: Bug
>          Components: product
>    Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, 
> 14.12.01
>            Reporter: Forrest Rae
>         Attachments: OFBIZ-6323.patch
>
>
> The LookUpProductPrice ajaxLookup leverages the same LookupDecorator screen 
> that is used for more advanced product queries.  The results of the request 
> display all the different price types configured for a product  This is 
> confusing for the user when adding an item to a quote.  The attached patch 
> adds additional conditionalFields to the search criteria.
> I've searched the code base for areas where this change might adversely 
> affect usability and didn't see any cases of that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to