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.
Friendly URLs "double up" in term-driven navigation on Modern pages
Hi everyone, I'm setting up Term-Driven pages for the first time in my environment, and I noticed that when I create a friendly URL, the friendly term I enter is referenced twice in the generated URL when viewing the navigation on a page using the Modern experience. Screenshots say it all, sorry for potato quality: We have a sandbox environment too in a completely separate tenant, and it has the same issue. Any workarounds?Term GUID showing in sharepoint list filter
I'm adding metadata to a sharepoint list via power automate. From testing and other posts, below is the fomat that I have found to work to add the term to the list. Issue is, when I filter the list, I get the Location + its term. It appears that the metadata is being added to the list properly. Am I passing the wrong string in power automate or any ideas on why the guid is showing in the filter?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?
Tracking usage of terms in Term Store?
Does anyone know of a tool that can provide metrics on the usage of terms in the Term Store? In order to maintain taxonomies effectively, it would be really useful to know how often terms are used: Terms that are rarely/never used should be reviewed for value, and updated or merged with other terms. Terms that are used much more than other terms could be divided into more specific terms. Obviously this would only be possible with metrics on how many times each term is used...any tips are appreciated!
Can I use the term store to access a list of my projects? or use a list is better?
I am totally new at SharePoint, lists, term store, and so on... I'm building a document library to store all our approval drawings, emails, etc. All those documents are tied to a project number and name, I have a list called Projects, but I found it difficult to share it with other sites. Would the term store be a good way to contain these project numbers and names, so I can use them in different lists? If yes, could I have any suggested links or ways to do this? Or if the use of my existing list called "Projects" is still better for this situation even if sharing it is difficult. Hope I have put this clearly. Any help or suggestions are welcome. Please let me know if any more details are required. Thanks everyone. Eric
