Set 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) and in Flow (single value for now, but multi-value coming soon...) Here's a sample multi-value taxonomy column that was tied to a termset for languages. We are not fully all the way there: the default values are not yet showing up if they are set, and we don't yet let you disambiguate between different paths while you are typing, but we think this is a great net new add for our customers who love and use the managed metadata columns. Please give it a try, and let us know your feedback. In your First Release tenant, you can create a new app, or custom forms, or go to an existing app and refresh the schema to get the new columns. We expect to start rolling out to Production in the last week of November if we don't hit any blocking issues.
Managed Metadata Column, Term Label Returns Some ID Instead of Actual String Value
I have a flow which will get file properties from a library that contains a managed metadata column. But when I run the flow, the term label value returns some ID instead of the actual string value. The actual Label value should be something like "Fire Protection" and not 109. I can't find a way to get the Label string using any other way. Is this the actual behavior or it's a bug? I'm not sure. Is there any other way to get the Label value? Thanks.
Site Columns don't become Crawled Properties (in page library)
Hi all, I hope someone here can help me as the admins in my organization don't seem to find a solution to my issue. My problem is this: I have site columns fed by my managed metadata. I use those site columns in document libraries and in the page library. My goal is to filter all documents and news posts using the PnP Modern Search (v4). This works very well so far - at least for the documents inside my document library. For whatever reason, however, when adding site columns to the page library instead and filling them with metadata, these metadata do not become crawled properties, i.e. they do not show up when I try to add them to managed properties (RefinableString). This is really odd and I suppose this is due to incorrect site settings. I was in touch with colleagues from my organization who run another SP communication site and who do not run into this problem, but where page library columns are readily available as crawles properties. Can anyone think of a possible solution? Many thanks!
Dynamically filter content based on page property
TLDR Is it possible to aggregate pages using a modern highlight content webpart an filter on managed metadata field to show child items? Filter should work dynamically based on page taxonomy field value. Like you could with classic page layout and PageFieldValue filter. More detailed question With classic webparts I was able to add a Content Query Webpart with a filter that would rollup other items (document, links, pages, etc.) that had the same metadata property as the current page, including the option to filter on managed metadata child items. See attached screenshot. This provided the opportunity to create a wiki template with custom properties, add a CQWP to the page layout, and rollup items by default on the same property. The end-user only had to create pages and specific the property of the wiki page, and voila: additional content appeared automatically. I would like to provide the same functionality with modern webparts. I can add custom (managed) metadata to modern pages. I can add a Highlight Content Query webpart to a template page, and filter on a property and specify the filter query manually. But it seems this cannot be accomplished dynamically. I don't want my end-user to edit webpart properties en fiddle around with queries etc. Why should they, they should only update the page properties and webparts should apply the filters based on the page properties. Preferably also respecting managed metadata field with multiple layers and be able to show child items. Can this be done with out-of-the-box SharePoint Online and modern pages? Or is there an item on the roadmap that would make this possible. Any tips are welcome.Error cannot save term in required managed metadata column
My SharePoint document libraries that have required managed metadata columns without a default term cannot save metadata if a user follows these steps: Create a new Word or PowerPoint document and start editing the content or name Close the document tab Go to the document library view to resolve the "Required info" prompt Use any properties controls -- sidebar, in app, edit in grid view -- to try to change the "Type of Document" column I created to select a term. The term will show briefly until user hits "enter" to escape and save the selected term Properties window refreshes, selected term disappears and messages say "missing required info" No issues with Excel. No issue if there is a default term, but I don't want that. I cracked open properties in Windows to see that the column on these particular documents is not getting saved as "Type_x200_of..." but "Type of" ...
Managed metadata term sets can only be 7 levels deep to be supported, why is that?
We need 10 levels in a specific cost center structure. What is the actual problem of having more than 7 levels. I never tried myself, and I guess that since MS says they only support 7 then it is actally possible to add more.Modern Library Managed Metadata modal dialog CSS bug?
Hi all, hoping you can help me. I have a document library (modern UI) that has a managed metadata column. Selecting one document, turn on the details pane and select the tag button to choose the correct term as value, the modal dialog pops up, but looks squashed on the left: This seems to be a CSS bug, since I have tested this across different browsers using a demo tenant. It appears to have something to do with the CSS property: "display: flex". Is there anyone that is experiencing a similar issue? Does anyone know if the is in fact a bug?
Group Connected Site Taxonomy Feature not activated
Hi, If you created a SharePoint Team Site that is connected to a Office 365 Group the hidden taxonomy Feature is not activated. So you can`t create a managed metadata field. Does any body know is there a reason for that or is it supported to activate the Feature? I successfully activated the Feature via PnP but it is a bit strange that it is not activated by default.Word quick parts - issues with managed metadata when converting word to pdf
Hello everyone, I am having an odd issue which I am not sure how to deal with. I have a site (SharePoint Online) with document sets and different content types. Within document sets I create various Word documents which I fill with data using Word Quick parts (data from columns). Everything seems to work fine until I export the file to PDF via Microsoft flow (when I open the original Word files, everything is filled in correctly). Most of the time, all the information is filled in, except of 2 quick parts, which are basically filled with managed metadata. For some reason, only these 2 are not getting the information, even thought the original Word document has those filled in (I basically take the same document and convert it to PDF file). I am not sure why this is happening. Also, one of my former colleagues has created a custom functionality to create PDF files directly on SharePoint (not using Flow), but the same thing happens. The only way when all data is filled in PDF document is when you convert file directly from word using File --> Export --> Create PDF. From what I see, it seems that in this process, quick parts have the issue with column types of managed metadata, as the other ones work as expected. If anyone has any idea why this happens, I would much appreciate it.
