Well, this is my first blog on blogspot and this I am sure would help someone address their problems of hiding views.
We have a system for logging issues and our req is to be able to hide the view control to normal users and show it only to a specified set of administrators. After googling, Binging and what not, we ran across this simple solution out of the box.
We created two groups in SharePoint and added the respective users to the groups. Next we added the same forms library web part in the allitems.aspx page and used audience targetting on both web parts with audience targetting set to two different groups. So when a user added to one group logs in, he sees the web part intended for him.
The advantage in doing this was that we got rid of the view dropdown in the second web part we added to the page and targetted that web part to the users.So, the original web part within the forms library has the views dropdown while the other web part that was added by us does not have the views dropdown.
Wednesday, February 24, 2010
Tuesday, February 23, 2010
SOAP errors in SharePoint Designer
Blogging about this for the first time but its been such a pain in the b*** for some time now.
We have been playing around with the default.aspx page quite frequently in our dev environment making changes directly to the page ( not the way Microsoft recommends)and every time that we edit the page, we get an ugly soap error stating to contact the web administrator or something like that.
After hitting our heads against the wall for about 3 days, the easiest solution to this that we found was to close web parts on the aspx page using the web parts maintainence page( just append ?contents=1 after default.asxp to get to the web parts maintainence page eg mypage/default.aspx?contents=1).
This works and the page opens up like a charm.
We have been playing around with the default.aspx page quite frequently in our dev environment making changes directly to the page ( not the way Microsoft recommends)and every time that we edit the page, we get an ugly soap error stating to contact the web administrator or something like that.
After hitting our heads against the wall for about 3 days, the easiest solution to this that we found was to close web parts on the aspx page using the web parts maintainence page( just append ?contents=1 after default.asxp to get to the web parts maintainence page eg mypage/default.aspx?contents=1).
This works and the page opens up like a charm.
Subscribe to:
Posts (Atom)