Forum Discussion
SharePoint list dynamic filtering on a multi-choice column
Hello,
I was wondering if anyone has a solution/work around for a limitation I'm running into with using dynamic filtering on one of my SharePoint lists.
The way I have it set up: there is a "Tags" column that has multi-selectible choices like "x", "y", "z", etc. The problem I'm running into is when you try doing dynamic filtering on the list webpart and want to view every item with tags "x AND y", it filters using the logic "x OR y". So, the output contains way too many unrelated items and the filtering is pretty much pointless.
This is on top of the limitation that you can only dynamically filter by 1 column at a time, which is why I needed to add every tag to a multi-selectable choice column in the first place.
Has anyone found a way around this? Or is there some solution I'm not seeing?
The behavior you are seeing is the native List web part’s limitation: dynamic filtering connects one source column to one target column, and a multi-choice selection is evaluated as matching any selected value rather than requiring every value. There is no setting in the standard web part that changes this to AND logic. A no-code workaround is to replace the multi-choice column with separate Yes/No tag columns, then create views that combine them with AND. If tags are numerous or change often, add a single helper text column containing a normalized key for each supported combination and filter on that value; keep it updated when items change. JSON column formatting cannot alter query semantics. If users must select arbitrary combinations at runtime, a custom SharePoint Framework web part or another custom interface is required. Test the design against indexed columns before scaling to a large list.
1 Reply
The behavior you are seeing is the native List web part’s limitation: dynamic filtering connects one source column to one target column, and a multi-choice selection is evaluated as matching any selected value rather than requiring every value. There is no setting in the standard web part that changes this to AND logic. A no-code workaround is to replace the multi-choice column with separate Yes/No tag columns, then create views that combine them with AND. If tags are numerous or change often, add a single helper text column containing a normalized key for each supported combination and filter on that value; keep it updated when items change. JSON column formatting cannot alter query semantics. If users must select arbitrary combinations at runtime, a custom SharePoint Framework web part or another custom interface is required. Test the design against indexed columns before scaling to a large list.