ReportPortal
ReportPortal
Home | Profile | Register | Active Topics | Members | Search | FAQ
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 ReportPortal General Forum
 Report Portal General Issues
 Drillthrough Error message on filtered cube
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

toulon83

United Kingdom
7 Posts

Posted - 07/28/2005 :  05:44:26  Show Profile  Reply with Quote
Symptom:
Following error message when performing a drillthrough with Report Portal on a filtered Analysis Services cube

"Error Data Source Provider Error. Statement(s) could not be prepared, 42000, the column prefix "dbo.DIM_FLEET" does not match with a table name or alias name used in the query., 42000"

Sequence of events:
step 1 - i have created a cube RELIABCL390CUBE
step 2 - in Analysis services, i have added a Source Table filter as follows
"dbo"."DIM_FLEET"."Fleet_Name" = 'CL390
where DIM_FLEET is my dimension for the fleet names, here i want to limit my cube's data to hold only record for fleet "CL390"
step 3 - The cube processes happily in Analysis Service to process only records on fleet "CL390"
step 4 - When i come to develop my OLAP report on reportportal, i will only be able to drillthrough, if i include the DIM_FLEET as a filter and select "CL390"
on the portal!
If i try to drillthrough without adding the DIM_FLEET dim as a filter i get the error message seen above.

I believe this is because the MDX statement built by report portal doesn't include the DIM_FLEET in the statement (when the user doesn't filter on that dimension in reportportal), whereas the Analysis Services cube includes this DIM_FLEET as its filter by default.
The same problem happens if the filter is placed on the drillthrough window in Analysis Services instead of the Source Table filter.

You suggested in the past we use the following code
Drillthrough maxrows 2500 select {(" + sTupple + ")} on columns From [" +
sCube + "]"


But none of our users program in MDX. And we don't intend to teach them.

One "workaround would be base the Analysis cube on a SQL Server view and to implement the filtering there instead of inside Analysis Services. But this defeats the object of building the cube on our star schemas and adds some complexity to the whole process.

Any ideas ?

Rgds

Frederic

admin

1646 Posts

Posted - 07/28/2005 :  12:48:16  Show Profile  Reply with Quote
What happens what you drill-though in the Analysis Services Manager by double clicking?

http://www.databasejournal.com/features/mssql/article.php/10894_1963091_5

According to Google it is a somewhat common drill-though problem:

http://www.dbforumz.com/-HELP-MS-Support-DrillThrough-working-partition-bug-ftopict163526.html
http://www.technologyone.org/new-2986356-3728.html
http://www.all-usenet-archive.com/File.asp?service=36284

It would be nice if you could reproduce this problem using the Foodmart database…

Anyway, my suggestion is that you try OLAP actions instead of OLAP drill-though. The OLAP actions are somewhat more difficult to setup but they provide more control. The URL action can point to a Reporting Services or an SQL report.
Go to Top of Page

toulon83

United Kingdom
7 Posts

Posted - 08/11/2005 :  05:40:31  Show Profile  Reply with Quote
I am gonna cry of joy in a minute. Just managed to fix this one

- made sure the the dimension member on which i was filtering in the cube processing (Fleet_Name) was also selected in the cube drillthrough on Analysis Services

- this nows works perfectly (i.e: i can drillthrough on a filtered
Analysis Cube) via ReportPortal.

Good day

Frederic
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
ReportPortal © 2000-2002 Snitz Communications Go To Top Of Page