Ask anyone in the industry, I’m a total SharePoint homer. I defend SharePoint in all conversations and always look for the silver lining when problems occur or when users have interface related complaints. However, I learnt from an early age that it is important to understand the good and bad to be able to have an informed discussion when the time comes.
Keeping within this theme, I have been keeping a list of items that I would love for Microsoft to improve on. Here are details on 3 of them:
1. Content Type Management
Content Types are essential to any properly deployed SharePoint environment. The issue with it is not the creation, but rather the management of it. When trying to remove a content type from an environment SharePoint doesn’t tell you where a particular content type is in use, it simply states that it is in use.
// Suggestion
Rather than simply noting that it is in use, please tell the administrator where it is in use.
2. Inline Editing
I recently discovered this nifty feature (blush). Now that I’ve discovered it, I’ve sadly found that it has some limitations. For one, a user is not able to edit the content type of a particular item.
// Suggestion
Although I’m sure there is a solid technical explanation for this, I suggest allowing for the editing of content types in inline editing which will greatly enhance the user interface for users that are migrating content.
3. Managed Metadata in Datasheet View
Managed Metadata is one of the BEST new features Microsoft introduced with the 2010 version of the product. As the feature is brand new, it does pose a couple of challenges specifically in the migration arena. When uploading a ton of documents (via explorer view), the users would typically view a list in “Datasheet View” and then simply bulk edit the columns. Unfortunately, columns based on Managed Metadata cannot be edited in Datasheet View.
// Suggestion
Please enable the ability to edit columns based on Managed Metadata to be edited in the Datasheet View. This will make migrations a lot simpler, especially considering the number of clients that are coming from a choice column type of environment.
Conclusion
SharePoint has taken many leaps forward with each updated version. Here’s hoping that the innovation and attention to detail continues.
Francois,
Although I would welcome item #3, the ‘problem’ is not as easy as enabling a feature. No custom field types are available in DSV, and this includes the Microsoft custom field types like MM and BCS columns, plus any custom field type you may develop yourself, or buy from a third-party.
Remember that the DSV is an ActiveX control, not an HTML control. The rendering of an ActiveX control is vastly different from what can be done in ASP.NET. The ActiveX control renders only core field types because it is hard-coded with the display method of those types only. It would be impossible to create a control that would render any possible field type because Microsoft has no idea how you want your field types rendered, and there’s no way for you to modify the DSV control so that it can render the fields the way you want.
What Microsoft _could_ have done is develop an ASP.NET control instead, that would mimic the DSV. It’s certainly possible, but it would mean the death of the DSV as we know it, and increase the complexity of creating custom field types, which already is about as complex as doing rocket science while blindfolded and drunk.
.b
I agree with all your comments. I personally think it’s about time that MS dump the ActiveX DSV and replace it with a web based datasheet view control, which really isn’t that hard to do if you think about it. Not having custom field controls display here is actually quite irritating.
Thanks for the comprehensive explanation Bjorn. I’m very interested to see what Microsoft come up with in versions to follow. Great insight!
Inline editing also has some issues with grouping.
You can add Managed Metadata support in InfoPath forms – thats a big PIA
Great list. It would be a good thing to add a list of “community wants” that people could vote on. If it has enough contributors and enough voters and seemed valid, maybe the MSFT team would buy into it?
Sounds like a great idea, wonder where would be the best place to host such a list? I do however know that partners that are part of the TAP programs are able to give input into future versions. My previous company, MINT, served on the SharePoint panel for a while. I’m working hard to get IMMIX onto it in the not too distant future. Thanks for the support, keep reading.