12

The property mentioned by djeeg works if it is set on the list element in your schema.xml: <List Title="A List Definition" ... NavigateForFormsPages="TRUE"> This is the equivalent to setting "Launch forms in a dialog" to "No" under advanced list settings. It doesn't show up in the schema, but I've verified that it is still effective.


4

Do you want to get the information through code, or only through the UI? For example the ListTemplateId can be found as variable when you look at the source code of the site where the list is displayed (for example: var g_wsaListTemplateId = 100). You can get this value with javascript. Or you can use server API: SPList.RootFolder.Properties["...


4

The SPList.BaseTemplate property tells you what list definition was used to create a given list. Also, LINQ is by far the most efficient way to query all the lists in your site -- and this could obviously be extrapolated to query all lists within an entire site collection too (see Example 2 here). Creating nested "foreach" loops to manually enumerate all ...


4

Well you made changes to List Schema definition, changes will only be applied to New Instances of List not to existing one. You have to write additional Upgrader feature which will Add the view programatically. You can also look into the http://www.sharepointnutsandbolts.com/2010/06/feature-upgrade-part-1-fundamentals.html (Upgrade Feature Concept in SP2010)...


4

Yes I believe this is the case. When creating a List by the template shown in your screenshots a List Definition is also created, and then you can delete the List Instance. If you do this the List tab will simply not be clickable, and you can design your independent List Definition. Walkthrough: Create a Site Column, Content Type, and List for SharePoint


4

You can do this as follow- Add Site Columns to the custom Solution in the Visual Studio. Add The Content Type if Required. Create List Definitions & Associate the Content Type to the List (If required). Add the List Items in the List Instance by default. In the Items Here Deploy this solution & you can see the List with default items. For the ...


3

I assume you want to create a list definition based on existing list definition that comes with SharePoint or installed by other solutions. I would just use the VS.NET > Add New Item > List Definition and select Custom List as base. Then locate the existing list template directory in SharePoint root and copy 1) schema.xml and 2) element file ...


3

Trying to change the display name of the Title is going to be an uphill struggle: There are several versions of the same column, each with their own DisplayName (some of which are created in the list). If you open your list in SharePoint Manager, you'll see the various hidden Title fields. My advice would be to hide the title field (Hidden="TRUE" in the ...


3

Separating each question. Your Id of the <ContentTypeRef ID="0x0120" /> specifies a reference to a content type to associate with the lis you are creating through the list definition. In particular, you are telling to associate Folder Content Type. By the other hand in the Elements.xml, type="1116" is wrong because doesn't exist (take a look here If ...


3

In PowerShell you can add a library the same way as you would do in C# code First you get the Web $url = "<url web>" $web = Get-SPWeb $url Then get the template name of a definition To determine the name you can use someting like $web.ListTemplates | Select Name, BaseType Then take the name. The example below takes the document library ...


3

Have you tried the LCID attribute? I think that is the one you should try! <Field ID="{1706A5C3-AC44-4685-A075-6019FAF9D940}" Name="Budget" DisplayName="Volumen (in €)" Type="Currency" LCID="1033" /> ofcourse replacing "1033" with the wanted local (like 1045 for Polish) Edit Per MSDN: Optional Integer. The LCID attribute can be used to ...


2

If I'm not wrong you can create site template and then import this template in Visual Studio 2010. When the template is imported, you can choose what elements do you want to include in new solution. You can choose your list. The VS2010 creates all needed files. After this you can simply package this solution.


2

EnableContentTypes="TRUE" instead of EnableContentType="TRUE" (note the s)


2

There is no way to disable the ListTemplates in a Site Collection. So I'd do the following: Hide the following SiteActions menuitems (this can be done by removing them from the Masterpage or by implementing a custom action and web control like this) CreateDocLib CreateSite Create Create a menu item to my own page to create a Discussion board Implement ...


2

