Tag Info

New answers tagged

0

Create the list view with A Status column only. Then open the view in designer and drop B Status field inside A Status field (inside the same td of A Status)


0

If you look at the list item template (C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\CONTROLTEMPLATES\DefaultTemplates.ascx) you will find that the ChangeContentType control is used. You need to create your own control, inherit it from ChangeContentType control and override visible property. After this you should create ...


-1

Just create a link with the template file. You can find template url location from Document Library Settings => Advanced Settings ->Template URL


0

There are no out of the box content types like Excel,PowerPoint,One Note in SharePoint 2013. You need to create your custom content types and add it your document library.


0

Every SPList object has a 'DefaultView' Property, the Default View Property has a 'ViewFields' Property. Here's a link to the documentation on that Property as well as a code snippet: http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spview.viewfields(v=office.15).aspx If you want to access it via REST, it would be: ...


0

So, it turned out that somebody screwed up with the default Item content type and hence the Title column was not visible under the Item content type. And, hence also not visible under my custom content type, as it was inheriting from Item content type. While googling around, i came across a similar question here. Jason provided the STSADM commands for ...


2

Scenario 1: When you go to Site Settings --> Site Content Types -- > select any content types , then it will show you only Site columns, no list columns will be shown there. Scenario 2: You have a list , which is using a content type. Go to List settings--> Under content types select the content type . Here it will show both Site columns and List columns. ...


0

You can existing site column using powershell: $site = Get-SPSite -Identity "http://serverName:4001/" $web = $site.RootWeb $field=$web.Fields["Custom Site Column"] $field.Type= "Choice" $field.Update($true) $web.Dispose() $site.Dispose() But i think is the good practice as Joseph mention above is to create a content type which inherits from the issue ...


2

I would create a new content type that inherits from the issue content type. You could then remove and use the fields you need from issue content type. The created modified fields are system fields. These are usually defined in the base type item. http://msdn.microsoft.com/en-us/library/office/ms472236(v=office.14).aspx


1

After decompiling SharePoint DLL's (ILSpy ftw!) and checking the ascx templates, I found the issue. It's a UI bug in SharePoint! What happens is: During activation of the Records feature receiver, a different rendering template is set on all content types in the Drop off library. If you add rules later, they will get the default template! This custom ...


0

After adding the document content type/s to a library, add the library to a web page and set its toolbar to display. From there you can grab the code for the new button/template from the page's source code and paste into a CEWP. For a library with multiple document content types, enable only one at a time and grab the code for each separately. For ...


0

Create a base content type, and have all your child content types inherit from the base. Then create the routing rule on the base content type. ...of course, if you've already created the content types, and have data associated with them, you are out of luck. The wildcard syntax doesn't work the way I think you believe it does. It is meant to handle ...



Top 50 recent answers are included