User filter based on multiple fields

One possible way you could do it is to create a local variable of partially filtered users.  Have that update whenever the first filter is applied.  Then, create another local variable of fully filtered users that works by applying the second filter to the partially filtered list local variable.  It would be updated when either the second filter changes, or the users in the first local variable change.

I can't do that in a user filter

hello Ignacio Arriagada did you get solution for this issue? I am also looking for the solution. We are using 22.4 Version. Please let me know how you resolved this issue with default user filters and without using customize filters.

You can create a custom record field and provide a user filter on top of that field. 

If you share exact requirements, members can provide proper suggestions/inputs.

What is your exact requirement, please elaborate. You will have to create separate filters for individual fields is what I am aware of. if it is a combination create a custom record field and a filter on it.

With the help of userFilters you cannot meet the requirement. As of now it is not possible to configure an user filter by combination of two fields. You can configure a filter in the interface by using dropDown or textField component. Here is an example. 

Now you can configure the filter with the help of dropDown component or text field. Here I have configured with dropdown.

Expression Rule:GT_firstName

a!queryRecordType(
  recordType: 'recordType!GT CustomerDetails',
  filters: a!queryLogicalExpression(
    operator: "OR",
    filters: {
      a!queryFilter(
        field: 'recordType!GT CustomerDetails.fields.firstName',
        operator: "=",
        value: ri!firstName,
        applyWhen: a!isNotNullOrEmpty(ri!firstName)
      ),
      a!queryFilter(
        field: 'recordType!GT CustomerDetails.fields.lastName',
        operator: "=",
        value: ri!lastName,
        applyWhen: a!isNotNullOrEmpty(ri!lastName)
      )
    }
  ),
  pagingInfo: a!pagingInfo(startIndex: 1, batchSize: 500)
).data

---------------------------------------------------------------------------------------
Interface Portion:

a!localVariables(
  local!save,
  local!name: rule!GT_firstName(
    firstName: ri!firstName,
    lastName: ri!lastName
  ),
  {
    a!dropdownField(
      choiceLabels: cons!GT_USER_NAME,
      choiceValues: cons!GT_USER_NAME,
      label: "Name",
      placeholder: "Search here by name",
      value: local!save,
      saveInto: {
        local!save,
        a!save(ri!firstName, local!save),
        a!save(ri!lastName, local!save)
      }
    ),
    a!gridField(
      label: "",
      labelPosition: "ABOVE",
      data: local!name,
      columns: {
        a!gridColumn(
          label: "First Name",
          sortField: local!name['recordType!GT CustomerDetails.fields.firstName'],
          value: fv!row['recordType!GT CustomerDetails.fields.firstName']
        ),
        a!gridColumn(
          label: "Last Name",
          sortField: local!name['recordType!GT CustomerDetails.fields.lastName'],
          value: fv!row['recordType!GT CustomerDetails.fields.lastName']
        )
      },
      pageSize: 16
    )
  }
)

Hi, In this code, I have noticed that the same value is being saved in two different rule inputs, i.e., the value local!save is being stored in both ri!firstName and ri!lastName. Could you please explain why this approach is being used?"

Hi, In this code, I have noticed that the same value is being saved in two different rule inputs, i.e., the value local!save is being stored in both ri!firstName and ri!lastName. Could you please explain why this approach is being used?"

I have just given an example.