Forum Discussion
Set values for Managed Metadata (aka Taxonomy) columns in PowerApps and Flow! (First Release)
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.
- Mikael SvensonJan 11, 2018Steel Contributor
That could be the case as I'm using content types and site columns. I've given details to Kerem Yuceturk so we'll see :)
- Mikael SvensonJan 12, 2018Steel Contributor
To follow up. My issue was that I have too many lookup columns (people, metadata) , hitting the REST column threshold. I can work around this limit, so nice to know what triggered it at least. Thanks for checking and confirming Kerem Yuceturk :)
- DeletedJan 11, 2018
Kerem has proposed using a Flow to update text columns with the MMD column values, which I've yet to try out as a workaround but should work :)
- Mikael SvensonJan 11, 2018Steel ContributorI would rather create Azure functions to solve this for me - which is an option. I would create a non-conencted PowerApp, using (custom) connectors to get people lookup, term lookup etc. Then send the data to Flow or another azure function to store it in the list.
I have mostly a create scenario, view/edit is not that important right now.
- Kerem YuceturkJan 11, 2018Microsoft
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: