Tag Info

New answers tagged

0

I've finally got the upgrade done. Here's a list of actions I proceeded: 1.Update spsolution (.wsp file): Update-SPSolution -Identity SharePointProject58.wsp -LiteralPath "<Path>" -GACDeployment 2.Upgrade feature: $feature = $web.Features | where{$_.Definition.DisplayName -eq '*myfeature*'} $feature.Upgrade($true) And the most important ...


0

When you inherit a content type you inherit the fields or rather the field references as they are. There is no editing of fields as you noticed there is only a reference towards a field. So if you edit the field than all fields that have a reference towards that field will change as well. The only thing that is somewhat flexible is when you add or remove ...


0

Give versioning to the feature, i.e. VersionRange id, then remove from VersionRange the BeginVersion property. Exemple: <Feature xmlns="http://schemas.microsoft.com/sharepoint/" Version="10.0.0.0"> <UpgradeActions> <VersionRange EndVersion ="10.0.0.0"> <ApplyElementManifests> <ElementManifest ...


0

Okay, I had an idea, and creating it as a folder, then getting the item representation of that folder, and then changing that items content type and setting all the custom fields seems to have worked. SPFolderCollection folders = docLibrary.RootFolder.SubFolders; SPFolder newFolder = folders.Add(SALAE_docLibrary.RootFolder.Url + "/foo"); SPListItem ...


0

Try This SPList currentList = currentWeb.Lists["DocLib"]; SPField newField = currentList.Fields.CreateNewField(SPFieldType.Text.ToString(), "New Field2"); currentList.Fields.AddFieldAsXml(newField.SchemaXml, true, SPAddFieldOptions.AddToAllContentTypes); currentList.Update();


0

I know this question is old, but I have been facing a similar issue for the past 2 hours and I figured I would post my answer here. If you are creating your content types in your root site i.e. (Mainweb/) you must ensure that you are configuring MMS within central administration. Then you must activate "content type syndication hub" of the site collection ...


2

This is the default page of a publishing site. The content you see is in web parts, which can easily be removed. All of the links also exist in site settings, so this page is just trying to be helpful and present links for the most common tasks on a publishing site.


1

You can use a content type hub to allow the scope you need. Have a read though these articles: http://sharepoint-community.net/profiles/blogs/understanding-content-type-hub-cth-in-sharepoint-2013 This one is not 2013 but it is a useful FAQ: http://blogs.msdn.com/b/chaks/archive/2011/02/09/content-type-hub-limitations.aspx


0

This was fairly straightforward once I found where to look. Within the Pages library the choice column was copied when the content types were associated with the library. This copy of the choice column contained the old values. The fix was to remove the column from the library and re-add it. SPList list = web.Lists["Pages"]; SPField productGroupField = ...


1

Do you have really any issue, just asking the question...can a content type revert back to default by its own. I never see any issue with content type, where its go back to default one unless some body change it, manually or view workflow corruption etc. If you have issue, please share the more error detail.


0

I don't think the folder's CT is the same as your document's CT. If you're restricting by only the document CT then the folders won't be included in the results. You could restrict your search to just that document library and you should get both.


0

Here is the poowershell script to delete the Column from Content Type. #Attach to the web and content type $web = Get-SPWeb http://portal $ct = $web.ContentTypes["Sales Document"] #Get link to the columnn from the web $spFieldLink = New-Object Microsoft.SharePoint.SPFieldLink ($web.Fields["Aliases"]) #Remove the column from the content type and update ...


0

You have to specify the content type directly this way because SPMetal will treat it as a normal Item type which is already implemented My list is ProductProfile My Content types is ProductProfileCT


0

I figured it out--in SharePoint Designer for the List there's a section called Custom Actions: Thanks anyway :)


0

[Solved] The problem seems to come from a bug in Sharepoint where if a site column is listed a required, it will still show up as required even if the settings in the list are changed to optional. Workaround: change the site columns to optional without updating all the previous content of those columns. create the list; now those columns will be ...


1

This is a know issue with "Save Site As Template", this operation is not full fidelity Because as you said you can do it if you add the Site colum from SharePoint (from The U.I) and not from Visual Studio... Here, you can deduct that this issue is related to Visual Studio and What is happening behind the deployment Action... This Problem Has many ...


2

I think what you are hitting is that SharePoint, when a content type is associated with a specific lists, adds an extra GUID to the Content Type ID. This makes it a child content type if the original one, even if it theoretically is not. You should be able to get the correct parent content type by doing something like: $listct.Parent.Parent.Name


1

to my knowledge, creating a site template is not full fidelity! so that means you loose the lookup, alerts and workflows! to get around this issue you need to use: powershell: SPBackup-site http://technet.microsoft.com/en-us/library/ff607901(v=office.15).aspx or stsadm stsadm.exe -o backup ...


1

I'm pretty sure all content type definitions created in VS are, by default, site content types. There is no attribute in the Content Type element of a content type definition that allows you to target a specific list. Even if you were going to create a list definition declaritively in VS, to include a content type in the list you would have to create a ...


0

Solution: Provide the contenttype "myArticlePage" with a feature made in Visual Studio and activate the feature on the publishing site. This way, you can be sure that the SiteCollumns are the same and you can then use it as expected.


1

a coded solution. what your talking about is the field that you want hidden! SPField.Hidden() http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spfield.hidden.aspx and to get the field use: Fields.GetFieldByInternalName() http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spfieldcollection.getfieldbyinternalname(v=office.14).aspx ...


0

When adding field elements to the list, or adding fieldref elements to a content type, you can add the following attributes to hide the column: ShowInDisplayForm="TRUE" | "FALSE" ShowInEditForm="TRUE" | "FALSE" ShowInListSettings="TRUE" | "FALSE" ShowInNewForm="TRUE" | "FALSE" http://msdn.microsoft.com/en-us/library/office/aa543225(v=office.15).aspx ...


0

John-o is correct, you have some syntax errors. But since you have more than 7 IF statements, you'll have to link them together with & =IF([Stage]="0 - Not Applicable",0,IF([Stage]="1 - Identify Opportunity",0.1*[Confidence],IF([Stage]="2 - Qualify Opportunity",0.25*[Confidence],IF([Stage]="3 - Develop Response",0.5*[Confidence],IF([Stage]="4 - Submit ...


1

It seems you're missing some parenthesis or not calling AND quite right, here is what you currently have with some returns... =IF(Stage="0 - Not Applicable",0, IF(Stage="1 - Identify Opportunity",0.1*Confidence, IF(Stage="2 - Qualify Opportunity",0.25*Confidence, IF(Stage="3 - Develop Response",0.5*Confidence, IF(Stage="4 - Submit ...


0

I would suggest you to create a List and create folders for Each requirement folder and then tests folder followed by data sets and defects item. In this way your data will be organized form. So to have a defect item, It should be placed as follows: Requirements Folder > Tests Folder > DataSets Folder > Defect Item. To create a folder in Lists please ...



Top 50 recent answers are included