• To add your Office 365 email account, click on 'Add Account' in the welcome screen:

• In the Accounts dialog, just pick the Exchange Account option:

• Use your Office 365 account as email address and username:

If you previously dismissed the welcome screen or need to add additional accounts, the Accounts dialog can also be accessed via Tools > Accounts or Outlook > Preferences and then selecting the second option under Personal Settings for Accounts:

 or

If you have any questions or feedback please leave me a comment or send me an email at sunder.raman at microsoft.com.

Reporting in TFS 2010 deck: [View:https://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-74-54/0474.Reporting-in-Team-Foundation-Server-2010.pptx]

Thanks for your patience!

When running through Step 4 of this article, if you specified ‘TfsWarehouse’ as the warehouse database name then you probably saw the following warning on the Reporting dialog: “The database you specified cannot be used. The database exists, but its schema is not valid for use with Team Foundation Server.”

How can you fix this?

Specify a different database name. You can use the same names we default to on a clean TFS 2010 installation: ‘Tfs_Warehouse’ for the Warehouse database and ‘Tfs_Analysis’ for the Analysis Services database (the second tab of this dialog).

Once you change the database name, if you click ‘Test Connection’ button you should one of the following success messages on the dialog:

	You don’t have a database with this name on the SQL Server and one will be created for you. Note that you’ll need appropriate permissions on SQL Server to create the database itself.
	If you created an empty database already or if you didn’t have access to your SQL Server and asked your SQL Admin to create an empty database for you, TFS can use that database as the warehouse database.

Why didn’t you just use my old Warehouse database?

We don’t support upgrading the Warehouse or Analysis database from the Admin Console. We have changed the schema quite a bit so it breaks old 2005/2008 reports. We wanted to leave the old databases in place so you can have working (albeit stale as we don’t populate the old warehouse with new data) reports while you migrate your reports to the new schema. In fact, even if you chose to upgrade your TFS 2005/2008 server along with reporting we automatically create new Warehouse and Analysis database because of the schema changes.

• Walkthroughs for out-of-the-box experience including customizations
  • SharePoint Dashboard
  • Rich SQL Reporting Services Reports
  • Excel Reports from Work Item Queries
• Custom report authoring tools and walkthroughs
  • Options and tools
  • Custom report in Excel walkthrough
  • Custom report in Report Builder walkthrough
  • Relational reporting
• An overview of the reporting architecture

As we saw in the previous posts in this series, we ship a lot of useful reports and dashboards out-of-the-box in TFS 2010. In addition, we do open up several options for building your own reports specific to your organizational needs:

• Ad-hoc Excel reports
• Custom SQL Server Reporting Services  (SSRS) reports
• Relational reporting
  • This is a new option that is officially supported in 2010. I’ll cover more about what this means to you in a subsequent post.

Here’s a look at report authoring tools and how they stack up in terms of the power and complexity. I’ve also outlined some of the options for sharing custom reports built using these tools in the image below.

• Excel
  • This is the easiest option for getting started and is plenty powerful for most purposes and available in a tool you are already familiar with.
• Report Builder
  • This is a SQL Sever tool freely available for download here: https://www.microsoft.com/sqlserver/2008/en/us/report-builder.aspx
• BIDS
  • This is as powerful as it gets for a report authoring tool and is a development tool available with your SQL Server installation.

Let’s pivot the tool choice and look at the options based on the kind of reports you can author using these tools:

We ship Excel reports that are available on the SharePoint Server dashboards built in Excel and we also use BIDS to build a few complex SSRS reports like Stories Overview report that’s available in the Agile 5.0 template.

In my next post I’ll cover a walkthrough for building a custom report in Excel. If you have questions or feedback please leave me a comment or send me an email at sunder.raman at microsoft.com

The sample shows an example for moving custom data into the warehouse and cube to enable reporting on code churn by assembly for C# assemblies. It also includes documentation for getting started including do’s and don’ts when building your own adapter.

We put in a significant effort in the recent weeks to improve the final cube processing performance for RTM. While we contained most of the changes such that they don’t alter public schema of the cube we, unfortunately, had to make one final change that impacts the Test Result dimension in the cube as it improves processing performance significantly.

We removed Area and Iteration attributes from the Test Result dimension as shown below:

Test Result dimension in RC	Test Result dimension in RTM

So, how do you report on these? John Socha-Leialoha has a blog post outlining the report changes you’ll need to make: https://www.socha.com/blogs/john/2010/03/upgrading-team-foundation-server-2008.html. We’ll also release instructions in our upgrade guide documenting the steps needed to update RC reports based on this change.

• Walkthroughs for out-of-the-box experience including customizations
  • SharePoint Dashboard
  • Rich SQL Reporting Services Reports
  • Excel Reports from Work Item Queries
• Custom report authoring tools and walkthroughs
• An overview of the reporting architecture

I know how to get this list of results using a work item query:

But, I want a chart like these without having to ask my developers:

Let’s look at how to get this done in TFS 2010:

Perfect – a cool report generated with just a few mouse clicks! Now, let’s backup and see how this works.

First, I ran a query to get Active Tasks in my project showing Assigned To, Remaining Work, Completed Work etc. in my query results:

In the new menu bar that’s on the query results window, I have a new option to create a report in Excel:

The work item query is translated to figure out the reports that can be generated and I get report options based on columns included in my work item query. I have the option to generate Current as well as Trend reports.

Let’s pick current and trend reports for remaining work by assignment:

The selected reports are generated:

Current report:

and Trend report:

Now, that was super easy! The first worksheet generated includes a useful table of contents with links to reports:

The reports that are generated are not static and can be modified so it is very powerful. Let’s say I want to make some simple adjustments to the current report so it’s a bar chart and also tweak some colors. I can just as easily tweak the Team Project filter to make it a cross project report or drag additional fields like Completed Work to show more information.

Similar to what we saw in my previous posts, I can easily publish this report to my team dashboard to share this with my team. I can use the Excel Services Options button to publish the entire workbook or specific charts. I’ll publish the customized report to the Excel Reports document library like the out-of-the-box Excel reports shown on the MOSS dashboard.

Then, I all have to do is use standard SharePoint functionality to edit my team dashboard, add an Excel Web Access web part to display the report from my newly published workbook:

So, it was easy to go from here…

to here:

In the next topic I’ll cover custom reporting including walkthroughs for tools of choice. If you have questions or feedback please leave me a comment or send me an email at sunder.raman at microsoft.com

• Adding reports and/or dashboards on an existing project that was created without these options
• Adding the new Agile/CMMI RC version of the reports to existing projects after upgrading from TFS 2008 to TFS 2010
  • We provision updated version of 2008 reports that works with the new warehouse and cube schema when the server is upgraded from TFS 2008 to TFS 2010. These instructions allow you to provision the latest version of the reports from 5.0 version of the templates to these projects and wire them up.
• Updating reports on existing project to latest version after upgrading TFS 2010 from Beta 2 to RC

The steps aren’t where we’d like it to be, but its far better than the manual workaround that involved creating a temporary project we had in Beta 2. It still requires updating each project individually and we are working on a powertool to make that easier for RTM.

My colleague, Gregg Boer, has posted the instructions on his blog: https://blogs.msdn.com/greggboer/archive/2010/02/24/creating-sharepoint-portals-reports-and-upgrading-reports-for-an-existing-team-project.aspx