Filters component



The filters component is a technical component which cannot be used in the Lightning app builder. 
Instead other components are using this component for filtering list views. 

Where can this component be used?

The filters component is used in the following components:



List component


Talentpools tab


Talentpools detail page


How to configure the component?

The filters component can be configured when you add the list component to a Lightning page in the Lightning app builder:


You have the option to add one or more filters to the records shown in the list component.  In case you want to use more filters, you should separate them with comma's. 

To add a filter you need to add the field you want to filter on first. You can also add filters on parent objects. by using the Fieldname__r.ParentObjectFieldname__c notation. 

Subsequently you need to add an operator. Possible operators are:

EQ --> Equals
NE --> Not equals
GT --> Greater then
GE --> Greater then or equal to
LT --> Lower then
LE --> Lower then or equal to
ISNULL --> Is empty
NOTNULL --> Is not empty
VALUEIN --> Field value is in specified list of strings
VALUENOTIN --> Field value is not in specified list of strings

Finally you need to add the value. For String values (Text values) you need to put the value inside single quotes. For integer or boolean fields this is not needed. 

Operator Example
GE Number_of_job_applications__c GE 2 
LT Number_of_job_applications__c LT 2
LE Number_of_job_applications__c LE 1
ISNULL Last_name__c ISNULL
VALUEIN Status__c VALUEIN ('Open','Concept')
VALUENOTIN Status__c VALUENOTIN ('Open','Concept')

Often the list component is used on a record detail page and the data shown in the list component should be filtered on the current record ID. 

This is possible by using the variable recordId. Example:

Position__c EQ ('{recordId}')

Filters logic
You can also add multiple filters. For example the recruiter of the job must be equal to the contact record or the hiringmanager must be equal to the contact record. 
In this case you should specify the following two filters (comma separated):
Position__r.Hiringmanager__c EQ ('{recordId}'),Position__r.Hiringmanager__c EQ ('{recordId}')
The filters logic should then contain the logic between the two filters:
{A} OR {B}

Show filters or not
You can choose to show the filter options or to hide them.

Fieldset used for filters
You can choose which filters you want to show above the table. You can do this by creating a fieldset on the job application object and add the fields you want to allow filtering on to this fieldset. Then add the API name of the fieldset to this setting. 


Was this article helpful?
0 out of 0 found this helpful


  • Avatar
    Jagmohan Singh

    Will the operator 'Contains' also be supported?

  • Avatar
    Ashna Lakhisaran

    Hi Jagmohan,

    Currently the operator 'Contains' is not supported. Is this something that would be useful for your organisation?

  • Avatar
    Jagmohan Singh

    Hi Ashna,
    Yes, this will be very usefull to make a list component for active job applications by filtering on the status. Example: Status CONTAINS 1.0, 2.0, 3.0 etc..

    Currently this is only possible with status EQ of NE resulting in a very long string. Applying filter logic as described above ({A} OR {B}) doesn't work anymore after 26 filters (so when one reaches {Z}).

  • Avatar
    Ashna Lakhisaran

    Hi Jagmohan,

    I will create a ticket for this.

Powered by Zendesk