Skip Ribbon Commands
Skip to main content

Laura Rogers @WonderLaura

:

Top Link Bar

Microsoft MVP
 
Home
SharePoint for Non-Developers
 

 Posts

 
May 16
Creating a Workflow Initiation Form for Approvals
by  lauraNo presence information  on 5/16/2012 1:47 PM

In SharePoint Designer workflows that are manually started, the initiation form is the page that has the “Start” button to kick off the workflow.  In this 11 minute video, I show how to create an approval workflow that can be manually triggered. 

I walk you through:

  • Setting up the workflow so that after the approval process, the content approval status of the document automatically gets updated.
  • Customizing the initiation form in InfoPath, so that the needed approvers may be selected from a people picker, and the colors are modified.
  • Adding a “high priority” check box so that high priority item approvals are due in a more timely fashion than normal.

This solution applies to only the enterprise version of SharePoint and SharePoint online.  This does not include SharePoint Foundation because it uses browser-based forms, which are enterprise only.

How can you learn more?  This solution is actually an excerpt from chapter 10 of our book.

CropperCapture[27]

Click to buy the book:

InfoPath Boook

Already own the book? Open it to Chapter 10, and follow the step by step instructions that start on page 256.

 

Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
May 15
InfoPath: Create Common Multiple Choice Selections
by  lauraNo presence information  on 5/15/2012 6:53 PM

In InfoPath, when using certain controls such as the Drop-Down List Box, Combo Box, List Box, or Multiple Selection List box, there are several different ways that you can obtain the list of choices that are available to people filling out the form.

  • Enter choices manually – This option allows you to simply click the Add… button below and type in the values for each choice, and use the Move Up and Move Down buttons to rearrange the order.
  • Get choices from an external data source – This option allows you to select an existing data connection, such as one that receives a SharePoint list. This way, the selections can be dynamic. This is the best option to use when the values in the list change frequently. It allows you to simply change the source location, such as the items in a SharePoint list, instead of having to re-type the options in and re-publish the form.

 

 

 

This blog post is all about that other option, called Get choices from fields in this form.

This middle option is pretty useful in a couple of situations:

  1. You have a list of fairly static choices, but you need to use them in several places in your form. A good example is a survey. Commonly, there need to be many drop-down boxes in a survey, but they have all the same choices, such as Yes, No, Maybe.
  2. A different situation, which I don't come across often, is when there is a repeating table or section somewhere in the form, and the values that have been filled in there, need to be the values to select from in your drop-down box.

 

This blog post is about option 1 above. A survey with the same set of answers being needed multiple times in the form.

Here's how to create some choices "Yes, No, or Maybe", using that middle option in your drop-down box, and use it in many places in the same form:

  1. In InfoPath Designer, in the Fields pane on the right, right click the MyFields folder (root folder) and click Add…
  2. Name it SurveyChoiceGroup, select Group as the type, and click OK.

  3. Right-click on SurveyChoiceGroup, and click Add… Name it SurveyChoice, and click OK.
  4. Name it SurveyChoice, check the box next to Repeating, and click OK.

  5. Your new structure in the Fields pane on the right should look like this:

  6. On the Data tab, click the Default Values button.

  7. Click the drop-down on the SurveyChoice field, and select Add another SurveyChoice below.

  8. Do this one more time, so that there are three different Survey choices under the SurveyChoiceGroup.
  9. Click to select the first of the three SurveyChoice fields. In the Default value field, type Yes

  10. Click to select the second SurveyChoice, type a default value of No, and then for the third, type a default value of Maybe. Click OK.
  11. Put a drop-down box on your form, and open its properties screen.
  12. Select Get choices from fields in this form, and choose SurveyChoice. Click OK, click OK.

Now, when you publish or preview your form, you can see that when you click the drop-down, it shows the 3 choices of Yes, No, or Maybe. You can create multiple drop-downs or any type of selection boxes, and use that same list of survey choices in all of them. Then, if the list of choices need to be edited, you can just do it in one place. Of course, this can always be done by creating a data connection to a SharePoint list, but for such a simple set of choices, all of that may not be necessary. This is just another option.

 

Permanent Link to Post | Email Post Link | Number of Comments 0 Comment(s)
May 07
International SharePoint Conference – Wrap Up
by  lauraNo presence information  on 5/7/2012 10:52 PM

