Error Opening Report in Report Builder

I try to open an existing report definition like "Bug Rates" (or any other ones for that matter) and always recieve an error with this: "Server data sources do not match RDL". Has anyone experienced this or know of a way to fix this?It appears your report has multiple data sources in it, which means you probably built the report in Report Designer. Report Builder expects the report to have exactly one data source -- a report model. It has many other limitations as well, so opening an arbitrary RD report in RB is generally not supported (although vice-versa is fine).|||

I too get this error. These are not reports that have been created in Report Builder by us, but are part of the MSF Agile process template with Team Foundation Server.

A range of standard reports are loaded when a new Team Project is created. It seems impossible to edit these using Report Builder.

There are two data sources defined in the standard TFS installation: TfsOlapReportDS and TfsReportDS. These both seem present in the reports if you go in to Properties -> Data Sources.

If this is the problem, and Report Builder has this limitation, how are we meant to amend the Team Foundation Server default reports?

This is obvious "as intended" from the TFS guys, and obviously SQL Reporting Services copes with multiple data sources as viewing the reports are fine.

But editing these without resorting to getting highly confused in manually editing the RDL is achieved how?

Many thanks,

Jonathan

|||We resorted to writing our own reports based on creating a model from TFSReportDS using the basic report builder. It isn't too difficult but take some getting used to. My boss has messed around with the more elaborate report editing that you can use via IDE extensions and was able to open the pre-baked report though he couldn't really make heads or tails of the underlying queries (and there are usually many) needed for what seemed to be a basic report. So far the feeling we have, is keep it basic or you need an incredible amount of OLAP related querying understanding to extend the reports.