How to create cascade filter

[Prekumar Muruga]

Can someone please explain how to create cascade filter step by step. gone through this below link but not sure which table I need to choose on step 3.

https://community.servicenow.com/community?id=community_question&sys_id=ee9bd954db730cd4feb1a851ca961984

Requirement is we are having list collector field in incident form referring to user table. in the dashboard on clicking on respective user it has to filter the selected  incident user who is mentioned in the list collector field.

[Community Alums]

Hi @Prekumar Murugan ,

Here are your steps:

Procedure

1. Navigate to All > Reports > Administration > Interactive filters.
2. Click New.
3. In the Filter based on list, select Cascading Filters.
4. Right-click the form header and select Save.
5. Define the first level of the cascading filter.
   1. In the Cascading Filter related list, click New.
   2. Select the Table and the Display field from the table that contains the values you want to use as the top-level filter choices. The Display Field is limited to the types boolean, choice, reference, and string.
      To define the top level of a hierarchy based on managers and the groups they manage, select Group [sys_user_group] as the Table and Manager as the Display field.
   3. (Optional) Use the Filters field to limit which choices are available to users.
      Filter conditions are especially useful when you create a cascading filter based on a self-referencing table, such as Location [cmn_location]. Filter the data to ensure that each level of the cascading filter only has options appropriate for that level.
   4. Right-click the form header and select Save.
6. Define the next level of the hierarchy.
   Cascading filters use a one-to-many relationship between higher-level filters and lower-level filters. One higher-level filter can affect the choices available in any number of lower-level filters.
   1. From the manager filter, in the Cascading Filter related list, click New.
   2. Select the Table and the Display field from the table that contains the values you want to use as the second-level filter choices. The Display Field is limited to the types boolean, choice, reference, and string.
      In the managers and groups example, select Group [sys_user_group] as the Table and Name as the Display field.
   3. In the Parent Reference Field field, select the field that contains the value selected from the higher-level filter.
      For example, when you create the Group filter, the Parent Reference Field value is Manager. In this example, the manager selected in the first filter is used to filter the list of available groups based on the Manager field value of each group.
   4. Right-click the form header and select Save.
   5. Repeat these substeps for each additional filter you want to add. To add another level to the filter hierarchy, add a new record in the Cascading Filter related list of the lowest-level filter. For example, add the Group filter instead of a top-level filter such as the Manager filter.
7. Define how each filter level applies the filter to reports on a dashboard.
   1. In the Target Tables related list, click New.
   2. Select the Target table that contains the data you want to filter, such as Incident.
   3. Select the Field to filter on.
      The field must reference the table specified in the filter. For example when filtering incident data, the Field for the top-level manager filter is Assignment group.Manager. In this example, the Field for the second-level group filter is Assignment group.
   4. Click Submit.
   5. Repeat these substeps to add targets for each level of the filter.
      You can define multiple targets for each filter level. For example, filter incident data by assignment group or CMDB CIs by support group using the same Groups [sys_user_group] filter.

      Note: A cascading filter hierarchy must specify at least one target. You can define a cascading filter that skips levels in a hierarchy, or a cascading filter that only specifies targets for certain levels in a hierarchy. For example, define a target only for the Group-level filter and not the Manager-level filter. In this example, reports are filtered only when a user selects a specific group and not just a manager.
   The following images demonstrate the completed configuration for the example cascading filter. The Cascading Filter related list (not shown) in the top-level filter contains the second-level filter.

   Top-level filter

   Second-level filter

What to do next

After you create all levels of the filter, add it to a dashboard.

Cascading filters deduplication

So that you do not have to clean up the filter panel, duplicate filters are removed automatically.

Duplicate filters are removed according to the following criteria:

• If the configuration is the same, the last edited filter is retained.
• If the configuration is the same, except that some filters have only one target and others have multiple targets, then only the last updated filter is retained.
• If the configuration is the same, but some filters have multiple target columns in the same target table, then all the filters are considered as separate filters and retained. An example of multiple target columns in the same target table is the Date opened and Date escalated columns in the incident table.
• If the configuration and the UI control are the same, but the base condition is different for any two filters, then they are considered separate filters and retained.

Mark my answer correct & Helpful, if Applicable.

Thanks,
Sandeep

[Community Alums]

The table is where you are building the filter. example, if it's for incident the table is "incident table".

[Prekumar Muruga]

@Sandeep Dutta  I am trying for list collector fields this is not working.

I have a list collector fields in incident table referring to user table. As first step I created a cascading filter in user table

Target table I have configured like this and added to dashboard.

It showing like this but not filtering the records. on click on apply