ListView UI - Content Type filters inconsistency

[ypcode]

Hi there,

We discovered a strange behavior in the OOTB list view filters especially for Content Type filters.
It looks like it started happening since the recent UI rollout.

IMHO it is a UI bug since the UI does not behave consistently for Content Types filters depending on the "entry point".

Let's take a library with multiple content types applied to it. (At least 4 per my tests) with multiple documents having different content types

If we filter the content type by right clicking the Content Type column header > Filter and select 3 content types

We get the expected result, Only the documents with the filtered content types

But, if we use the filters panel

We select a first Content Type, this works

If we select 2 or more content types, then the filtered results are empty

But wait, If I then unselect the second content type, the filtered results come back BUT , I now see the ID of the content type as selected filter:

Also, if I click the "See all" link with 2 content types selected, I see a list of duplicated content types (and duplicates are selected/unselected together with ticking

With a bit of investigation, we also noticed that the method that works generate a URL with the name of the content type in the query string parameters, whereas the values are the IDs for the method that does not work

URL that does work :
https://xxxx.sharepoint.com/sites/Conferences/Documents%20partages/Forms/AllItems.aspx?FilterFields1=ContentType&FilterValues1=PVX%20Received%20Invoice%3B%23Document&FilterTypes1=Computed&viewid=4447b6f0%2D1f94%2D4324%2D805f%2D9b2c0e7475bb

URL that does not work : https://xxxx.sharepoint.com/sites/Conferences/Documents%20partages/Forms/AllItems.aspx?FilterFields1=ContentType&FilterValues1=0x01010083FEC5D8D3616644A6A8EDCC6E85941C%3B%230x0101004FD1D8AA2681A94983C7D079D33C99820037683A3469C6914E9440E2B23856ED08&FilterTypes1=Computed&FilterDisplays1=PVX%20Received%20Invoice&FilterOp1=In&viewid=4447b6f0%2D1f94%2D4324%2D805f%2D9b2c0e7475bb

Could you please have a look at this ?

[Ashlesha-MSFT]

Hello @ypcode,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.
If you don’t receive a reply within two working days, please use this escalation form to escalate.

[Ashlesha-MSFT]

Hi @ypcode,

I’m trying to reproduce this issue but I’m seeing slightly different behavior.
I’ve enabled content type management on my document library and added multiple content types. I also have documents assigned to those different content types.
However, in the Filters panel, I’m only able to see one content type listed, instead of all available/used content types.
Because of this, I’m not able to reach the scenario where selecting multiple content types results in empty results.
Could you please confirm:

• Are all your content types actively used by documents in the library?
• Does the issue occur in a specific view or with any additional column/view configuration?

Thanks!

[ypcode]

Thanks for investigating @Ashlesha-MSFT ,

Just to make sure,
I tested it now on another existing site and created new blank document library, enabled content types management and added 5 "built-in" content types

on the classic view settings page, added the Content Type field

Added a bunch of dummy documents and applied several content types to chunks

Clicking the Filters button opens up the filters pane

So yes the filters pane only shows the available applied content types to documents, If I add a few more documents and leave them the Document content type, it then shows up too (and the "see all" link appears too starting 5 different applied content types

[Ashlesha-MSFT]

@ypcode,
Thank you for the detailed steps and additional clarification — that really helped.

I was able to successfully reproduce the issue following your scenario with multiple content types and documents assigned across them. The behavior you described is consistent.

We will be raising this with the engineering team for further investigation.

Thanks again for the thorough repro steps — they were very helpful in isolating the problem. I’ll keep you posted here as soon as we have any updates from the engineering team.