Last month was the International SharePoint Conference in London. I was honored to be invited to be a speaker at the conference. The format of the conference was great. Not only were there different tracks, but within each track, there were continuous solutions being built from one session to the next. I absolutely loved this, because an hour to cover a topic never seems like enough. Here's what we did as one of the solutions in the information worker track: Jennifer Mason, Darvish Shadravan, Matt Hughes and I did 4 sessions throughout the day, all around building a travel request site in SharePoint.

  1. Jennifer and I taught the basics of how to build the travel request form using InfoPath.
  2. Matt and I taught how to create a workflow which includes an approval process for each travel request.
  3. Jennifer and Matt taught how to build a nice user interface by placing web parts on pages and creating needed list views.
  4. Darvish and I taught all of the ways we can report off of this travel request site data, using KPIs, Excel Services, PerformancePoint, and SSRS.

How did we do it? How did we collaborate on the creation of this solution? Funny story behind that…

At first, we just figured we'd use Office 365, but then some of the business intelligence solutions in the 4th session can't be done in Office 365. We figured we'd just copy the site and do that last part on someone's virtual machine on their computer. Easier said than done. After we had created the solution in Office 365, we discovered that you can't simply save a SharePoint Online site as a template and then put it in an on-premise version of SharePoint. Good to know! This doesn't work because SharePoint online has a feature that SharePoint on-premise doesn't have, so you get errors when trying to add a site using the site template. Yes, there are some hacks we found online to accomplish this, but it turned out to be faster to just re-create the site from scratch and just publish another copy of the InfoPath form to it.

Darvish and I still needed to be able to collaborate on an on-premise SharePoint site, to build our reporting solutions. Rackspace to the rescue! With a couple of days left to go before leaving for London, my amazing colleagues whipped up a cloud SharePoint server for us! It was absolutely terrific, like "Okay, here's your whole SharePoint server, all built and configured, ready to go!". PerformancePoint was working correctly, SSRS was installed, and everything, so all that Darvish and I needed to do was to start building out our reports off of the travel data. Thanks to Jeff Deverter, Javier Barrera, Todd Klindt, and the rest of the SharePoint admin team!!

Here is an example of one of the charts that I created off of the SharePoint task list, using SQL Server Reporting Services (SSRS):

Below is one of the scorecards that Darvish created using PerformancePoint:

As you can tell from my enthusiasm, the last session was my favorite. We had a blast, and it went really well!

All in all, it was a fabulous few days in London. Steve Smith and the crew at Combined Knowledge sure put on quite a conference! Here's the group of speakers at the wrap-up on the last day:

We arrived in London a couple of days before the conference started, so we had some time to go sightseeing. Here is a picture of me, riding the London Eye:

Permanent Link to Post | Email Post Link | Number of Comments 2 Comment(s)
May 02
SharePoint Designer - Restore Previous Workflow Version
by  lauraNo presence information  on 5/2/2012 10:04 PM

Have you ever published changes in a workflow in SharePoint Designer and wish you hadn't? There is a little known way to go in and restore a previous version of your workflow. This uses the same versioning capability that lists and libraries have. By default, every time you publish changes to a workflow, they are saved as a new version.

This solution applies to all versions of SharePoint 2010, 2007, and SharePoint Online with Office 365.

Here's how to revert to a previous version:

  1. In the left pane of SharePoint Designer, click the little pin icon next to All Files.

  2. Once All Files is expanded, scroll down and expand out your folder called Workflows. Note that if you have not actually created any workflows yet, you will not have this folder. Each workflow will be a "subfolder" under workflows. One weird little thing to point out also is that if you changed the name of any workflow after you created it, that new name will not show here, only the original name of each workflow will show in this list.

  3. The workflow that I want to restore a previous version of is called "Check Audit Month", so I'll expand out that folder. Now I can see all of the files that my workflow is comprised of.

  4. Each of these files has a set of versions. Right click on the XOML file, and choose Version History. I want to get rid of all the changes I made today, and revert back to the 4/12 version which I know worked correctly. I scroll down and click on the most recent 4/12 version. (I've blurred out the domain name I'm working in)

  5. Click Restore.
  6. Right click on the next file, the XOML.rules. Go find that exact same date/time of the file as the one in the previous step, and restore it. Note that the version number may NOT be the same.
  7. Right click the next file, which is xoml.wfconfig.xml. Do the same thing by finding that same date/time that matches the one you restored at step 4. Restore it.
  8. In this case, I don't need to change anything about my InfoPath XSN file, which is the task form as part of tasks that are assigned in the workflow. I'm skipping that one.
  9. Important step after you've restored the old versions… EXIT SharePoint Designer. This is because of a cached version of your workflow needing to be refreshed.
  10. Re-open your site in SharePoint Designer. When you open your workflow in the normal way now (as opposed to the funky way we did in step 2), you will see that good old version that you just restored.
  11. Click Publish. Now your restored workflow is live and in use on the site.
