This would be helpful . Do you have an estimate when the functionality will be developed?

What is the status of this, i been waiting for this function to be up and today is 2020, but i still do not see these changes

Please allow filtering of multiple columns on list lookup. This will allow use of one list for multiple sites.

CAML or SQL where clause

Please, please, please add this functionality.

I'm trying to recreate some of my infopath forms, but the lack of the ability to filter by multiple values leaves Nintex forms rather useless. In some cases, the need to filter by 10 different values, even between different lists is needed.

Also, setting fields based on conditions, button clicks etc. which is anotherbasic feature of infopath, but has been excluded from Nintex.

These are basic, key features that are needed when creating forms. These features should be options, basic calculations etc. not scripting/coding, else you may aswell just hire a developer to create a custom form.

I hope these requests are implemented in future updates, as does everybody else that uses Nintex.

Our users are getting quite frustrated with Nintex forms due to the limitation on filtering. Scrolling through a dropdown list of several hundred items because additional filtering on the list isn't possible is a significant issue.

Allowing a CAML query would be great, however I would even be happy with allowing a form variable to be selected when filtering By Specified Value.

This was marked as Under Review over 3 years ago, is there any update on this yet?

CAML query would be great indeed. Not all multiple columns filtering can be resolved using cascading dropdowns. What's the status of this improvement request as it has be Under Review since march 2014?

I have a List Look up which I want to filter where the the fields IS NOT EQUAL to another field on my Nintex Form. Having the ability apply more that one filter and to the =, <>, > or < would be great.

Please make it possible like in Infopath:) It's there for like 10 years already....

Please consider the ability to select a named control when defining the list view in the lookup. This would allow dynamic filtering based on another field in the form. i.e. A person selects Fiscal Year from a drop down and the list lookup uses the Fiscal Year to define the list view in the list lookup

Do it just like they do in SharePoint views, AND and OR. We are all familiar with that construct.

I would add options in the configuration screen for AND and OR functionality that could easily be selected. You can do this similar to some of the config screens you see on various workflow actions. Hopefully you can get this going soon as it would make lookup filtering very robust.

Reusing the CAML Builder from the List View control would probably be the best bet here.

I too would like to vote for this functionality...Either SQL or CAML would help me solve a couple of issues. This thread hasn't been updated in while. Is this item still under review?

I would like to add a functionality : to be able to choose to apply the filter on the form read mode. Lots of time, I filter a list lookup with items that are opened to only be able to associate the current item with other active items. But once the association is done, the other active item lives by its side and can be completed but still associated with the current item. In this case, with the current behavior, the associated and completed item won't be visible in the form whereas it is in fact associated.

We would also like to be able to use the SQL where clause in our Nintex form dropdowns. It looks like there are a few 3rd party add-ons for this, but if it could be included in the next update that would be appreciated greatly!

I been really stuck on this issue this week. I have a single lookup list that I need to filter by 2 columns. Either CAML or SQL would be great. Evan the out of the box list view filters select multiple fields with AND / OR operation would be helpful.

CAML queries would be great. If you bring over the CAML builder from the Query List Action in Nintex Workflow that'd be wonderful.

My feeling tells me that a structured form will be limited in brackets and precedence. SharePoint listview filtering also has this limitation in the GUI.
If using CAML or SQL you offer full control and that would have my preference.