[jira] [Commented] (OFBIZ-10195) Add the ability in performFind service to set OR search criteria

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (OFBIZ-10195) Add the ability in performFind service to set OR search criteria

Nicolas Malin (Jira)

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

Gil Portenseigne commented on OFBIZ-10195:
------------------------------------------

You make good points :), and I think about another one, we could use hidden or display, to force condition to the user, and the it'll be good to have the ability to group these conditions.  So extend this ability to all fields is the way to go !

> Add the ability in performFind service to set OR search criteria
> ----------------------------------------------------------------
>
>                 Key: OFBIZ-10195
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-10195
>             Project: OFBiz
>          Issue Type: Improvement
>            Reporter: Gil Portenseigne
>            Assignee: Gil Portenseigne
>            Priority: Minor
>             Fix For: Upcoming Branch
>
>         Attachments: OFBIZ-10195.patch, OFBIZ-10195.patch
>
>
> When using performFind service for advanced entity search, we can meet the need to have search criteria that do not intersect between them, but make the union of the condition.
> To realize this improvement we propose to set a new suffix _grp.
> Thus using :
> <field name="field1"><text-find/></field>
> <field name="field1_grp"><hidden value="unionKey"/></field>
> <field name="field2"><text-find/></field>
> <field name="field2_grp"><hidden value="unionKey"/></field>
> Then the two search fields criteria will be unioned during the search by the OR operator.
> Several different keys can be used for several different unioned condition.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)