Forum Discussion
Kerem Yuceturk
Microsoft
MicrosoftSet values for Managed Metadata (aka Taxonomy) columns in PowerApps and Flow! (First Release)
Hi everyone,
As of today, you will be able to set the values of your managed metadata columns (sometimes also called taxonomy columns) in PowerApps (for both multi-value and single value) a...
Kerem Yuceturk This is great. I find one thing a bit weird. If I create a customized form for a SharePoint list using PowerApps all my choice/metadata fields are added to the forms in the app. If I however create a standalone PowerApp using the list as data, it skips all choice/metadata fields on the app it creates.
Is this a limitation/bug, or something which will be fixed? I tried it two different environments and experienced the exact same thing.
I want to create a form app, but need to move it between environments, so a stand-alone app should be the way to go, except I don't get all my needed fields. I'd hate to create a data-wrapper middleman service for this.
Kerem YuceturkMicrosoft
MicrosoftHi Mikael Svenson, I just tried this on some of my test lists by creating a new app from SharePoint UX, and got the taxonomy columns generated without issue.
Maybe there is some complexity with your columns that we are not catching in our tests? Could you send me the schema of your list in a private message to understand what types of columns you are dealing with?
Also, do the columns show up when you open the "Data" panel for your edit/detail forms like in the picture below? If they do, but they are not checked, is the problem fixed if you check the checkboxes?
Kerem Yuceturk Thank you for testing and getting back so quick, and I will get back to you tomorrow on this when at work. Good to know the behaviour should be equal. The list has two content types and exceeds the number of lookup columns (12) if you do REST against it, which could be an issue
I’ll report back once I have more info.
I didn't think that PowerApps had support for content type columns? At least, it's never worked for me. Whenever I query a list or library meta data, I am able to see any list/site columns, but ones added through the content type are not supported.
- Kerem Yuceturk
Hi Deleted, we have added content type support around 4-5 months ago if my memory serves me right. It is exposed as the {Content Type} column that is available for your use.
You should be able to change the content type, or look at this value and show/hide columns in your list through some If statements in your forms for the "visible" attribute.
Here's an example from a list that has two of them (Reservations, and Issue), and you have access to both the name and the ID:
