TF208015 Error when we export data to excel

Question

The below message we get it after installing the VS and Team explorer 2010 connected to TFS 2008. in VS 2005 we didn't have this problem

TF208015: You are trying to add work items that are not in the selected team project for this Microsoft Excel file. Only the work items from the SMS Management team project will be added to your work item list. If you want to add work items from another tem project, open a new Microsoft Excel file from that team project

Any suggestions and help???

We didn't have this problem with VS 2005

 

Answer 1

None of the TFS Office Add-Ins has supported exporting workitems from multiple team projects.  This has been a frequently requested feature and is on my backlog to do for an upcoming release. 

The suggested work around is to create separate workbooks bound to different team projects. You can then aggregate the data from tables.  Table names are persistent with the TFS 2010 Add-In so this is more stable.  Unfortunately, you still need to do a refresh in multiple workbooks.

John Nierenberg (TFS)

 

Answer 2

Hi John, What you are saying is that “None of the TFS Office Add-Ins has supported exporting workitems from multiple team projects”. But this is what we used to do in the VS 2005 version. I used to created a query from the SMS Management project that returns for example the list of all test cases related to all my projects. Then I used to select the work items that belonged to one project and export it to excel. I guess what you are trying to say is that, following the above example, I won’t be able to select all work items returned from my query (belonging to different projects) and export them using excel, and this was true in VS 2005 where I also used to get an error. But what I used to do in that case is select all the work items belonging to the same project and export them to excel. This is what I’m not able to do anymore in the VS 2010 version.

Answer 3

You should be able to export all of the work item belonging to one project and export them.  You may need to check which project is selected when you export.

Answer 4

Hello John, June last year you replied that this issue was on your backlog to be implemented. Can you say anything about it at this point in time? We are facing the same issues here.

Answer 5

Me too!

---

michhes (http://blog.mediawhole.com)

Answer 6

Me too....

Answer 7

I was having this problem too and I was able to fix it just now with John's suggestion: "You may need to check which project is selected when you export"

Over in the Team explorer pane, I have two project folders and I had the "wrong" one selected.  When I selected the folder that contained the items in my query, I was able to export to Excel without the error.

 

-e

PS: Hey John, add me to the list of people requesting this feature, or at least try to have VS be smart about selecting the correct project when exporting.

Answer 8

ETA on this fix?

Answer 9

John, FYI, I'd have a hard time telling Management they have to read 50 separate reports, or that we have to change the "aggregate" workbook every time a new Team Project is created.

 

---

John Saunders
WCF is Web Services. They are not two separate things.
Use WCF for All New Web Service Development, instead of legacy ASMX or obsolete WSE
Use File->New Project to create Web Service Projects

Answer 10

We are experiencing the same problems.  Any known work around?

Answer 11

Closing in on 2 years now...any news on this?  

Our workaround is to simply to select all of the query results while in Team Explorer, then copy, then paste out to a clean Excel workbook.   It's not connected to the data source, but you can now sort, filter, pivot, chart etc.

Answer 12

Hi,

In my company we had the same problem, at the end we solve this implementing an Excel Addin, it works faster and we can retrieve workitems from different Projects.

If any of you start to implement such an Excel addin, I could help you

Regards, Saludos