Hot answers tagged

3

In SharePoint 2013, You can try Client Side Rendering. You just need to override the display template of FirstName. For example, Templates: { Fields: { "FirstName": { View: function(ctx) { var FirstName = ctx.CurrentItem[ctx.CurrentFieldSchema.Name]; return "<span style='color :#f00'>" + ...


2

SharePoint API has class and function SPContentTypeUsage.GetUsages that returns all content type usages in site collection. Is MSDN article there is an C# sample too. Also look at the accepted answer in this question . The answer is in PowerShell.


2

The advantage of creating it as a lookup column versus a static column is you can delegate the maintenance of the column to other users who might not be site admins. You give them the ability to Contribute to the underlying list to add/remove values as necessary versus having to elevate permissions for them to site columns.


2

The most important questions are: Will choices change often (e.g. more than once a year)? (if yes, a lookup field may be better). Who will update the choices? Only one "skilled" SharePoint power-user who will have "Manage" permissions on the list? Or many users, who should not have elevated permissions (in the latter case, a lookup field may be better). ...


1

Filters aren't true security as you note. You could add folders to the list and secure the folders, then only the users who have access to the folders would see the information below. Item level permission performance scales horribly and is a pain to maintain.


1

You could have a list with all of the information you need and also have a document library for the documents. In the document library have a column that is a lookup to the Sharepoint List so that you can relate the documents to the list item (or to multiple items if you use a multi picker). The benefit of using this method over Eric Alexander's is that you ...


1

You have multiple ways to achieve this: Approach 1: Create a custom permission level with access only to create item and not delete, edit. Break permissions if you want no one to edit the item. Create a SharePoint Group and add users who are supposed to create items in the list or library. Now only users will be able to create items and not able to edit ...


1

You can link your SharePoint list to an Access database and create SQL to update the data. See here: Connect your Access 2013 Web Apps to SharePoint Lists


1

It's quite simple actually. You need to open the list/document library in SharePoint designer, and on the right hand side you will find a group of files titled "Forms". Create a new edit form or a new item form as per your requirement. The designer will generate a new aspx file which you would be able to edit, and place your button wherever you need. To set ...


1

I'm not sure how it would work with a word document, but maybe you can look into using Microsoft Infopath forms? The forms use XML data which can be promoted into list columns. So users can fill out the published infopath template, and the resulting data can populated into the form library.


1

You can use Word Quick Parts and properties promotion: Create a document library. Add fields you want. Create a new Word document from the "New" button in the ribbon. Design in it the form as you wish. Place QuickPart (from the "Insert" ribbon of Word) to place doc lib fields wherever you want. Save the document back to the SharePoint document library. ...



Only top voted, non community-wiki answers of a minimum length are eligible