Forum Discussion
Advanced filter options from different source.
Hi Community, good day,
I'm a bit stuck in a solution I need to produce for an odd situation.
I'd like to ask your help to see if it's possible what I'm trying to do, please.
My main table is a list of Events, similar to this:
| Event | Customer | Severity |
| x1 | c1 | Info |
| x2 | c1 | Warning |
| x3 | c2 | Critical |
| x4 | c3 | Info |
Now I need to add the information Areas where the event happened because the user wants to filter by them. It's in a new table, registered like this:
| ID | Event | Area |
| 1 | x1 | Zone 1 |
| 2 | x1 | Zone 2 |
| 3 | x2 | Zone 1 |
| 4 | x3 | Zone 1 |
As you can see the relationship between Events and Areas will be 1 - N. So if I just do a direct join (or merge) it will bring duplicate records for events. That is exactly what I need to prevent, but I also need to add the filter by Areas in the dashboard.
I did try to concatenate them first to have a 1-1 relationship but the filter becomes like:
Which is not good, because these values can vary among many types of areas and happen simultaneously in many. We could have for example |Zone B, Floor 2|, |Zone B, Floor 4, Zone 1|, etc.
Although we have the Advance Filter, using the option "contain" and then filtering by a term, the users don't necessarily know all the names of the areas that it can be to insert the correct term.
So the question is. Is there programmability that makes a filter give the options from a different source table (for example with all the areas) and applies it against the main table with a "contains" clause? Or if there is another solution that I'm not seeing, please.
I really appreciate the attention, thanks.
8 Replies
farina_dj Can you just have 2 slicers, one for Event and one for Area?
Hi Greg_Deckler , thanks for the answer.
I might be missing something. A slicer needs a field to filter right? But as the relation is 1 - N, it's duplicating the events. If I go for making the relationship 1-1 by concatenating the areas in a event, I have that ugly filter like:farina_dj I'm not understanding something. If the relationship is Events 1:N Areas and you create a slicer based on the Event column in Events and create a slicer based on the Area column of Areas then when you select an Event in that slicer then the Area slicer will only display areas for that Event.
