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!
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.
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.
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.
Filtered news (custom categories with managed data) do not appear to visitors
Hi everyone, In my SharePoint Online hubsite, in the page library, I've added a column for categories. This column is of the Managed metadata type. I added the categories to the terms store and tagged the news accordingly. In the Home page, I have three news webparts that are filtered with the created categories. Now, news is displayed correctly in each webpart for owners and members. However, the webparts don't display news for visitors except in the webpart where there are no filters and uncategorized news is displayed. How can I solve this problem?Sharepoint 2019 Managed Metadata
I am supporting a client Sharepoint 2019 farm. There is Global Navigation driven by Managed Metadata. I am using Term Store Management tool to create a Master Top Navigation - term sets and terms. There are multiple sites and subsites that are configured for this farm. I have created different term sets for each sites/subsites. I have pinned the terms with the children to all the sites and subsites. The issue is that if I change a URL for any terms on Master Top Navigation, it does not reflect to the sites and subsites using that. Is there an easier way to accomplish this?Managed Metadata property cannot be selected on News Link in Site Pages Page Library?
I have added a managed metadata column to the Site Pages Page Library on a SharePoint site. When I edit the properties on pages and news posts, the managed metadata property can be selected. However, when I edit the properties on a news link "page," the managed metadata property does not display and cannot be selected. Why isn't the managed metadata property available on news link pages?
Not setting mandatory managed metadata does not throw any error
Hi everybody, I am using the Migration API to create a document on SharePoint. I have a managed metadata field which is mandatory on SharePoint content type. If I don't set the value on the Manifest.xml file I got no error from SharePoint and I want to have a message if this happens. Do you know how to force SharePoint to send you a response or how to identify if a mandatory field is missing?
Tags with keywords in SharePoint
I know much about SharePoint metadata already. Also about the term store and the content type hub, where I can assign content types to many SharePoint pages. What I don't know is a smart way how to implement tagging. My scenario looks like this: 1. We have many SharePoint pages for our customer projects, each one for a machine we sold to a customer. 2. Sometimes failures in our customer projects happen. Those failures are repeating through many of our projects. 3. Each failure has a name 4. A failure can be described with different keywords in different languages. For example: 1. Name: Ram broke down Search terms: Ram break, Ram failure, Hopper leackage, Stempel fehlerhaft, ... 2. Name: Oil too hot Search terms: Oil issue, Öl zu heiß, Öl boiling 3. Name: Pressure too high Search terms: Pressure problem, Druck zu hoch, ... If a failure happens, people should be able to assign the Name of the failure to a set of files (a document set, a library or something similar) If other people search later for specific search terms, the cases should be found. For example: In ten different SharePoint pages I assigned the "Ram broke down" failure to a set of documents. If people are now searching for "ram failure", they should find all ten SharePoint pages, because "ram failure" is a search term for the failure "Ram broke down". However, with normal metadata something like this cannot be archived. One idea would be to use a managed metadata field for each failure and store all search terms below it. But assigning those to documents will be tedious, because all "search terms" have to be added manually. There must be a better idea... Do you have any alternative solution?
