KQL Search with CollapseSpecification not working

[FranBor]

What type of issue is this?

other

What SharePoint development model, framework, SDK or API is this about?

SharePoint CSOM

Target SharePoint environment

SharePoint Online

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

• browser version
• SPFx version
• Node.js version
• etc

Issue description

I use KQL Search with CollapseSpecification to search within document libraries on several tenants without any problems, but on one tenant this does not work.

I have revised the search patterns and re-indexed the entire site collection but it is not working.
Is there any functionality/configuration I need to enable to make CollapseSpecification work in KQL Search?

I tried the following query with REST Api:

https://{mySharePointSite}/_api/search/query?querytext='test'&selectproperties='RefinableDecimal01'&collapsespecification='RefinableDecimal01'

with or without CollapseSpecification I get 3 results, all items have RefinableDecimal01=34 so the expected result should be 1

The same behaviour occurs with the CSOM code below:

KeywordQuery keywordQuery = new KeywordQuery(context);
keywordQuery.QueryText = "test"
keywordQuery.CollapseSpecification = "RefinableDecimal01";
keywordQuery.SelectProperties.Add("RefinableDecimal01");

Can you help me.

THX

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[github-actions]

Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.

If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.

We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.