Tag Info

New answers tagged

0

You can also create a SiteColumn with a different name first and then change the displayname with powershell: $web = get-spweb http://yourweb $web.Fields["InitialName"].Title = "NewName" $web.Fields["InitialName"].Update() In this case you don't need to deploy a solution.


0

You can create site columns using c# with same display name and distinct internal name. The important thing here is internal name. See this code: string internalName = site.RootWeb.Fields.Add("XXX", SPFieldType.DateTime, true); SPFieldDateTime newField = (SPFieldDateTime)site.RootWeb.Fields.GetFieldByInternalName(internalName); newField.Title = "existing ...


2

If you limit the scope to the MSDN Walkthrough you linked, there is only one difference between Farm and Sandbox Solutions that is important. You could deploy the Sandbox Solution to SharePoint Online but not the Farm Solution. It's been a while since I looked at this but I'm 80% certain that when you deactivate the Feature, a site column created using CAML ...


1

In my experience, the only time you may want to use a Farm Solution instead of a Sandbox solution is if you have some site columns that are Managed Metadata or Lookup columns. The declarative syntax in your solution will only created the column, but in the case of a Managed Metadata column you will still need to connect it to a term set, and in the case of ...


1

First of all WSP Solutions are of two types. Farm based and Sandboxed. Sanboxed solutions are more restrictive in nature. They can be deployed by site collection owner whereas user needs to have administrative privileges to run or deploy Farm based solutions. Sandboxed solutions are uploaded in solution gallery and can be deployed from there. Whereas Farm ...


0

Just an fyi for anyone that is stumped on adding custom actions on task lists -- I've found for task lists, specifically, if you are creating a new View Ribbon custom action, you will need to change the Ribbon Location syntax to: Ribbon.Tasks.Actions.Controls._children instead of Ribbon.ListItem.Actions.Controls._children for all other list types.



Top 50 recent answers are included