Requirement:
We need to display documents from SharePoint Document Library into custom ASPX page and when user clicks on documents, it needs to open in “EDIT” mode, by default it’s giving user prompt to open documents in “EDIT” or “READ” only mode.
Solution:
We need to put extra JavaScript code which will open document in EDIT mode.
Reference Links:
http://ddkonline.blogspot.com/2007/07/issues-with-sharepoint-2007-checkout.html
http://www.google.com/search?q=dispex+sharepoint
http://mattknott.com/content/blog/2009/08/Stop_DispEx_Redirecting.html
http://dotnetninja.wordpress.com/2009/01/12/how-to-open-sharepoint-documents-in-edit-mode-with-internet-explorer-6-and-windows-xp-without-regfix/
Showing posts with label Document library. Show all posts
Showing posts with label Document library. Show all posts
Wednesday, December 16, 2009
How to open any documents in EDIT Mode from custom ASPX page
Labels:
custom ASPX page,
DispEx,
DispEx SharePoint,
Document library,
EDIT mode,
How to open any documents in EDIT Mode from custom ASPX page,
JavaScript code,
MOSS 2007,
Personal Experience,
SharePoint 2007,
SharePoint Document Library,
SharePoint List,
SharePoint Object Model
Wednesday, June 10, 2009
SharePoint web services – permission for GetWebCollection method
For one of my requirement I took the advantage of SharePoint web services, actually I needs to make a windows application which will get the information for all document libraries and list down all the documents inside each document library from SharePoint site.
So I have used WEBS and LISTS web service to get my required results, while working with WEBS web service, I used web method GetWebCollection() from WEBS web service to take all the web site name underneath one SharePoint web site, the windows application runs well for development sites but for production sites it’s giving me unauthorized access error while accessing GetWebCollection() method, because I don’t have sufficient rights into product site, I was thinking that for executing GetWebCollection() method, I need service account or extra full control rights, but after finding from the internet, I had conclude that I just need “contributor” rights into all sites and sub-sites while working with GetWebCollection() method.
User needs “browse directories” permission.
Reference Link:
http://www.novolocus.com/2008/07/03/browse-directories-and-webs-getwebcollection-strangeness/
From my point of view, we can do all things with SharePoint web services which we can achieve from SharePoint object model, just we need to know which web services and web method to call.
Happy coding !!
So I have used WEBS and LISTS web service to get my required results, while working with WEBS web service, I used web method GetWebCollection() from WEBS web service to take all the web site name underneath one SharePoint web site, the windows application runs well for development sites but for production sites it’s giving me unauthorized access error while accessing GetWebCollection() method, because I don’t have sufficient rights into product site, I was thinking that for executing GetWebCollection() method, I need service account or extra full control rights, but after finding from the internet, I had conclude that I just need “contributor” rights into all sites and sub-sites while working with GetWebCollection() method.
User needs “browse directories” permission.
Reference Link:
http://www.novolocus.com/2008/07/03/browse-directories-and-webs-getwebcollection-strangeness/
From my point of view, we can do all things with SharePoint web services which we can achieve from SharePoint object model, just we need to know which web services and web method to call.
Happy coding !!
Labels:
browse directories,
contributor,
Document library,
GetWebCollection,
Lists web service,
MOSS,
MOSS 2007,
permission for GetWebCollection() method,
Personal Experience,
SharePoint,
SharePoint Architecture,
SharePoint List,
SharePoint web services,
unauthorized access,
Webs web service,
windows application
Sizes and items limitation for SharePoint List objects
Below are recommended guidelines for creating total # of site collection, webs, document library and many more …
1. Recommended limitation for SharePoint site objects
http://technet.microsoft.com/en-us/library/cc287790.aspx
2. Limitation guidelines for SharePoint 2003 and SharePoint 2007
http://www.sperto.com.ar/fs_files/user_img/articulos/SharePoint%20Limits.pdf
Apart from this article discussion, here is very good link which will describes logical architecture of site collection.
http://www.sharepointblogs.com/llowevad/archive/2007/06/25/site-collection-logical-architecture.aspx
1. Recommended limitation for SharePoint site objects
http://technet.microsoft.com/en-us/library/cc287790.aspx
2. Limitation guidelines for SharePoint 2003 and SharePoint 2007
http://www.sperto.com.ar/fs_files/user_img/articulos/SharePoint%20Limits.pdf
Apart from this article discussion, here is very good link which will describes logical architecture of site collection.
http://www.sharepointblogs.com/llowevad/archive/2007/06/25/site-collection-logical-architecture.aspx
Labels:
Document library,
logical architecture of site collection,
MOSS,
SharePoint,
SharePoint Admin,
SharePoint Architecture,
SharePoint List,
SharePoint Object Model,
SharePoint site objects,
Sizes and items limitation for SharePoint List objects,
SPListItem,
total no of site collection
Tuesday, September 16, 2008
Hiding/Deleting Current Navigation(Left Navigation) from Document library
Below are some of the ways to hide/delete left side navigation from SharePoint Page.
1. Left side navigation bar has predefined placeholder into main master file, so if we open our master page into SharePoint designer and try to find navigation placeholder tag and removed that tag then left side navigation bar will not be displayed into any of site.
So removing place holder from master page will completely remove it for all child pages.
2. If we want to hide in some of the pages then we can override style and achieve result.
I. we have to Edit page in designer and unlock region and remove left navigation frame OR
II. We can put left navigation bar in child page and put nothing inside that tag OR
II. We can put
<style>
.ms-navframe{ display:none; }
</style> on page.
With any of the above steps, left side navigation bar will be removed/hide from pages or document library.
1. Left side navigation bar has predefined placeholder into main master file, so if we open our master page into SharePoint designer and try to find navigation placeholder tag and removed that tag then left side navigation bar will not be displayed into any of site.
So removing place holder from master page will completely remove it for all child pages.
2. If we want to hide in some of the pages then we can override style and achieve result.
I. we have to Edit page in designer and unlock region and remove left navigation frame OR
II. We can put left navigation bar in child page and put nothing inside that tag OR
II. We can put
<style>
.ms-navframe{ display:none; }
</style> on page.
With any of the above steps, left side navigation bar will be removed/hide from pages or document library.
Subscribe to:
Posts (Atom)