Abhishek Bhowmick | SharePoint Blog

Difference between SharePoint “View only” and “Read” permission level

Posted in Sharepoint by Abhishek Bhowmick on May 4, 2011

View Permission – Users with Read only permissions can view the content using Client side application like Excel or InfoPath. It allows users to open a Web site, list, or folder in order to access items inside that container. View items in lists, documents in document libraries, and view Web discussion comments.

Read Permission – Users with View only permissions cannot view the content using Client side application like Excel or InfoPath. Like they can view only Server side rendering items.It allows Users to View items in lists, documents in document libraries, and view Web discussion comments. Open Items and View the source of documents with server-side file handlers.

More information: http://office.microsoft.com/en-us/sharepointserver/HA101001491033.aspx

Advertisements
Tagged with: ,

Users with lower permission level are unable to view Site Directory links

Posted in Sharepoint by Abhishek Bhowmick on January 23, 2009

Here is a simple issue which took us some time to get hold of.  Heartiest thanks to Vijay Kumar Acharya who gave us this lead.  This is how it goes…  Site Collection Administrator creates a link in the Site Directory and can view the same after logging back to the site.  Users with lower permission level are unable to view this link in the Site Directory.  We logged back into the SharePoint site and navigated to the Site Directory.  Clicked on View All Site Content.  Under Lists we clicked on Sites.  We found in the List settings > Versioning Settings we found that Content Approval was enabled hence any new links being created in the Site Directory has an Approval Status as Pending.  We approved the list item for the concerned link and the other users with any permission level were able to view links in the Site Directory.  If the Site Collection Administrator does not wish to continue this operation then the Content Approval can be disabled and the links should appear to other users just like that.  Hope this helps!

Moving items from one list to another in SharePoint

Posted in Sharepoint by Abhishek Bhowmick on January 23, 2009

We come across this almost in every issue that we work with pertaining to Lists in SharePoint.  Have you ever been in a situation where you needed to move just one List item to another list and not all of them.  So here is the way we can do it.  Open your SharePoint site and make sure you’re logged in atleast as a Site Collection Administrator (not that you cannot do this operation with other permissions.)  Before we proceed also make sure that publishing is enabled for the Site Collection Features and Site Features.  Navigate yourself to the Site Settings and then to Manage Content and Structure.  Select the List where you have the list item and then hover over the list item you want to move.  Drop down the menu and select Copy/Move.  It should open a dialogue box displaying a the site tree structure again.  Select the List you would like to the copy/move the item to and the operation would be executed.  Voila! Open the destination List and you would see your List item listed there.

Sharepoint Webpart Differences: .dwp and .webpart

Posted in Sharepoint by Abhishek Bhowmick on January 21, 2009

I am sure most of us have come across this situation when users try to add webparts to their SharePoint site and have difficulties with that.  Ever wondered how .dwp and .webpart are different to each other?  Well then here is the answer to this question which is a good one to start with to understand.

The .dwp is a SharePoint web part. This would be one like the Content Editor.  And the .webpart is a .NET framework.

The primary differances are that the SharePoint webparts are built with backwards compatibility and more functionality in the web parts communitcation area. If you needed a web part that worked in WSS 2.0 and WSS 3.0, this would be your guy.

The later is one that most likely originated in Visual Studio.

Source:  http://www.shannonbray.com/2008/07/dwp-vs-webpart.html

Tagged with: , , ,

Restrict Views for User Groups for Lists and Libraries in Sharepoint

Posted in Sharepoint by Abhishek Bhowmick on December 18, 2008

Restricting views for users in Sharepoint could not have been easier.  Searching through the internet got me to this website where I found this handy tool:  http://www.codeplex.com/SPViewPermission.  Installing this tool will make a feature available in the site collection feature called “View Permission Settings (powered by Bewise)”. Activating feature will add one item “View Permission Settings (powered by Bewise)” in the list or library settings where you can control which user group should view certain views.  Please visit the above link for screenshots and procedure.

Alternative:  Creating personal views and making them their default view by individual users will show them their own views but that will not restrict them from viewing other views as well.

Search does not work with Anonymous Access

Posted in Sharepoint by Abhishek Bhowmick on October 2, 2008

CAUSE:
This is a default behavior seen in SharePoint that anonymous users do not get search results.  Security trimming prevents anonymous users from seeing items in search by default.

RESOLUTION:
Enable “Always index all ASPX pages on this site” on the site collection.

Perform the following steps:
• Open the SharePoint Site
• Click on Site Actions, Site Settings and Modify Site Settings
• Click on Search Visibility
• Select the option that says “Always index all ASPX pages on this site”
• Perform a full crawl again
• Log into the site anonymously and perform search and you should get search results now

Tagged with: , , ,

Run stsadm.exe command from any command prompt

Posted in Sharepoint by Abhishek Bhowmick on September 26, 2008

Many a times people think of running stsadm.exe commands from any command prompt.  So here is the way:

•  Open command prompt
•  Type in the following command:  @set PATH=C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN;%PATH% 
•  You can now run the stsadm.exe commands from anywhere in the command prompt

%d bloggers like this: