Showing posts with label model. Show all posts
Showing posts with label model. Show all posts

Friday, March 9, 2012

Problem: Reporting using Report Model

I'm having a reporting problem when using the report model as my data source. I was able to duplicate the problem by trying to create a report dataset using the ModelTutorial (based on the AdventureWorks database) as my data source.

For example, say you wanted to get all products which have illustrations. The query shown below would retrieve the 23 rows as expected (don't worry about duplicate products for this example).

SELECT P.ProductID, P.ProductNumber, P.Name, I.IllustrationID, I.ModifiedDate
FROM Production.Product P
INNER JOIN Production.ProductModel PM ON P.ProductModelID = PM.ProductModelID
INNER JOIN Production.ProductModelIllustration PMI ON PM.ProductModelID = PMI.ProductModelID
INNER JOIN Production.Illustration I ON PMI.IllustrationID = I.IllustrationID

Trying to create a dataset to get this same information using the report model as the data source is my problem. I am unable to get fields from all the following 4 tables: Product, ProductModel, ProductModelIllustration, and Illustration. I can get fields from the ProductModel, ProductModelIllustration, and Illustration tables, but not the Product table. The circle with the diagonal shows up when I try to drag a field from the Product table into the dataset area. What am I doing wrong?

Are you able to query Product table alone?|||

Yes, I can return records from the Product table alone. I created a report to display the product name and number for all products. It returned 504 rows as expected.

In addition, I can generate a dataset with fields from both the Product and ProductModel table. However, when I try to add a field from the ProductModelIllustration table, I am denied (circle with the diaganol line).

|||It is hard to guess without knowing your model.|||

As mentioned above, I duplicated the problem with the ModelTutorial Model (based on the AdventureWorks database). You can duplicate this model by following the "Creating a Report Model" tutorial in SQL Server Books Online (see below link).

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/sqltut9/html/395a4f26-6401-4ee1-8658-be8b43cc70a8.htm

If the link above does not work for you, you can find the tutorial in books online by searching for tutorials [Reporting Services], then click on Reporting Services Tutorials link, then click on the Creating a Report Model link. Once you have the model built and deployed, you should have no problem duplicating my problem.

|||

My understaning is that relations are:

Product -(many to one)- ProductModel -(one to many)-Illustration

This case is not supported automatically.

|||

You are close, but the relations are as follows:

Product -(many to one)- ProductModel -(one to many)- ProductModelIllustration -(many to one)- Illustration

This scenario will come up frequently for report model designers. In fact, it will occur every time there is a junction (aka intersection) table in the model.

If this case is not supported automatically, can you explain in detail the best way to handle it manually (e.g. view in database, new named query in model, etc.)?

Thanks for your help.

|||

Transition many-one-many is not supported. Additional relation (in this case ProductModelllustration -Illustration) is not important.

Easiest way to do it is to add named query.

Wednesday, March 7, 2012

Problem writing a report on a generated Report Model

I get this error message:

Semantic query execution failed.
The 'PerspectiveID' custom property for the 'query' perspective is either not set or is not set to the string data type.

The report model does have a perspective.

Anyone else seen this?

I believe this occurs when you create a report based on a report model generated from Analysis Services, and you do not specify a perspective. This should never happen in Report Builder (it should always force you to choose a perspective). Can you provide more details?|||

Hi Bob, yes thanks for your interest, I was trying to use BI Dev Studio report designer to write the report on a report model generated from AS.

The AS database has perspectives, so the RM picks those up OK. Report Builder works fine, but I cant get BI Dev Studio to connect to the perspective - hence the error I posted before.

Thanks again

|||Sorry for the delay in responding...in BI Development Studio there is currently no UI for specifying a perspective on a report model query. The perspective is specified using a CustomProperty in the report model query XML. If you create a basic query using the same perspective in Report Builder, then save that report as a file and bring it up in BI Dev Studio, you can use the generic (text) query designer to see the custom property in the query XML that specifies the perspective. You can use this basic query as a starting point in your report, or you can copy the custom property into your existing query to avoid the error you are getting.|||Is still the only solution to creating a report Desinder report attached to a model?|||

Are there any plans to address this issue in either a service pack for BI Studio 2005 or in Orcas or Katmai? It's pretty lame to have to go in and edit the semantic query xml by hand - the whole point of using the semantic model is to abstract away the arcane SQL (or MDX) so it seems like an oversight to have missed this little nuance for OLAP sources.

By the way the only reason I want this fixed so bad is that the ability to use BI Studio to design reports over a semantic model is extremely awesome and a great selling point for my end users that would be too limited by Report Builder - so it just kills me that this otherwise awesome story is a little tarnished with this complexity.

|||

Hi, I met the same problem when I use report builder to design report from a report model. This report model was generated from a SSAS cube in my report server web site.

Initially, this report builder worked well. After I enabled "Allow user drill this report from other reports" in the report properties window, the error occured. I could not save or view the report.

The problem is the report model is in the report server. How may I get the XML file? And we need let end user to use Report Builder to design and publish reports by themselves. It is difficult to explain all of above operation to end user and let them edit XML file to fix the issue.

Obviously,it is really a critical issue. Please fix it asap.

Problem writing a report on a generated Report Model

I get this error message:

Semantic query execution failed.
The 'PerspectiveID' custom property for the 'query' perspective is either not set or is not set to the string data type.

The report model does have a perspective.

Anyone else seen this?

I believe this occurs when you create a report based on a report model generated from Analysis Services, and you do not specify a perspective. This should never happen in Report Builder (it should always force you to choose a perspective). Can you provide more details?|||

Hi Bob, yes thanks for your interest, I was trying to use BI Dev Studio report designer to write the report on a report model generated from AS.

The AS database has perspectives, so the RM picks those up OK. Report Builder works fine, but I cant get BI Dev Studio to connect to the perspective - hence the error I posted before.

Thanks again

|||Sorry for the delay in responding...in BI Development Studio there is currently no UI for specifying a perspective on a report model query. The perspective is specified using a CustomProperty in the report model query XML. If you create a basic query using the same perspective in Report Builder, then save that report as a file and bring it up in BI Dev Studio, you can use the generic (text) query designer to see the custom property in the query XML that specifies the perspective. You can use this basic query as a starting point in your report, or you can copy the custom property into your existing query to avoid the error you are getting.|||Is still the only solution to creating a report Desinder report attached to a model?|||

Are there any plans to address this issue in either a service pack for BI Studio 2005 or in Orcas or Katmai? It's pretty lame to have to go in and edit the semantic query xml by hand - the whole point of using the semantic model is to abstract away the arcane SQL (or MDX) so it seems like an oversight to have missed this little nuance for OLAP sources.

By the way the only reason I want this fixed so bad is that the ability to use BI Studio to design reports over a semantic model is extremely awesome and a great selling point for my end users that would be too limited by Report Builder - so it just kills me that this otherwise awesome story is a little tarnished with this complexity.

|||

Hi, I met the same problem when I use report builder to design report from a report model. This report model was generated from a SSAS cube in my report server web site.

Initially, this report builder worked well. After I enabled "Allow user drill this report from other reports" in the report properties window, the error occured. I could not save or view the report.

The problem is the report model is in the report server. How may I get the XML file? And we need let end user to use Report Builder to design and publish reports by themselves. It is difficult to explain all of above operation to end user and let them edit XML file to fix the issue.

Obviously,it is really a critical issue. Please fix it asap.

Problem writing a report on a generated Report Model

I get this error message:

Semantic query execution failed.
The 'PerspectiveID' custom property for the 'query' perspective is either not set or is not set to the string data type.

The report model does have a perspective.

Anyone else seen this?

I believe this occurs when you create a report based on a report model generated from Analysis Services, and you do not specify a perspective. This should never happen in Report Builder (it should always force you to choose a perspective). Can you provide more details?|||

Hi Bob, yes thanks for your interest, I was trying to use BI Dev Studio report designer to write the report on a report model generated from AS.

The AS database has perspectives, so the RM picks those up OK. Report Builder works fine, but I cant get BI Dev Studio to connect to the perspective - hence the error I posted before.

Thanks again

|||Sorry for the delay in responding...in BI Development Studio there is currently no UI for specifying a perspective on a report model query. The perspective is specified using a CustomProperty in the report model query XML. If you create a basic query using the same perspective in Report Builder, then save that report as a file and bring it up in BI Dev Studio, you can use the generic (text) query designer to see the custom property in the query XML that specifies the perspective. You can use this basic query as a starting point in your report, or you can copy the custom property into your existing query to avoid the error you are getting.|||Is still the only solution to creating a report Desinder report attached to a model?|||

Are there any plans to address this issue in either a service pack for BI Studio 2005 or in Orcas or Katmai? It's pretty lame to have to go in and edit the semantic query xml by hand - the whole point of using the semantic model is to abstract away the arcane SQL (or MDX) so it seems like an oversight to have missed this little nuance for OLAP sources.

By the way the only reason I want this fixed so bad is that the ability to use BI Studio to design reports over a semantic model is extremely awesome and a great selling point for my end users that would be too limited by Report Builder - so it just kills me that this otherwise awesome story is a little tarnished with this complexity.

|||

Hi, I met the same problem when I use report builder to design report from a report model. This report model was generated from a SSAS cube in my report server web site.

Initially, this report builder worked well. After I enabled "Allow user drill this report from other reports" in the report properties window, the error occured. I could not save or view the report.

The problem is the report model is in the report server. How may I get the XML file? And we need let end user to use Report Builder to design and publish reports by themselves. It is difficult to explain all of above operation to end user and let them edit XML file to fix the issue.

Obviously,it is really a critical issue. Please fix it asap.

Problem writing a report on a generated Report Model

I get this error message:

Semantic query execution failed.
The 'PerspectiveID' custom property for the 'query' perspective is either not set or is not set to the string data type.

The report model does have a perspective.

Anyone else seen this?

I believe this occurs when you create a report based on a report model generated from Analysis Services, and you do not specify a perspective. This should never happen in Report Builder (it should always force you to choose a perspective). Can you provide more details?|||

Hi Bob, yes thanks for your interest, I was trying to use BI Dev Studio report designer to write the report on a report model generated from AS.

The AS database has perspectives, so the RM picks those up OK. Report Builder works fine, but I cant get BI Dev Studio to connect to the perspective - hence the error I posted before.

Thanks again

|||Sorry for the delay in responding...in BI Development Studio there is currently no UI for specifying a perspective on a report model query. The perspective is specified using a CustomProperty in the report model query XML. If you create a basic query using the same perspective in Report Builder, then save that report as a file and bring it up in BI Dev Studio, you can use the generic (text) query designer to see the custom property in the query XML that specifies the perspective. You can use this basic query as a starting point in your report, or you can copy the custom property into your existing query to avoid the error you are getting.|||Is still the only solution to creating a report Desinder report attached to a model?|||

Are there any plans to address this issue in either a service pack for BI Studio 2005 or in Orcas or Katmai? It's pretty lame to have to go in and edit the semantic query xml by hand - the whole point of using the semantic model is to abstract away the arcane SQL (or MDX) so it seems like an oversight to have missed this little nuance for OLAP sources.

By the way the only reason I want this fixed so bad is that the ability to use BI Studio to design reports over a semantic model is extremely awesome and a great selling point for my end users that would be too limited by Report Builder - so it just kills me that this otherwise awesome story is a little tarnished with this complexity.

|||

Hi, I met the same problem when I use report builder to design report from a report model. This report model was generated from a SSAS cube in my report server web site.

Initially, this report builder worked well. After I enabled "Allow user drill this report from other reports" in the report properties window, the error occured. I could not save or view the report.

The problem is the report model is in the report server. How may I get the XML file? And we need let end user to use Report Builder to design and publish reports by themselves. It is difficult to explain all of above operation to end user and let them edit XML file to fix the issue.

Obviously,it is really a critical issue. Please fix it asap.