owstaxidmetadataalltagsinfo managed property in search api doesn't contain all managed metadata column data

[ishanisuchak]

Target SharePoint environment

SharePoint Online

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

SharePoint REST API

Developer environment

No response

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: Version 94.0.4606.81 (Official Build) (64-bit)
• node version: v10.23.3

Describe the bug / error

We have a custom site column "HubNewsCategory" which has terms in it and the site has been created more than a month back. So, we are sure the data is all crawled. We have also reindexed the site and the lists multiple times.

There are two crawled properties created for the column:

1. ows_HubNewsCategory
2. ows_taxId_HubNewsCategory

We tried mapping “ows_HubNewsCategory” to a new managed property and that returns semi-colon separated labels for the selected terms as expected.

But the OOTB created managed property owstaxIdHubNewsCategory remains empty.

We also tried mapping "ows_taxId_HubNewsCategory" to a new managed property and that too remains empty.

It looks like “ows_taxId_HubNewsCategory” crawled property doesn’t have any value, so it doesn’t get propagated to owstaxIdHubNewsCategory and owstaxidmetadataalltagsinfo managed properties.

Steps to reproduce

1. Create a site column called HubNewsCategory
2. Map it to any term set
3. Add the column in a list
4. Fire a search query and check if owstaxidmetadataalltagsinfo managed property has the value for the HubNewsCategory column in it.

Expected behavior

owstaxidmetadataalltagsinfo managed property should contain the values from all the managed metadata columns in a list.

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.