Showing posts with label regions. Show all posts
Showing posts with label regions. Show all posts

Tuesday, March 20, 2012

Data regions are not allowed inside a table detail ..

Developing using Visual Studio .Net (2003).
I have a simple table on my report showing data from a dataset. Works
fine. Displays a bunch of records.
One of the values from my dataset is a percentage value (integer from 0
to 100). I'm attempting to illustrate this using a chart. So I'm
attempting to put a chart in the table detail row. It doesn't like me
doing this, though. I get a build error:
"The chart 'chartx' is contained inside a table detail row. Data
regions are not allowed inside a table detail...".
Is there a way to do what I'm attempting with Visual Studio .Net (i.e.
SQL Server 2000 Reporting Services)? I know it can be done with Visual
Studio 2005, as that just makes you define a group expression when
attempting to "use a data region in a list".
Any help/info would be great.
Thanks.Have you tried putting it inside a matrix?
I tried putting a chart inside a table detail row, but vs didn't let me
do it "Cannot place a chart at this location in a table"
However, putting it inside a matrix works just fine.
eamon wrote:
> Developing using Visual Studio .Net (2003).
> I have a simple table on my report showing data from a dataset. Works
> fine. Displays a bunch of records.
> One of the values from my dataset is a percentage value (integer from 0
> to 100). I'm attempting to illustrate this using a chart. So I'm
> attempting to put a chart in the table detail row. It doesn't like me
> doing this, though. I get a build error:
> "The chart 'chartx' is contained inside a table detail row. Data
> regions are not allowed inside a table detail...".
> Is there a way to do what I'm attempting with Visual Studio .Net (i.e.
> SQL Server 2000 Reporting Services)? I know it can be done with Visual
> Studio 2005, as that just makes you define a group expression when
> attempting to "use a data region in a list".
> Any help/info would be great.
> Thanks.sql

Data regions

Greetings,

Can someone explain the rationale as to why nested data regions are restricted to use the same dataset?

Craig

We didn't have time so far to implement hierarchical data source support in our processing engine - but it is under consideration for a future release.

Anyway, there are a few options available today to achieve similar results:
* join the datasets already in the query (e.g. by using linked server functionality)
* use subreports for the "nested data region" - but this is usually not very efficient
* use SQL Server 2005 Integration Services to join the datasets in the query (there are various options to perform such joins) and use that SSIS package directly in reporting services as data source.

-- Robert

|||

hey Robert,

can you point me toward some documentation on how to do this:

"use SQL Server 2005 Integration Services to join the datasets in the query (there are various options to perform such joins) and use that SSIS package directly in reporting services as data source."

Thanks,

jen

Data regions

Greetings,

Can someone explain the rationale as to why nested data regions are restricted to use the same dataset?

Craig

We didn't have time so far to implement hierarchical data source support in our processing engine - but it is under consideration for a future release.

Anyway, there are a few options available today to achieve similar results:
* join the datasets already in the query (e.g. by using linked server functionality)
* use subreports for the "nested data region" - but this is usually not very efficient
* use SQL Server 2005 Integration Services to join the datasets in the query (there are various options to perform such joins) and use that SSIS package directly in reporting services as data source.

-- Robert

|||

hey Robert,

can you point me toward some documentation on how to do this:

"use SQL Server 2005 Integration Services to join the datasets in the query (there are various options to perform such joins) and use that SSIS package directly in reporting services as data source."

Thanks,

jen