Tag Info

New answers tagged

1

What I suggest is, Create Site Columns as follows <Field ID="{7A2608F0-A2AC-435D-8011-A8E640AB091F}" Name="ABCCode" DisplayName="ABC Code" Type="TaxonomyFieldType" Group="Custom Site Columns" Description="To display ABC Codes" ShowField="Term1033" Required="FALSE" EnforceUniqueValues="FALSE"> ...


1

As per you requirement, you have to make decision, whether you need Folder-SubFolder or document sets or sub site, as you need unique permission so it is little tricky. It also depend what type of documents you want to store in it. Manage Metadata can help you in views and search but will not help in permission management. I am thinking of create Folders ...


0

You can make use of document set. Document set are the best alternative for folders. So each document set will have unique permission to achieve it.


1

You don't have permissions for Managed Metadata so if you need permissions you have no way around of breaking permission inheritance. Be aware that if you have more than 5000 items on the list that have the permission inheritance broken, SharePoint will do extra round trips to SQL server and you will start seeing performance hit, source. So, consider the ...


4

Document management by metadata is the correct approach. I’ve worked both with Document Sets and without them. Document Sets have the benefit of storing documents that share one or more properties. They come in handy if you use a document library for storing multiple documents in an isolated environment. An example can be the use of marketing surveys records ...


0

In case you haven't already solved this issue, I found this post that explains how to import using CSOM PowerShell commands. https://cann0nf0dder.wordpress.com/2014/11/29/importing-taxonomy-to-sharepoint-using-powershell/ While I'd like to provide more details, that WordPress post is far too lengthy and may completely miss the mark if you're looking for a ...


0

To move the MMS from One server to other please follow the below steps. To export: $mmsAppId= "App ID Guid Placeholder" $mmsproxy = Get-SPServiceApplicationProxy -Identity "Proxy ID Guid Placeholder" Export-SPMetadataWebServicePartitionData -Identity $mmsAppId -ServiceProxy $mmsproxy -Path "Path to save Exported file placeholder" To import: $mmsAppId= ...


0

I had this problem with default Department term set in People group. I was unable to update it because the term set Owner was not set. And since this field is on the different tab I didn't see the validation message.


1

You can create Site Columns that have these properties: Person or Group and Metadata Keyword where users are allowed add keywords that doesn't exist. These site columns can be added to a Content Type which may be a Docement or a Page or anything else. Navigate to Site Settings and find the links you need in the group Web Design Galleries.



Top 50 recent answers are included