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.