Skip Ribbon Commands
Skip to main content

Chris Caravajal

:

Other Blogs
There are no items in this list.
Home
Welcome to your Blog!

To begin using your site, click Create a Post under Blog Tools.

What is a Blog?

A Blog is a Web site designed to help you share information related to a particular subject area in the form of text, images, links, and other media such as video. Blogs can be used as team sites, news sites, journals, diaries, and more.

Blog posts usually consist of frequent short postings and are typically displayed in reverse chronological order (newest entries first). Blogs encourage site visitors to interact with one another by leaving comments on posts.

Blogs can be also be used as a team communication tool. Keep team members informed by providing a central place for links and relevant news.

SharePoint 2010:  Delete Users From Site Collection

When managing user access to site collections, it can sometimes be necessary to remove a user from an entire site collection. In SharePoint 2007 sites, there was a nice action button via the All People page. This page could be accessed by going to Site Actions > Site Settings > Advanced Permissions > All People (Quick Launch link). Unfortunately this option is not available to us in SharePoint 2010 sites, but this does not mean that this functionality is not available. Instead, it is just a hidden feature that we must manually get to:

 

  1. Log in as a Site Collection Administrator
  2. Click on Site Actions > Site Permissions
  3. Click on one of the SharePoint Security Groups displayed on the permissions page
  4. When your browser has been redirected to that group's page, look at the URL in the address bar of your browser. It should look something like

     

    http://[SiteURL]/_layouts/people.aspx?MembershipGroupId=[SomeNumber]

     

    In my testing environment, the URL is

     

    http://server/sites/Contoso/_layouts/people.aspx?MembershipGroupId=5

     

  5. Change the last character of the URL, the number, to the number zero, "0." Hit enter. …_layouts/people.aspx?MembershipGroupId=0 is the group for All People.
  6. From here you can select a user, click on the Actions dropdown, and click on the Delete Users from Site Collection button.

 

Item Limit on lists and libraries.
Have a list that has hundreds of items?  And you can't view them all at once?  Instead you have to click on another page? Well, the Item Limit settings on the List/Library you are viewing are the cause.  By default, SharePoint sets the Item Limit at 100 items.  Usually this is not a problem for most large lists/libraries when you use filters and custom views to narrow the displayed items.  However, there are occasions when it is necessay to view all the items at once, so you have to change this setting.  There are two ways of accomplishing this:  using the browser and using SharePoint Designer (SPD).
 
Using the Browser:
1)  Navigate to the list/library.
2)  Click on the View dropdown menu and select the view you would like to edit.
3)  Click on the View dropdown again and select Modify this View.
4)  Scroll down to the Item Limit section and expand.  Here you can change the value.  Click OK.
 
 
Using SPD:
1)  Open up SPD from your Start menu>Programs>Microsoft Office.
2)  Click on File>Open Site and enter the site URL where the list/library is kept.
3)  Expand the list/library.
4)  Expand the Forms folder.
5)  Here you should see the .ASPX files for all your views along with some other files.  Locate the [View].aspx file for the view you want to edit and double click to open it.
6)  The master page for the view will open.  You should see the list view within SPD.  Have the SPD view set to Design (you should see three options on the bottom of the page:  Design, Split, and Code).
7)  Locate the PlaceHolderMain area and click on the List View Options dropdown menu.
8)  Click on Change Layout...
9)  Click on the Paging tab,, select Display items in sets of this size, and enter the value of your chosing.  Click OK.
10)  Click the Save icon or File>Save
 
That's it.
Accessing your SharePoint site from a smartphone or PDA.
It is actually easier than you would think.  When trying to use your mobile device to access a SharePoint site, make sure that you do or have done the following:
 
1)  First and foremost, you have to enable the Mobile Web View.  See the following blog:  http://www.akgroup.com/news/blog/200801/enabling-the-mobile-web-view-on-moss-collaboration-site
 
2)  Next, you have to be using a mobile device that is running Windows Mobile 6.0 or better.
 
3)  When typing the URL for the site, add /m.  So if the URL for your site is http://litwareinc.com you would type http://litwareinc.com/m
 
Also keep in mind that you can create mobile views for your lists in libraries in SharePoint.  Simply navigate to the list/library, click on the View dropdown menu and modify or create a view.  When you are on the Settings page, scroll down to the Mobile section and expand.
Mapping InfoPath Fields to SharePoint Columns
I was recently working on a project implementing an InfoPath form template with a SharePoint forms library when I ran into a troublesome problem:  The InfoPath form wasn't publishing to Sharepoint properly.  During the final step of publishing the form I would receive the error that InfoPath could not "Update the content type."  At first I thought it may have something to do with the several data connections that we were using or possibly the multiple "Contact Selector" controls.  In the end, the problem was the number of InfoPath fields that we were trying to map as columns in SharePoint.  When you publish an InfoPath form to SharePoint, there is a step where you can take an InfoPath field and have SharePoint create a column for that field.  Unbeknownst to me at the time, but it makes sense now, is that there is a finite number of InfoPath fields that can be mapped as columns in SharePoint.  The literature I found put this number at approximately 90 fields.  However, as I tested my form and it's 120 fields, 5 data connections, and 20 Contact Selector controls, I found that this ceiling value is dynamic, dependent on the number of data connections and amount of conditional formatting that is associated with your InfoPath form.  So just a friendly heads-up to anyone creating InfoPath forms for SharePoint, if you are getting the same error, check the number of InfoPath fields you are mapping to SharePoint as columns.