New answers tagged

0

It may be worth checking the hidden list "TaxonomyHiddenList" to see if the permissions are correct. I have witnessed similar issues in viewing terms from the termstore just because this hidden list's permissions were set to "Unique" and had no permissions set. When this happens, very odd things happen where terms are concerned. Go to the hidden list : ...


1

SSPID is the GUID of you Managed Meta Data service. TaxonomyField.SspId Property You are on the correct place and getting the correct id. Do you have more than 1 MMS service in your farm? What error you are getting?


1

Any query can be "saved" as a URL. So you could create a links list that included the various queries that you expect end users to run. This TechNet article details some of the options for querying Managed Metadata fields. https://technet.microsoft.com/en-us/library/jj613136.aspx You are on the right track. You can either use the "taxid" version of the ...


1

The most common way would be to create your own content type, deriving from Document and add the custom column to this new content type. That way you would not run in to this kind of clashes with other OOTB content types that already inherits from Document. This custom content type could be created and published from a Content Type Hub, making it available ...


0

I've found a way to migrate the Managed Metadata into our test farm. It does not solve my timeout issue in Powershell, but the data got transferred with same term guids. Maybe someone needs to do the same. 1) Make a backup of your Managed Metadata by creating a SQL dump of the Managed Metadata database and transfer this dump file to your SQL system of ...


0

There are a few approaches to backup/restore managed metadata between environments. OOB, SharePoint 2010 allows for ONLY importing managed metadata in CSV format. You are required to use Powershell / Object Model to build the csv file. Here is a script that can do it. Managed metadata terms and termsets each have a unique guid. If you take a backup of a ...


2

Use the PnP PowerShell CmdLets, and you can do this with one line of code: Add-SPOTaxonomyField -DisplayName "Region" -InternalName "Region" -TermSetPath "Contoso|Region" Documentation Implementation



Top 50 recent answers are included