Tag Info

Hot answers tagged

15

Open the AllItems.aspx page for the specific list. Search for the <ViewFields> tag List item LinkToItem="TRUE" to whichever column you want the link: <ViewFields><br/> <FieldRef Name="Attachments"/><br/> <FieldRef Name="LinkTitle"/><br/> <FieldRef Name="linkThisColumn" ...


12

The design intention of content types is to support re-use of the list schema (or behaviours). So if there is a requirement to create a lot of lists with the same structure, which is often the case, then the content type enables this. It would be unacceptable to have to create list schemas individually in this situation and would result in repetitive ...


9

Creating site columns is the right way to go. You can add a list column to a list or library that is associated with a content type, but it isn't the same. The point is really to define your data properly. I kind of think that it is more likely that you are "polluting" the environment when you create the same field 10x as a list field versus a Site ...


9

Q: Is there a max number of columns in a sharepoint list? A: SharePoint Server 2010 capacity management: Software boundaries and limits / Column limits Q: Can we use reporting services to read from two lists? A: Yes: if you are using SQL Server 2008 R2 reporting service Q: Is it possible to display information from two lists in a single view even if the ...


9

Do you try this solution? In this solution you should modify field declaration on a view through SharePoint Designer.


8

In the Column Validation settings (Edit the Column and it is an expandable section near the bottom) you can use this formula: =ISNUMBER([My Column]+0) Just Replace My Column with your actual Column's name


8

Next time you perform the changes to the ContentType make sure to push changes to the lists while updating the ContentType. For now, you might need to perform some clean-up job here, just to make sure the field is deleted from all the lists, with your Custom ContentType. Use the following PowerShell script for clean-up! VĂ„rsegod :) Add-PSSnapin ...


8

I'm assuming you provisioned the column as a site column. The next thing is to make sure to push the changes to the down to lists and content types where this site column has been referred (which apparently you haven't done it). So, I would recommend to delete the old definition and provision the column again! See an example below where I am using the ...


7

The solution is two fold - first the content type defination needs to have inherit set to false, and the title column needs to have sealed to true (see below). Second issue is that the view will still show title (but the add new item form will show the correct display name). To correct the view a custom list must be defined <?xml version="1.0" ...


7

AvailableContentTypes is a read-only collection. Use SPWeb.ContentTypes instead.


6

What Bill (@SPDoctor) said. It depends. Related to #3, as the solutions you work with get larger, you will tend to split up your solutions across several Site Collections. Since Content Types has site collection scope, this can become a problem if you dont want to have redundant maintenance of your content types. To solve this you can use the new SP2010 ...


6

If you're trying this for SharePoint 2013, change "LinkToItem" to "linkToItem" <ViewFields><br/> <FieldRef Name="Attachments"/><br/> <FieldRef Name="LinkTitle"/><br/> <FieldRef Name="linkThisColumn" linkToItem="TRUE"/><br/> <FieldRef Name="data_x0020_column"/><br/> <FieldRef ...


6

Solution Packages - whether Farm or Sandbox - are still the way to go for deploying site columns and Content Types. With an "app", you can only deploy these artifacts to the app itself, not to the host SharePoint site (and I'm a little peeved with Microsoft for not making it more clear what you can and can't do in an app). And yes, Sandbox solutions are ...


6

From SP2010 and forward we have not used solutions / features for this. Instead we use PowerShell to do this programmatically using server side API's. By doing this we avoid "unghosting" the content types (as doing it declaratively does) and we also avoid having to deploy a package which include resetting IIS. In SP2013 we continue doing this, but since we ...


6

Ever since v1 of SharePoint Team Services, Microsoft has used OWSSVR.DLL to remotely invoke functions against SharePoint. It is part of SharePoint Foundation Remote Procedure Call (RPC) protocol. To read more about the OWSSVR.DLL command follow URL Protocol from Microsoft Blog. The query: ...


5

yes, it is possible. In technical terms, you need to create a new field type. Check the article below in SharePoint SDK to get started. http://msdn.microsoft.com/en-us/library/bb862248.aspx


5

They are documented here


5

I found these two PowerShell posts from Phil Childs quite helpful in my attempts (I presume you are looking for a PowerShell approach) - Export and import/create site columns in SharePoint using PowerShell Export and import/create site content types in SharePoint using PowerShell


5

You could utilize the content syndication hub and create a site column there. Add it to an item content type and syndicate that content type to all site collections. At which point that column should become an option to use in all site collections. This is in theory of course but it should work.


4

I have created a blog post on how to deploy a content type and its fields on SharePoint 2010 using Visual Studio 2010. Can you check if my approach is similar to yours? http://www.koenvosters.be/post/howto-build-a-deployable-content-type-for-sharepoint-2010.aspx


4

Isn't too difficult really, in the FeatureActivated method, you just create a new SPieldLookup (using SPWeb.Fields.AddLookup() for the SPSite's RootWeb), and set the properties for the SPFieldLookup as required. First time doing it? Bit tricky if you've never made a FeatureReceiver before, let me know if you need a tutorial do that, and here's some sample ...


4

Out of the box, there is no easy solution. I recently had to move some site columns from development to production and had to resort to some custom PowerShell script. There's also no easy way to copy content types to another environment and/or collection. In short, it can be done but you'd need to write some custom PowerShell to do it.


4

There must be an existing field with that Guid in your content database. Have you tried it with a different Guid? Or possibly there is a field with the name Tab1Link but a different display name, or hidden. You might try a different name also.


4

I always create Site Columns and Content Types. Harsh experience has told me that anything implemented will probably seen as a cool idea by someone and will request it to be implemented elsewhere on the same site collection. If you have a hierarchy of content types in use across multiple lists inside web sites, and a change request means you need to, for ...


4

SharePoint has no ability to assign meta-data to a Site Collectin or site directly. There are a few approaches to simulating it for the purposes of search and navigation: 1 - Use the Site Directory. although the 2007 Site Directory was deprecated, it still exists on SharePoint 2010 (for upgrade compatability) and you can turn it on and use it the same as ...


4

Yes, you can specify it. Example: public static readonly Guid MyFieldId = new Guid("{CC1E421C-29BE-4373-81D0-55D5D64B2E3D}"); public static readonly string MyFieldDefXml = "<Field ID=\"{CC1E421C-29BE-4373-81D0-55D5D64B2E3D}\"" + " Name=\"MyFieldName\" StaticName=\"MyFieldName\"" + " Type=\"Text\" DisplayName=\"My Field Name\"" + " Group=\"My ...


4

You can use LinkToItem, LinkToItemAllowed and ListItemMenu properties of SPField. If you want field to show link to item's display form you need to set LinkToItem property to true and LinkToItemAllowed property to Allowed. If you want to add context menu to field you need to set ListItemMenu to true.


4

John, if you are creating the site columns from the visual studio use the DisplayName property of the field for your case <Field ID="{2690E8BF-0801-408A-8445-93D816DF5D29}" Name="LastName" DisplayName="Last Name" Type="Text" Required="FALSE" Group="Custom Site Columns"> </Field> <Field ...


3

I have noticed that if you deploy a site column in a feature, then retract the solution, then deploy again, the feature is no longer listed in site columns. However, if you do an IISRESET and then check site columns, the column reappears. This suggests that SharePoint is cacheing the schema at some level. So my recommendation would be to force an iisreset ...



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