Skip to main content
Share Your Experience: Take the 2024 Developer Survey
8 votes
Accepted

Difference between Feature ID and Solution ID

Solution id is identity of Solution package (.wsp file). If you are deploying wsp file, it will check solution id. If exists, it will update solution. Solution contains all the features, assembly, ...
Viraj Gorajia's user avatar
7 votes

How to remove orphaned features

To my surprise this worked for me: stsadm -o uninstallfeature -id <id-of-feature-missing> -force Found in this blog post Sharing Minds - by Anthony Butcher
spankmaster79's user avatar
4 votes
Accepted

How to move a feature from "Manage Site Features" to "Site Collection Features"

Make the feature scope in Visual Studios be "Site" instead of "Web". https://msdn.microsoft.com/en-us/library/ee231541.aspx
Mike's user avatar
  • 12.2k
3 votes
Accepted

CSOM Powershell to check if feature is activated

There can be better and different ways to check if Feature is activated or not. But once I used below code. Connect to your site collection using CSOM code, and load feature as below. $FeatureID = "...
Asad Refai's user avatar
  • 5,981
3 votes

Difference between Feature ID and Solution ID

Solution Id- A WSP contains unique / single Solution ID. One solution / WSP can contains many feature ID's, depending on the requirement. Feature ID- - Feature Id can be multiple in a single ...
Ram's user avatar
  • 2,444
3 votes

How to remove orphaned features

You can try this and second Reference, this one I have refered fist time. For this you need the add the Feature Id and then -Force is important. Without force it works sometimes but definitely works ...
Ram's user avatar
  • 2,444
3 votes

How to remove orphaned features

I used following command to remove feature from Site Collection Administration : Features interface stsadm -o uninstallfeature -id <GUID> -force GUID of feature (which you want to remove) can ...
Farhan Jamil's user avatar
3 votes

Feature has already been installed. Use the force attribute to explicitly re-install the feature

I had this same issue and found that it was because of Orphaned Feature. There are chances that whenever you remove wsp from farm and redeploy it, then Feature associated with that wsp might not got ...
Vishal_chorghe's user avatar
3 votes
Accepted

SP2019 - Site Collection feature "SharePoint Lists and Libraries experience" missing

You are not missing anything. SharePoint 2019 doesn't have this feature. It is only available in SharePoint online. If you want to disable the modern experience in SharePoint 2019, you could use the ...
Michael Han's user avatar
  • 5,201
2 votes
Accepted

feature is site-scoped and cannot be added to the web sharepoint 2010