Permanent Link to Post | Email Post Link | Number of Comments 6 Comment(s)
April 11
User Information within InfoPath Forms
by  lauraNo presence information  on 4/11/2012 11:18 PM

There is a quick and easy way that information about the logged in user can be obtained from within an InfoPath form. You may have read my blog and other blogs before, with the user profile service web service instructions. In this post, I'm not going to be using the user profile service. This means that what I'm about to show you can be utilized with any version of SharePoint, whether you have a user profile service (enterprise) or not. This can be done with SharePoint 2010 Foundation, SharePoint 2010 enterprise and standard, and also WSS 3.0 and MOSS.

The User Information List is a list that exists at the site collection level, and contains a list of every user who has actually visited the SharePoint site. If they are a new user, they will not show in this list until they've actually visited a site in that site collection.

With that said, here are some instructions for getting some information about users, more specifically, the currently logged in user.

  1. Open up your InfoPath form, click on the Data tab, and click the Data Connections button.
  2. Click the Add… button.
  3. Choose Receive Data, and click Next.
  4. Choose SharePoint List or Library, and click Next.

  5. Paste the URL of your SharePoint site, click Next. (No need for any "default.aspx" at the end, or any other .aspx)
  6. Scroll down towards the bottom of the list of lists and libraries, and select User Information List. Click Next.
    (note that even though the user information list physically exists at the site collection level, you will still see this list on every sub-site also)

  7. Put check boxes next to the following fields, especially User_name. Click Next.

  8. Do not check the box to store a copy of the data. Click Next.
  9. This is very important. UNCHECK the box to automatically retrieve the data. Click Finish.

  10. On the Data Connections screen, click Close.
  11. Still on the Data tab in InfoPath, click the Form Load button, which will bring up the rules pane on the right side of the screen.
  12. Click the New button to create a new Action rule.
  13. Click the Add button and choose Set a Field's Value. On the Rule Details screen, click the button next to Field.
  14. In the Fields drop-down box, choose User Information List, expand the queryFields, and select User name.
    (be sure that you're selecting from the query fields, not the data fields.) Click OK.

  15. Back on the Rule Details screen, click the function (fx) button next to the Value box.
  16. Click the Insert Function button, and choose the userName function. Click OK two times.

  17. This is what your rule looks like. Click OK.

  18. Back over in the rules pane on the right, click the Add button, and choose Query for Data.
  19. Choose the User Information List and click OK.

  20. Now, each time the form is opened, the current user's information will automatically be queried, and that one record will be retrieved. There are many ways that this information can be used within your form. The data exists in the data fields of the user information list. In the Fields pane on the right side of the screen, choose the User Information List from the drop-down box.
  21. Select the folder directly under dataFields, the one with the blue icon called d:SharePointListItem_RW. Drag it onto an empty area of your form, and when you let go, choose Repeating Section with Controls.
    I'm really just having you put all this on the form so that you can see exactly what's being returned.

  22. Go ahead and publish the form, and open a new form. You'll see all of the data about you will be displayed, something like this:

  23. One more little trick. Go back to InfoPath Designer. Delete the "Picture" field. Add a Picture control to the form (not a picture button, just a picture), and choose As a link. Click OK.
  24. You will be prompted to bind to a field. Select the Picture field under the User Information List data fields. Click OK.

  25. Filling out the form again, now there's me:

     

    You can see how this data could potentially be used in many ways in your form. You can set some field defaults the first time the form is filled out, you could display the currently logged in user's picture… You can even use formatting rules to show, hide, or disable certain fields depending on who the current user is or what department they're in. I don't usually drop the fields on the form like I showed you, that was for demonstration purposes. I usually just refer to that data via rules, etc. Keep in mind that the user information list does not have the 60 or so fields that the user profile service contains, but it is very useful nonetheless. There are many other blog posts out there that show how to tap into the user profile service using the web service in InfoPath, it's just that if all you need is one of these basic fields, you might not need to deal with all of the complexity that it entails.

    Here are some other posts by me and others regarding user information in InfoPath:

 

Permanent Link to Post | Email Post Link | Number of Comments 9 Comment(s)
March 21
The International SharePoint Conference Next Month
by  lauraNo presence information  on 3/21/2012 10:32 PM
Category: conference

Only one more month until the big International SharePoint Conference in London!  This is going to be a great one, with a format that I’m very excited about.  The conference is organized into tracks.  These are not just tracks like “IT Pro” and “Developer”.  There are actual cohesive sessions within each track, that go together in succession. 

 

The track I’m going to be in is the “Information Worker” track, and the solution we’re building is called “Solution 1 – Building the Travel Request Solution”.  This track starts on Monday morning at 9:45 with session header of IW401. Our 4 sessions are then continuous one after the other until 3:45.  My cohorts in this travel request solution are Jennifer Mason, Darvish Shadravan, and Matthew Hughes.  This is going to be so cool, because we won’t be constrained to tell a whole story in a single one hour session.  We will use the four sessions to build one continuous solution!

The Travel Request Solution:

Jennifer and Laura: Part 1: Requirements and Design

In this session, we will start at the beginning of the travel solution, with the requirements gathering.  Then, we will start creating the form in InfoPath, with a lot of introduction to InfoPath and best practices in creating a form.

Laura and Matt: Part 2: Travel Request Workflow and Approvals

In part 2, Matt and I will take you through the approval workflow involved in this travel request.  We will talk through every step of the workflow, and talk about our own tips and tricks.  We will even delve into the task process designer.

Matt and Jennifer: Part 3: Planning and building the user interface

One of the most important aspects of building a solution for users is spending time in the design of the solution to ensure it is clear and easy for users to understand and work with. When building out of the box solutions there are many tools that can help in this process. In this session we will discuss list view web parts, DVWPs, InfoPath Form web parts and how they can be used to build a dynamic user experience for your solution users.

Laura and Darvish: Part 4: Reporting and Business Intelligence on travel requests

Darvish and I will delve into the reporting aspects in this session.  Once the travel requests have been submitted into this system, there needs to be reporting.  We will talk about the different ways that reporting can be accomplished, and will build out a dashboard for this system.

 

Technorati Tags: ,,
Permanent Link to Post | Email Post Link | Number of Comments 2 Comment(s)
March 19
SharePoint Saturday New Orleans This Week!
by  lauraNo presence information  on 3/19/2012 9:53 AM
Category: conference

Can’t wait!  SharePoint Saturday comes to my home town again!!  This Saturday, March 24th, is the third annual SharePoint Saturday in New Orleans.  I grew up down there, mostly in a small town on the west bank of New Orleans, called Luling.  Then, when I was about 13, my family moved to Baton Rouge, which is where my parents still live.  New Orleans is my favorite city, and I love sharing it with my SharePoint friends, especially those who have never been there.  There is a GREAT lineup of speakers for the event!

My session will be:

Advanced InfoPath: Working with User Profiles & the People Picker

When using the people picker control in an InfoPath form hosted in a SharePoint 2010 site, there are several advanced methods that can be implemented in order to use profile information to pre-populate fields. When your company’s user profile information is accurate, you can do some amazing things with that data. In this fast-paced session, Laura Rogers will go over several demonstrations of common scenarios in which information about people can be used in forms. This can be accomplished in not only the enterprise version of SharePoint, but in SharePoint Foundation.

It’s going to be a lot of fun!

My co-worker at Rackspace, Javier Barrera will also be presenting there.  His session is for SharePoint admins: SharePoint Search: A Look Behind the Curtain for System Administrators

Rackspace will also be a sponsor at the event, so look for us hanging out in our booth!

 

Permanent Link to Post | Email Post Link | Number of Comments 1 Comment(s)
March 16
List Form Fields–Show/Hide For Certain People: Part 2
by  lauraNo presence information  on 3/16/2012 4:09 PM

In this second post of the three part blog series, I will show how you can show or hide fields according to whether or not the currently logged in person is part of a certain SharePoint group.

This is a three part blog:

In this example, I have a task list, and there are only certain people who should be able to edit the task's due date.  Others should be able to see it but not edit it. This concept is very similar to the concept in the previous blog post, there are just a few things different in the steps.

This solution in part 2 can be done with any enterprise version of SharePoint: MOSS, SharePoint 2010, even SharePoint Online with Office 365 (enterprise plans).

  1. Create a custom list on your site, just to keep a single item in, with a very simple purpose that will be apparent as we go.  I'll call it "Single Item".  Add one item to the list, just type anything in the Title field.
  2. Open SharePoint Designer.  In Lists and Libraries, open your task list.  In the Forms section on the right, click the New button.
  3. Call your new file EditCustom, pick Edit item form, and check the box to set as default.  Click OK.
  4. Click the name of your new EditCustom.aspx form to open it. 
  5. Click your cursor inside the form on the screen somewhere, so that the contextual ribbon will show the appropriate options.  Click the Parameters button on the Options tab.
  6. Click the New Parameter button.  Call it the FilterParam, select Query String, and type Filter as the query string variable.  Click OK.  (side note: all those other 3 variables were already there, I didn't add them)

  7. Select the Due Date field with your cursor:

  8. On the Options tab in the ribbon, click Conditional Formatting, and choose Show Content.
  9. On the Condition Criteria screen, click the Advanced button.
  10. Type $FilterParam!=''  then click OK and click OK again.  This means that if the task admin parameter is not blank, it will show the content you selected, which is the date editable field.

  11. With the cursor still in the Due Date right column, select the Due Date field in the Data Source Details pane on the right.  Click Insert Selected Fields As… choose Formatted… and choose DateTime.

  12. Now you'll see a "read only" date on your form.  It's time to create a rule that will show this field when the logged in person is not a task admin.  Note that with conditional formatting, you do have the ability to select an entire row if you want, and just show/hide the whole thing.
    Select the new date you just added to the form.  Click the Conditional Formatting button and choose Show Content.  Repeat steps 9 and 10, except this time don't put an exclamation mark (!) in the formula.
  13. Save your changes.
  14. Click the F12 button on the keyboard to open the page in the browser.  Be sure to flip back over to SharePoint Designer and CLOSE that aspx form.
  15. In the browser, click the Page tab.  Click the Edit Page button.
  16. Click the big white section on the page that says Add a web part.  Add the Single Item list that you created at step 1.
  17. For the Single Item web part, in the Toolpane, expand the Advanced section. In the Target Audiences box, type or select the name of the group of people that you DO want to be able to edit the task due date. Click OK.
  18. Click the black arrow at the top right of the Task Admins web part, and choose Connections.  Choose Send Row of Data to, and choose your Task web part.
  19. Choose Get Parameters From, and click Configure.

  20. The Provider field name is "Title", and the consumer is the FilterParam.  Click Finish.

  21. Now that the web parts are connected, and you're seeing the editable Due Date field if you're in the SharePoint group that you used in step 17, it's time to hide the Single Item web part.  In the web part toolpane for Single Item, expand the Layout section.  Check the box next to Hidden, and click OK.
  22. On the page tab at the top, click Stop Editing.

Go ahead and test the solution.  Navigate to your Tasks list as you normally would, and Edit one of the tasks.  You'll notice that if you're in the list of task admins (or whatever SharePoint group you used at step 17), you'll see the Due Date as editable.  Then, take yourself out of that SharePoint group, and then when you edit a task, you won't be able to change the due date.

     

Technorati Tags: SharePoint,data view web parts,web parts,parameters,forms,fields,list form

Permanent Link to Post | Email Post Link | Number of Comments 5 Comment(s)
March 15
List Form Fields–Show/Hide For Certain People: Part 1
by  lauraNo presence information  on 3/15/2012 2:00 PM

Three years ago, I wrote a blog post called Displaying SharePoint Fields by Permission Level.  This one has the highest amount of hits, but it is an imperfect solution.  One of the most common questions that was asked was to see if there's a way to show or hide fields in an ASPX form based on who the logged in user is, as opposed to according to permission level.

This is going to be a three part blog:

  • Part 1: Using an ASPX form, with a SharePoint list of certain people who will be allowed to edit certain fields
  • Part 2: Using an ASPX form, with a SharePoint group of people
  • Part 3: Using an InfoPath form, with a SharePoint list or group of people

In this example, I have a task list, and there are only certain people who should be able to edit the task's due date.  Others should be able to see it but not edit it.

This solution in part 1 can be done with any version of SharePoint: MOSS, WSS 3.0, SharePoint 2010, and Foundation, and even SharePoint Online with Office 365.

  1. Create a custom list on your site, just to keep the list of people who are authorized to edit the certain fields in your form.  I'll call it "Task Admins".  Create a field called "Person", as a people field.  Add a few people to the list.
  2. Open SharePoint Designer.  In Lists and Libraries, open your task list.  In the Forms section on the right, click the New button.
  3. Call your new file EditCustom, pick Edit item form, and check the box to set as default.  Click OK.
  4. Click the name of your new EditCustom.aspx form to open it. 
  5. Click your cursor inside the form on the screen somewhere, so that the contextual ribbon will show the appropriate options.  Click the Parameters button on the Options tab.
  6. Click the New Parameter button.  Call it the TaskAdminParam, select Query String, and type TaskAdmin as the query string variable.  Click OK.  (side note: all those other 3 variables were already there, I didn't add them)
  7. Select the Due Date field with your cursor:
  8. On the Options tab in the ribbon, click Conditional Formatting, and choose Show Content.
  9. On the Condition Criteria screen, click the Advanced button.
  10. Type $TaskAdminParam!=''  then click OK and click OK again.  This means that if the task admin parameter is not blank, it will show the content you selected, which is the date editable field.
  11. With the cursor still in the Due Date right column, select the Due Date field in the Data Source Details pane on the right.  Click Insert Selected Fields As… choose Formatted… and choose DateTime.
  12. Now you'll see a "read only" date on your form.  It's time to create a rule that will show this field when the logged in person is not a task admin.  Note that with conditional formatting, you do have the ability to select an entire row if you want, and just show/hide the whole thing.
    Select the new date you just added to the form.  Click the Conditional Formatting button and choose Show Content.  Repeat steps 9 and 10, except this time don't put an exclamation mark (!) in the formula.
  13. Save your changes.
  14. Click the F12 button on the keyboard to open the page in the browser.  Be sure to flip back over to SharePoint Designer and CLOSE that aspx form.
  15. In the browser, click the Page tab.  Click the Edit Page button.
  16. Click the big white section on the page that says Add a web part.  Add the Task Admins list that you created at step 1.
  17. For the Task Admins web part, in the Toolpane, click Edit the Current View.  Scroll down to the Filters section, and set it so that Person is equal to [me].  Click OK.
  18. On the Page tab, click Edit Page again.  Click the black arrow at the top right of the Task Admins web part, and choose Edit Web Part.  Click the black arrow at the top right of the Task Admins web part, and choose Connections.  Choose Send Row of Data to, and choose your Task web part.
  19. Choose Get Parameters From, and click Configure.
  20. The Provider field name is "Person", and the consumer is the TaskAdminParam.  Click Finish.
  21. Now that the web parts are connected, and you're seeing the editable Due Date field if you're in the list of admins, it's time to hide the task admins web part.  In the web part toolpane for Task Admins, expand the Layout section.  Check the box next to Hidden, and click OK.
  22. On the page tab at the top, click Stop Editing.

Go ahead and test the solution.  Navigate to your Tasks list as you normally would, and Edit one of the tasks.  You'll notice that if you're in the list of task admins, you'll see the Due Date as editable.  Then, take yourself out of the list of Task Admins, and then when you edit a task, you won't be able to change the due date.

     

Technorati Tags: SharePoint,data view web parts,web parts,parameters,forms,fields,list form

Permanent Link to Post | Email Post Link | Number of Comments 6 Comment(s)
February 16
Big Rackspace News (and a party)!
by  lauraNo presence information  on 2/16/2012 10:08 AM
Category: conference

This morning I'm beyond thrilled to announce that Rackspace has purchased SharePoint911. Now all of us are Rackspace employees, AKA "Rackers". Back in January, our team took a trip out to San Antonio to the RackSpace headquarters, to meet our future colleagues and see what the company is all about.

Rackspace and SharePoint911 are a great fit with each other when it comes to corporate culture and personalities, and we're eager to work with them to share our expertise and build the SharePoint services in the company.

We've put together a list of frequently asked questions on our website (which has a new look, by the way!):

Here are some of the links to the big (official) news announcements today:

SPTechCon…

For those of you who will be attending the SharePoint Technology Conference in February, we have a treat for you. We will be hosting a party to celebrate this news! Here are the details:

SPint – Hosted by Rackspace and newly acquired SharePoint911
When: Monday, Feb 27th 7:30-10:00p
Where: Johnny Foley's, 243 O'Farrell St (half block from Hilton)
What: Enjoy eats and drinks with Rackspace and help us welcome SharePoint911 to the Rackspace family!

See you there!!

Oh, and here's a fun link. It gives a glimpse of what it's like to work at the Rackspace headquarters:

Rackspace - A day in the life

   

  

Permanent Link to Post | Email Post Link | Number of Comments 1 Comment(s)
1 - 10Next
Alert Me Alert Me
RSS FeedFacebookYouTube
 

 Pages

 
NameUse SHIFT+ENTER to open the menu (new window).
  
About Me
Data View Web Part Screencasts
SharePoint FREE Resources
Speaking Engagements
Webcasts
 

 Our Books for End Users

 
 

 Most Popular Posts

 
TitleUse SHIFT+ENTER to open the menu (new window).
  
# CommentsUse SHIFT+ENTER to open the menu (new window).
  
Display a Sub-Site List on a Top Level Site85
Workflow: Reminder Before Due Date – MOSS vs. WSS79
Displaying SharePoint Fields by Permission Level76
The Text Filter Web Part – Without Having To Filter Exact Text67
Web Part: Sites that I have access to66
List of SharePoint 2010 Web Parts66
SharePoint List Form – Default User Information60
Using Content Types as Statuses47
SharePoint 2010 – Where’d “My Links” Go?43
Financial Roll-Up Web Part37
InfoPath 2010 and Repeating Tables36
Click to Copy List Item to New36
Phone Number Validation in SharePoint 200734
InfoPath User Roles in Browser-Based Forms- Another Way (Part 1 of 2)32
“Data View Preview” in SharePoint Designer 201031
1 - 15Next
 

 Laura on Twitter

 
SingleMaltShot (Tyler Durham)
Good stuff RT @WonderLaura: Hiding "Share Site" action from the #SharePoint online sites http://t.co/d4dMf7rP #Office365
5/16/12 10:44 PM
Teamharmonie (Michal and Jenna)
RT @deefken: @WonderLaura wow, harmon.ie is really nice! It's just a bit to expensive... Enterprise license coming soon...
5/16/12 10:30 PM
WonderLaura (Laura Rogers)
Hiding “Share Site” action from the #SharePoint online sites http://t.co/JUqsyOFA #Office365
5/16/12 09:41 PM
bartb1067 (bartb)
RT @SharePointFest: SharePoint Fest Daily is out! ▸ today's top stories via @jwillie @teameusp @WonderLaura @jmancini77 ▸ http://t.co/PcONsgaJ
5/16/12 07:52 PM
phillduffy (Phill Duffy)
RT @pjcov: @WonderLaura plus a big thankyou + congrats to @nellymo for technically editing the book. @brettlonsdale @phillduffy
5/16/12 03:42 PM
NintexNinja (NintexNinja)
How to build a "My Company Portal" in #SharePoint Online http://t.co/n1q3Ombi (via @WonderLaura)
5/16/12 02:00 PM
WonderLaura (Laura Rogers)
RT @jennifermason: This is great! Watch and see what my new office location is like! http://t.co/r8pWao0d
5/16/12 01:12 PM
WonderLaura (Laura Rogers)
Book RTM’d today: Microsoft #SharePoint 2010 Business Connectivity Services http://t.co/Ad7zK0vl congrats @brettlonsdale @pjcov @phillduffy
5/16/12 01:05 PM
WonderLaura (Laura Rogers)
#OneNote Tip 5: Connect task lists & turn notes into emails http://t.co/iT6hbDVp
5/16/12 01:04 PM
More Results...
 

 Laura Rogers Calendar

 
< May, 2012 >
 Sun  Mon  Tue  Wed  Thu  Fri  Sat 
 29 
  30 
  1 
  2 
  3 
  4 
  5 
 6 
  7 
  8 
  9 
  10 
  11 
  12 
 13 
  14 
  15 
  16 
  17 
  18 
  19 
 20 
  21 
  22 
  23 
  24 
  25 
  26 
 27 
  28 
  29 
  30 
  31 
  1 
  2