.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Removing "Add Document" for all the document Libraries in the ListViewWebpart ?

Posted By:      Posted Date: October 14, 2010    Points: 0   Category :SharePoint



can anybody guide me how to Hide/Remove "Add Documnt" option of List View webpart as am having my custom upload functionality as per req.

Thanks in Advance !!! Cheers !!! Praveen Mandalapu

View Complete Post

More Related Resource Links

Working with SharePoint document libraries

Document libraries are collections of files that you can share with team members on a Web based on Microsoft Windows SharePoint Services. For example, you can create a library of common documents for a project, and team members can use their Web browsers to find the files, read them, and make comments. Users with Microsoft Office 2003 can check out and edit the files as if they resided on a local or network drive.

By default, your team Web site comes with a built-in document library named Shared Documents, which is listed on the Quick Launch bar as well as on the Documents and Lists page.

Large document libraries with a custom user interface


We recently migrated our document management system to SharePoint (WSS 3.0) and I adapted my VB6 client application to search for and retrieve a list of documents from this new SharePoint library using the Lists web service. Although the total number of documents in this library is 90,000 at one site and over 145,000 at another, my VB6 application never retrieves more than 600-700 documents at a time. From reading white papers such as "Working with Large Lists in Office SharePoint Server 2007" (http://go.microsoft.com/fwlink/?LinkId=95450&clcid=0x409), it appears that if my custom user interface limits the number of items returned in a search of these large lists, that it may not be necessary to put these documents into folders. However, our current scanning software, KnowledgeLake Capture, by default places newly scanned documents into folders based on the year, month, day and hour, which means that these documents are placed in nested folders 4 levels deep.

There are also some 20 metadata fields on these document libraries that allow us to filter these document libraries so that search results will in most cases be limited to a few hundred items.

We acquired new servers (Windows Server 2008 with SQL Server 2008) to host our SharePoint libraries and we are running WSS 3.0 S

Video: SharePoint 2010 Document Libraries

This demonstration delves into working with document libraries and documents programmatically. (Length: 5:39)

SharePoint Document Libraries and Horrors Oh My

I thought I would capture a few ideas around document libraries and share with the rest of the class. These are not "best practices" as I don't want to sound too preachy so let's call them "pretty good practices that you might want to consider if you have some time" (which is far too long for a blog title, hence the one I came up with is going to have to do). SharePoint Fight Club The first rule of SharePoint. I want you to repeat after me. "SharePoint Document Libraries are not file shares." Good. Now say it again. Good. Remember this, above all other things we're going to talk about here, and you'll be golden. Document Libraries are not File Shares I have to repeat this here because it is key. If your users are asking you to put a file share into SharePoint then you need to beat them upside the head when they talk about "replicating the folder structure" or "like for like" or "make it just like *that* (and points to file share)". If you really must make some kind of analogy and your audience knows something about databases (even Access), rather than saying document libraries are like file shares say "document libraries are like databases". While SharePoint sits on top of a database it's kind of irrelevant what the backing store is (side note, Dear Microsoft, please make a pluggable store for SharePoint in the next version) a list or document library is pretty

Seperate out the Document Libraries to individual Sites in MOSS 2007

We are using the MOSS 2007 with SP2. We are having three different Document Libraries for three different projects under same site. We have the requirement to migrate each library to shift to the individual sites. We need to do this with all the content, settings and and the permissions. It's fine to migrate the database and settings individually i.e. content database seperately and site settings seperately. Is anyone have this kind of migration?

custom columns in document libraries

Hi I created two custom columns "Fromdate, Todate" in document librarie, and assigned a document to other user. when other user logIn, in the tasks list, select the item and click on "Edit item" edit form is opened, but i could not found Columns "Fromdate, Todate", where did I went wrong! I created custom workflow in VS2005(no forms are used)

Incoming Mail enabled MOSS 2007 document libraries.

I would like to ask is there a way to get the incoming emails to go into a subfolder because right now the email goes into the root of the document library?

Event handler to delete minor versions in document libraries

Hi Is there a way we can capture the deletion of minor versions in document libraries using any event handler. May not be using the delete all the minor versions but at least when we use the option to delete the selected minor version. I do not see the ItemUpdating and ItemUpdated getting fired in this case. Thanks wpwije  

Problems with Custom List Forms in Document Libraries

I have setup several custom list forms for various lists with no issues however when it comes to document libraries a few things dont seem to work correctly. I create a copy of the editform.aspx --> Hide existing web part --> Insert custom list form (edit) --> restyle the fields etc. save it as edit.aspx confirm it is being used as the default form in the supporting files section. Great it appears to work whenever someone uploads a document or clicks edit. However... that is only th first impressions as there are a few issues that crop up at this time.  Clicking the edit button on an existing document doesn't display the Name field, meaning individuals cannot rename a document. After an item is uploaded and the required fields are entered in the form the user then clicks check-in. The library then opens and shows the document is still checked out to that user. Has anyone else experienced these issues before? The critical factor is the checking in a document, as to why this breaks on a custom edit form I have no idea. Any help would be greatly appreciated as under quite a lot of pressure to get this resolved. Chris

Version number syncronisation between document libraries

When I perform a Move or Copy operation from one Document Library to another in SP 2010 (using Send To or Manage Copies feature) SP resets the version number to 0.1 even if the version number in the source library is 4.2 (for example). All other Metadata is copied correctly. Is their anyway to keep version numbers in sync between document libraries? Seems like quite an obvious requirement to me but could not see any other info on the net about this.. thanks in advance

SharePoint Users Behind a Forefront TMG Server Cannot Access Explorer View in Document Libraries

SharePoint server via a Forefront TMG server in a separate sub-domain. These users cannot access Explorer View in Document Libraries nor can they map a drive to the SharePoint directory structure, as users who are in the same sub-domain as the SharePoint server can. How do I setup SharePoint and the TMG server so that these users can map a drive to the SharePoint site? Office SharePoint 2007 SP2 Windows 2008 Server SP2

removing new document and new folder from toolbar

hi, is there a way to remove new document and new folder from toolbar using jquery or javascript

Display an index of all document libraries

Hi, Is there a way to display an index of all document libraries that exist within a site? Initially I thought the Table of Contents web part could do the trick, but this only works if I add my document libraries to the site's navigation (which I don't want to do).  

