The ability to create lookup fields without featurereceivers...... and more documentation!

Ability to associate documents with each other, and check out multiple documents at once.

Better blog functionality... the closer to Wordpress or Typepad, the better.

Store documents outside of DB. Make lists unique tables within the database. Multiple checkout and check in.

It's too late to wish for things in vNext, time to ask for your v15 wishlist before the v15 design is baked (which apparently they're already talking about what goes into v15.) Unless something changes drastically in how the Office/SharePoint team takes customer input of course.

Fix that blasted webdeleted.aspx! As simple as that is, it's a thorn in my side...

I have three specific things I would like to see. 1. An improved Datasheet view. This is one of the most often used features that has many issues (namely around lookups and certain field types such as users/groups). If all the fields could just be modified in this type of view en-masse it would go a long way in getting people working on collaborative lists instead of excel for non chart/complicated calculation documents. 2. I would really like to see the content query webpart improved. It has such great potential but it's current design makes it difficult to work with. Requiring importing and exporting to customize the look and roll up extra fields. 3. I would really like to see mysite's greatly improved. In the large scheme of things personalized sites and dashboards are where real value is delivered. The current design of mysites and existing webparts/features are limited and difficult to work with/extend. Better enabling this will help more organizations reach Enterprise 2.0 level. Thank you, Richard Harbridge

Native Reporting

We need the wiki, blog and editor's to be feature competitivr and more flexible. http://tinyurl.com/lbfvv5

We need the wiki, blog and editor's to be feature competitive and more flexible. http://tinyurl.com/lbfvv5

The biggest development impediment has been no support for relational data, T-SQL, LINQ or some way to aggregate data. Lists should not be independent islands of data. We need tools to query lists like any other Win/Web app. 2010 appears to be addressing this glaring omission with external content types and LINQ integration.

The biggest development impediment has been no support for relational data, T-SQL, LINQ or some way to aggregate data. Lists should not be independent islands of data. We need tools to query lists like any other Win/Web app. 2010 appears to be addressing this glaring omission with external content types and LINQ integration.

Sharepoint Designer 2010 will not work on sites < Sharepoint 2009 . . . Bummer

Hi This is a nice site. Good information on Sharepoing I recently came this free Sharepoint Certification Preparation Guide From Exam Force Valid in US, Canada and Mexico only... http://afreelist-blogspot.tradepub.com/free/w_exam02/?p=w_exam02 Free Study Guides in this Offer: Microsoft 70-631 TS: Windows SharePoint Services 3.0 Configuration – 29 pages 70-640 TS: Windows Server 2008 Active Directory, Configuration – 78 pages 70-290 Managing and Maintaining a Server 2003 Environment – 45 pages

Make it compatible with other browsers than IE

The WYSIWYG editor for publishing sites needs an option for tables. The ability to do inline code behind in ASPX pages with SPD. Better CAML, XSLT writing tools, especially for the BDC.