[
https://issues.apache.org/jira/browse/OFBIZ-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481214
]
Leon Torres commented on OFBIZ-818:
-----------------------------------
Oh ok, that makes sense. Thanks for the clarificatoin, Jacopo.
I suppose there's a UI issue here rather than a problem with performFind.
We can close this issue.
> performFind not behaving as expected with empty fields
> ------------------------------------------------------
>
> Key: OFBIZ-818
> URL: https://issues.apache.org/jira/browse/OFBIZ-818
> Project: OFBiz (The Open for Business Project)
> Issue Type: Bug
> Reporter: Leon Torres
>
> If a field such as facilityId is left empty, then the performFind should be
> ignoring that field in its lookup. That is, it should lookup values
> regardless of what facilityId is.
> However I found a case where leaving the facilityId field empty causes the
> lookup to behave as if it had a facilityId == NULL condition. Thus if you
> leave it empty, then it will only match those values where facilityId is NULL.
> What's perplexing is the same lookup where this bug occurs has a productId
> field that behaves correctly if left blank. This means the performFind
> service is behaving differently where its behavior should be uniform.
> The lookup can be seen in the following URL:
> https://localhost:8443/ordermgr/control/ApprovedProductRequirements
> And the bsh that invokes performFind is here,
> order/webapp/ordermgr/WEB-INF/actions/requirement/ApprovedProductRequirements.bsh
> The entity being looked up is Requirement.
> I think there could be an issue with the performFind service, but I am not
> familiar with how that service works.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