As mentioned, create a project with multiple features. Here is how I typically do it: Feature 1 = Site Columns and Content Types (sometimes I'll separate Content Types into different features) Feature 2 = List Definitions (aka List Templates) Feature 3 = List Instances (if applicable) Feature 4 = "empty" feature with Activation Dependencies on the other ...


2

Try this : <!-- Parent ContentType: Document (0x0101) --> <Field ID="{01854464-EABC-4726-A517-397A4EA224C2}" Name="dueDate" StaticName="dueDate" DisplayName="due Date" Description="dueDate" Group="MyDoc Content Types" Type="Calculated" Format="DateOnly" ResultType="DateTime" ReadOnly="TRUE" > <Formula>=DATE(YEAR(Created),MONTH(...


2

I don't think there is some other way to keep list definition synchronized if you make changes to deployed list via UI. For future reference I have found a quick tutorial on how to do this: Simple Way of Creating a SharePoint 2010 Custom List Definition However since you are developing custom list definition in Visual Studio the 'proper way' to achieve ...


2

I'm not 100% sure which users should be allowed to do what, but if you need to give difference Controllers control of difference list items then you could look at Setting item level security in an eventhandler


2

Well, I hate this kind of thing where I get something working only moments after posting a question, but in this case it seems that you can't use anything other than alphanum characters in the Name property of an SPField. I changed my name as indicated in my second update above (from "Company.Appname - Fieldname" => "Company.Appname.Fieldname" => "...


2

Make sure that the FeatureId attribute in your ListInstance matches the ID of the definition's feature. Make sure the Type attribute in your ListTemplate element matches the TemplateType of your ListInstance (in your case, 2010001) Put both at the same scope. If the definition is at the same scope as its list instance and properly referenced, SharePoint can ...


2

@Kate Ponomareva sorry for the delayed reply (wasn't online), follow below steps to add html form webpart 1 : through SPD, create your required forms for the respective list and set them as default or you could use the default form itself 2 : go to your sharepoint site, click on the list from View All Site content or Quick Launch 3 : in top ribbon click ...


2

Usually in Visual Studio; Tools -> Generate GUID


2

I found the mistake... The BaseViewId was 0. After I changed it to 1, the link under the View is correct. "Add new Item" fyi: <View BaseViewID="1" Type="HTML" WebPartZoneID="Main" TargetType="List" DefaultViewForContentType="TRUE" DisplayName="$Resources:core,objectiv_schema_mwsidcamlidC24;" DefaultView="TRUE" MobileView="TRUE" MobileDefaultView="TRUE" ...


2

According to msdn FieldRef element doesn't have ID attribute, I suppose this is the case... You should provide field internal name instead of ID.


2

I also encountered the same problem recently. I found this blogpost that explains the cause: http://srinivasananand.wordpress.com/2013/09/04/sp2013-sync-button-doesnt-appear-for-document-library-created-with-custom-list-definition-2/ and here he has suggested one work around: http://srinivasananand.wordpress.com/2013/10/10/sync-button-for-document-library-...


2

Your .cs, .ascx, .xml and .xsl files are only invoked when rendering the field, and each time the field is shown on forms & list views. The contents of the elements file will reference something in the Schema file, so the schema file is loaded first before the contents of the elements, and this is done only on Feature activation. For the rest, the ...


2

Try with the following code, Add-PSSnapin Microsoft.Sharepoint.Powershell [CmdletBinding()] Param( [Parameter(Mandatory=$true,ValueFromPipeline=$true)] [string]$Web, [Parameter(Mandatory=$true)] [string]$ListTitle, [Parameter(Mandatory=$true)] [string]$ListUrl, [Parameter(Mandatory=$false)] [string]$Description, [...


2

Your list instance must have a FeatureId attribute that maches your ListDefinition's feature. This is not added by default, so it's likelly that this is why you are getting "Cannot complete this action". E.g. <?xml version="1.0" encoding="utf-8"?> <Elements xmlns="http://schemas.microsoft.com/sharepoint/"> <ListInstance Title="ListDef" ...


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