Using a List View web part to display documents from multiple document libraries from different site

Hi there, I am trying to have one web part display documents (or list items) from different document libraries (or different lists) from different site collections. I have achieved this under a single site collection using Data View Web Part (using SPD). I have also achieved displaying a single document library (or a list) from a different site collection by using List View Web Part. but I am not sure how to get my head around displaying documents or list items from different document libraries or lists across site collections. I have thought of using SPSiteDataQuery or ListViewByQuery, but they all seem to focus one site collection at a time. If any of you have done this before, please share your best practice on this one with me. Much appreciated. Clark

Users (even site collection administrator) unable to see minor versions in document libraries


I have document libraries with the following settings: major & minor versioning enabled, checkout required & 'only users who can edit items' can see draft (minor) items. The problem is when a user uploads a document (the first document), the library appears empty. However, looking at the summary in 'view all site content' we see that the number of items in the list has incremented by 1. Typically, if the user selects explorer view they can also see the document they just uploaded.

Similar behaviour occurs using the 'New document' option. Before checking in the document for this first time it is visible in the library. If it is checked in as v 0.1 it 'disappears' if it is checked in as v 1.0 it is visible.

I have noticed that if I toggle the Draft Item Security setting by setting it to 'any user who can read items' then set it back immediately to 'only users who can edit items' that the previously hidden items become visible. And any new minor versions created subsequently are also displayed correctly. I can of course do this for existing libraries, but if new libraries are created based on my template this behaviour reoccurs.

Has anyone seen this before?

SharePoint Feature / Solution - Unassociate/Associate existing document libraries to a DLL



Previously we have a document library feature that contains a DLL.

Over time we have created document libraries using this feature, so document libraries created were associated to the DLL.

Now we need to change the solution to NOT include the DLL, but we found out that even though we retract / redeployed the solution without the DLL, those document libraries that were created is still calling/associated with the DLL.

Is there a way to unassociate/associate back the document library to the DLL?

Thank you for any help! :)




combine Document libraries 2010 that is in Draft mode into a dashboard


I have a question on Sharepoint Enteprise 2010

I have couple of document libraries in one site that needs to rollup to a dashboard where the content should be displayed in an combined view ,showing draft versions only, perhaps in a summary total of ones in Draft.

Basically the best solution will be if I can get a summary list of some sort with the link back to docuemnt library where the draft documents reside.
The user will then edit the draft document and Approve the document that will remove it from the view.
With such a dashboard the user will always quickly see how many documents are left in Draft per library

Something similar to what you see at {site}/_layouts/viewlsts.aspx?BaseType=1 on the site would be really cool for the client.

Or even the content Query grouped by Content Type but when clicking on the item its should go the view Properties or something, even though Sharepoint2010 pops up with View Properties and not same as 2007, possible?

My documents libraries have a content type that all inherit from the same Parent Content type, so already quite well structured. Each Document library runs a custom workflow on them that prevents me from moving them all into one Document Library.

Any suggestions, with little custom development out there? with link perhaps?

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend