Monday, March 12, 2012
how to add multiple entities in report builder?
Have created a datasource and use report builder the build a report.
When I *start* a *new* report I see all the entitities (tables) in the
database on the left hand side......I can drag and drop tables/
columns to the report BUT once I have dragged *one* entities columns
to the report all the others disappear......
so I now *only* have one entity on the left hand side with its columns
below.
Is this expected behavour? I thought I would be able to add another
entity and make a join between them...but this doesnt seem to be
possible?
How can i make other entitiies display in the explorer on the left?
Thanks
Al BlakeHi
RB works with Report Model and the relations are set there. If you want to
add any other entity you need to define there at RM. This behaviour is by
design.
Amarnath, MCTS
"scubaal" wrote:
> I have SQLRS running under MOSS (ie in a report library).
> Have created a datasource and use report builder the build a report.
> When I *start* a *new* report I see all the entitities (tables) in the
> database on the left hand side......I can drag and drop tables/
> columns to the report BUT once I have dragged *one* entities columns
> to the report all the others disappear......
> so I now *only* have one entity on the left hand side with its columns
> below.
> Is this expected behavour? I thought I would be able to add another
> entity and make a join between them...but this doesnt seem to be
> possible?
> How can i make other entitiies display in the explorer on the left?
> Thanks
> Al Blake
>
Wednesday, March 7, 2012
How to add a second table in Report Builder?
Hi
I need a report with two tables. Table one pulls information from one entity in my database and table two pulls info from another entity in the same database.
I built a report model so that, I can access different tables using the same DataSource. But I don't seen an option to add a second table for the same report in Report Builder.
All my server components are on Win2003 server and client components on Windows XP.
I would greatly appreciate any pointers and suggestions on the same.
Thanks
Preps.
In Report Builder you can create report with only one dataregion (table, matrix, chart). But you can load this report into Report Designer and add more data sources and more data regions.
<edit>
|||More info on creating model-based reports in Report Designer:
http://msdn2.microsoft.com/en-us/ms345642(sql.90).aspx
Friday, February 24, 2012
How to Add a Calculated Column in Report Builder using a Model Based on a SSAS Cube
I am trying to add a calculated field / column in Report Builder when working with a Report Model built from anAnalysis Services Cube. I can create the calculated Field/Columns, but I get an error whenever I try to use it in a report.
Is there a way to create a report builder calculated column on report models built from a SSAS cube? Is this supported?
Thanks,
Some functions are not supported for calculated fields when running against an SSAS cube, in particular the aggregate functions like Sum, Count, Average, etc. The error message should provide some details on this.
Hope that helps!
|||The support for calculated fields in an SSAS model is better than Bob lets on. Most functions work. The trick is that you need to install Excel 2003 on the Analysis Services server. (Not sure if other versions like Excel 2007 work, but I know Excel 2003 does the trick.)
Report Builder builds MDX that use Excel functions, and for those functions to succeed, Excel has to be installed on the server.
If you agree with me that this is a terrible architecture, vote for this issue:
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=124864
|||Are there any online documentation about this? Our IT policy is not to install office or office application on SQL Server boxes.|||Common policy. Vote for that issue at connect.microsoft.com and maybe MS will change this in Katmai.
As for documentation:
http://msdn2.microsoft.com/en-us/library/ms145486.aspx
And documentation of the excel functions that are supported. (Don't know if there's a 2005 version of this page, but they're the same):
http://msdn2.microsoft.com/en-us/library/aa178231(SQL.80).aspx
I suppose one workaround is to code the Excel functions yourself and register them as specified here:
http://geekswithblogs.net/darrengosbell/archive/2006/12/13/100998.aspx
If you have interest in going that route, let me know because there are some gotchas.
How to Add a Calculated Column in Report Builder using a Model Based on a SSAS Cube
I am trying to add a calculated field / column in Report Builder when working with a Report Model built from anAnalysis Services Cube. I can create the calculated Field/Columns, but I get an error whenever I try to use it in a report.
Is there a way to create a report builder calculated column on report models built from a SSAS cube? Is this supported?
Thanks,
Some functions are not supported for calculated fields when running against an SSAS cube, in particular the aggregate functions like Sum, Count, Average, etc. The error message should provide some details on this.
Hope that helps!
|||The support for calculated fields in an SSAS model is better than Bob lets on. Most functions work. The trick is that you need to install Excel 2003 on the Analysis Services server. (Not sure if other versions like Excel 2007 work, but I know Excel 2003 does the trick.)
Report Builder builds MDX that use Excel functions, and for those functions to succeed, Excel has to be installed on the server.
If you agree with me that this is a terrible architecture, vote for this issue:
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=124864
|||Are there any online documentation about this? Our IT policy is not to install office or office application on SQL Server boxes.|||Common policy. Vote for that issue at connect.microsoft.com and maybe MS will change this in Katmai.
As for documentation:
http://msdn2.microsoft.com/en-us/library/ms145486.aspx
And documentation of the excel functions that are supported. (Don't know if there's a 2005 version of this page, but they're the same):
http://msdn2.microsoft.com/en-us/library/aa178231(SQL.80).aspx
I suppose one workaround is to code the Excel functions yourself and register them as specified here:
http://geekswithblogs.net/darrengosbell/archive/2006/12/13/100998.aspx
If you have interest in going that route, let me know because there are some gotchas.