Power Automate Managed Metadata Column Label Returns Numbers Instead of Value

[TestApp]

Hi.

I have a power automate workflow to get few column values of a document from a Library. And I have 3 managed metadata columns with values in Term Store. 

All I need is the the Label of those 3 term store columns. 

But when I run the flow, I only get the one column's label value. The other 2 columns are returning WssId in the Label field. Not the Actual Label. 

Here's the result from that Flow. 

First two columns returns some WssId in the Label field instead of actual Label value. 

But the third columns returns the correct value. And this one column allows multiple values. (I assume it doesn't have anything to do with the issue with previous columns.)

Is this a bug or a new feature? I'm facing this for quite few months and couldn't find any solutions. 

But when I use a PowerShell script to get the column values I can able to get the actual Label values. 

I can't even find any alternative for this in the power automate workflow. 

[NGUYENTHIHA]

Hi,

Any solutions for this,

I am also facing an issue with show label of managed metadata column in canvas app.

It shows number instead of label (even I don't know what is that number coming from).

Many thanks!

[quetzal]

Experiencing this also. It was actually pulling the text value fine initially, but has suddenly started pulling the numeric value instead despite it literally having the same expression in the field. I step back through the prior flow runs and see in the the raw input is the same in the two different flows but is somehow no longer pulling the term name but the number instead. 

[z3019494]

Same deal here but strangely, it's working fine on a standalone SharePoint site containing the Term Store, but the labels on a Team Site is not producing the intended result (e.g. the Label being identical to the WssId, is being pulled)

Site where it works (standalone SharePoint site)

Site where it doesnt (SharePoint site which is part of a Team)

[z3019494]

Urgh. Got it working by

1. Deleting the columns
2. Recreating the columns and linking to the term store again.

I suspect the reason why it was failing is that the list was created based on another list.

Moral of the story:

If you're going to create a new list based on another list with Managed Metadata, delete the MM columns and re-link!