Issue related to Cascading Filter Platform Analytics

[AnupriyaC]

Hi Everyone,

I’d really appreciate your guidance on an issue I’m facing while setting up a cascading filter, where Filter B should follow Filter A.

Here’s the context:

My main table (Incident Reduction) has two fields: Application and Department.

The Application field is a reference from the Business App table.

The Business App table also has a reference field for Department, but the source for the Department field comes from the Group table (which automatically gets selected as the filter source in Platform Analytics).

Similarly, when setting up the filter for Application, the filter source automatically gets selected as Business App.

What I want:

When a Department is chosen in Filter A, only the Applications belonging to that Department should appear in Filter B.

What I tried:

For the first-level filter, I used:

Table: Group

Field: Department

Target Table (Related Table): Incident Reduction -> Department

For the second-level filter, I used:

Table: Business App

Field: Name (since Application is a reference field, only “Name” was available, which corresponds to Application)

Parent Target: Department (already a reference field in this table with the same backend name)

Target Table (Related Table): Incident Reduction → Application (this is a reference to Business App)

Issue:
In Platform Analytics, I still see the error:

        “1 filter(s) cannot be followed.”

Since there’s no direct Application reference in the Group table, I’m struggling to make the cascading logic work correctly. Could someone help me understand what I’m missing here and how to correctly configure this cascading filter?

Thanks in advance!

[kaushal_snow]

Hi @AnupriyaC ,

It indicates that cascading filter setup is encountering issues due to missing or incorrect relationships between the tables involved. In your case, the Incident Reduction table references both the Business App and Group tables, but there is no direct relationship between these tables, which is necessary for cascading filters to function correctly....

>> To resolve this, consider the following steps:

Establish a many-to-many relationship between the Group and Business App tables.... This can be achieved by creating a new M2M table that links these two tables, allowing the Department field in the Group table to relate to the Business App table via this intermediary table.Once the M2M relationship is established, modify your cascading filter setup to use this new relationship. In the second level filter (for Application), set the 'Parent Target' to the Department field in the Group table, and ensure that the Target Table is set to the Business App table. This configuration will enable the second filter to display only the applications associated with the selected department....

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.