Site features (here site means "site collection", while web means root-site/sub-site) can only be activated at a site-collection level (i.e. from the root-site of a collection, under the &...
Evariste's user avatar
  • 9,731
2 votes
Accepted

How to set master page on team sites?

Firstly I agree with @Aveenav that you should look into the building wsp package, that will follow Sharepoint model, it will place the master page in layouts directory, push it if you connect servers ...
Marek Sarad's user avatar
  • 3,540
2 votes

Error occurred in deployment step 'Activate Features': Feature with Id 'xxxxxxxxxxxxx' is not installed in this farm

The solution I came up with is a temporary fix. I created a shell script to retract, remove and redeploy the solution. So at first I would have a dedicated location to publish my .wsp file than a ...
Muhammedh's user avatar
  • 1,157
2 votes

Feature is not displaying

If you have recently added the feature to a solution file already deployed, it will not immediately show up. You will need to check for existing features using power-shell then install it. ex. ...
Jordan Brobyn's user avatar
2 votes
Accepted

Limiting feature to 1 web application

This is happening because the feature files get deployed into the File System and it gets picked up by all web applications. There is no straight forward solution to this problem. The one workaround ...
Amal Hashim's user avatar
  • 28.3k
2 votes

Error occurred in deployment step 'Activate Features': The list "Lists/Issue Manage" doesn't exist. Please fix the ListUrl attribute

There seems to be some discrepancy. The error you are getting shows the Url as Lists/Risk Issue whereas the Url present in elements.xml file is Lists/Issue Manage. ListUrl attribute works for Web ...
Nadeem Yousuf-AIS's user avatar
2 votes
Accepted

Recommended way/Best Practice to create a sub-site with RunWithElevatedPrivileges inside my Event Receiver

For creating sub sites in event receiver you would need to create new instance of SPweb via url because of RunWithElevatedPrivileges. Also your worry on below Calls to the Update method on these ...
Siddharth Vaghasia's user avatar
2 votes

Difference between Feature ID and Solution ID

Solution ID: ID of the Package (.wsp file), That are you going todeploy Open the solution package file in VS Click on the package designer Open the Property window and scroll down the the Solution ID ...
Akshay Dattatray Nangare's user avatar
2 votes

Error "Feature schema contain wrong field name" when trying to create a new site based on a site template

Workflows, designed in the SharePoint designer use hard coded GUIDs so they do not play nice when exporting/importing including saving site as a template. What goes wrong I guess, is that the workflow ...
Tsvetelin Pavlov's user avatar
2 votes

Unable to deactivate the "Video and Rich Media" site collection feature "Cannot deactivate the feature because the Video Set content type is in use. "

Does that feature create any new lists or libraries? A content type is "in use" if it has been added to a list or library. So if the feature adds a new list or library that includes the "Video Set" ...
Dylan Cristy's user avatar
  • 12.7k
2 votes
Accepted

Cannot Extract Microsoft.Sharepoint.Client.Feature.DisplayName Property

You need to explicitly load the display name property of the feature. In CSOM unlike SSOM, it (mostly) only gives you only the properties that you ask for. Try either of the below two approaches, ...
Gautam Sheth's user avatar
  • 30.9k
2 votes

How to load FeatureDefinitionScope value via csom?

In CSOM Feature Object, there is no "FeatureDefinitionScope", please check the documentation: Feature properties If you are using SharePoint On-Premise Environment, you can use the Server Object ...
Jerry's user avatar
  • 2,583
2 votes
Accepted

How to load FeatureDefinitionScope value via csom?

With your code, you will only retrieve all features with scope "Web". There is actually a difference between features scoped to a site ("Web" class) or to a site collection ("Site" class). The ...
Anon's user avatar
  • 805
2 votes
Accepted

Use custom Feature Icon for SPFx

Yes I agree that it’s not possible or recommended . SPFx uses the Feature Framework (elements.xml) to handle features and it does not have a native api to set the image. (There were workarounds ...
Vardhaman Deshpande's user avatar
1 vote
Accepted

Sharepoint 2013 designer's ribbon doesn't have the "Stage" feature

Are you using a SharePoint 2010 workflow? You can check the workflow type in Workflow Settings. If you want to use the feature "transition to stage", you can use a SharePoint 2013 workflow. The only ...
imp. MSFT's user avatar
  • 1,321
1 vote
Accepted

How to hide existing Custom Actions (via Feature) in Sharepoint 2010

Go for custom Feature upgrade, No doubt in that. Reasons: Why to have a feature that kills another feature. Extra resource, extra load on SP servers. Not a good solution. Feature upgrade is easy, ...
DvG's user avatar
  • 2,332
1 vote

Returning an error message inside my event receiver using "SPEventReceiverStatus.CancelWithError;" will redirect to "Server Error in '/' Application."

I highly suspect you actually have another (real) error in the code in case the ER runs in the context of the issue tracking list (e.g. a field missing, an internal name misspelled, ...) First things ...
Evariste's user avatar
  • 9,731
1 vote
Accepted

Forcefully delete Home Page of a site programatically

The error is pretty much self explanatory. You need to set a different page as welcome page first and then delete your current welcome page. Try and modify below code as per you requirement: using (...
Gautam Sheth's user avatar
  • 30.9k
1 vote

Create and deploy ListInstance without ListDefinition in a feature

Forget about features and list definitions for this! Instead, provision your site columns, site content types and lists with client-side code (CSOM/REST API). Use the Office 365 Dev PnP Provisioning ...
Lars Fastrup's user avatar
  • 3,140
1 vote
Accepted

modify my sub-site Quick Launch link title from "Home" to be equal to the Sub-site title, inside my event receiver

Add below code to update quick launch: SPNavigationNodeCollection nodes = newSite.Navigation.QuickLaunch; foreach (SPNavigationNode node in nodes) { if (node.Title == "Home") { ...
Gautam Sheth's user avatar
  • 30.9k

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