Forum Discussion
Managed Metadata Column, Term Label Returns Some ID Instead of Actual String Value
I'm having the same issue. I'm using the "Get files (properties only)" action.
This is what I see in the raw output.
I haven't been able to figure out how to get the actual label name.
I have had a similar issue, when i am running Power Automate, Flow using the SharePoint, Get List Item, to return metadata value, labels.
the output returns the metadata ID, not the label that was requested.
This does not works on some lists and other are fine, they return the label.
After testing, lists that have been created using the 'From existing list' option,
create lists with Content Types, that are local to the list, (there parent is the Item)
Where as the lists that are working as expected, have been created manually with the Site Column and the Content Type being set up first, in the site, then added to a new list. This give you a parent Content Type in the site content type list
Note: Doing this manually or using PowerShell to the the list up both create list that does not have the metadata issues with Power Automate flows.
To resolve this I have rebuilt my problematic lists setting up the Content Type first manually (or with PowerShell) adding them to my new list and migrated the data.
Note: I create list like this ordinarily, but i notices this when you let the users lose with list creation, and they turn in to a 'Critical System' that needs some automation applied.
anyway, hope this helps.
- cwitzkeSep 18, 2024Brass ContributorThank you SO MUCH! I think you have diagnosed my problem as well as I have same error with some lists / flows working and some not. The most recent set of lists were created "from an existing list" and I am encountering the error. I expect it will be the same if we use the "Create a new library - from an existing library" too, which is a pain because I just set up a "template" library, and it isn't going to operate that way if it doesn't pull the metadata properly when I try to use Power Automate on it. That might explain some other weird behaviour I'm seeing in other libraries with metadata columns. Huh. Thank you thank you for the heads up!