Using SharePoint REST API with RenderListDataAsStream for getting Taxonomy metadata terms synonyms

[arunakshi]

What type of issue is this?

Question

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

SharePoint REST API

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: All versions of Chrome, Firefox, Edge.
• SPFx version: 1.9.1 & 1.10.0
• Node.js version : >= 10

Issue description

I am trying to find a way to get Taxonomy term label synonyms for list items.
Today I am getting only the Term Labels and Term Ids of the Taxonomy term for the list item currently using RenderListDataAsStream endpoint and selecting the Taxonomy fields via ViewXml.
${this.webUrl}/_api/web/Lists(guid'${this.listId}')/RenderListDataAsStream

<View Scope=\"RecursiveAll\"> <ViewFields> <FieldRef Name="Department"/> <FieldRef Name="_LikeCount"/> <FieldRef Name="_CommentCount"/> </ViewFields> <Query> <Where> <Eq> <FieldRef Name="ID"/> <Value Type="Number">${listItemId}</Value> </Eq> </Where> </Query> <RowLimit Paged="TRUE">1</RowLimit> </View>

I need to get now somehow the synonyms for the term label. I didn't find anything to get synonyms from list item metadata. The only way I found is loading entire termset terms along with labels and synonyms.

Is there anyway to get list item metadata along with taxonomy field labels and synonyms. Any ideas would be appreciated.

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.