You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Jacques Le Roux (JIRA)" <ji...@apache.org> on 2015/05/02 11:50:06 UTC

[jira] [Commented] (OFBIZ-6323) LookupProductAndPrice ajaxLookup should only return DEFAULT_PRICE rather than all the price types

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

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

I'm not sure why this "feature" is like that, but why not allow the user to constrain the search  (new field for productPriceTypeId) rather than force it?

> 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)