Parameter sould only affect rows, not the data. Is this possible?
I have a report based on a SSAS 2008 cube. The report contains 3 parameters and a tablix. The first two parameters are normal parameters. But the third is a special one. And i can't get it to work properly. I will explain what i want:
Default te parameters react with the data and rows. If you select year, then you see the
data and rows for that year. But my third parameter should only interact with the rows and
NOT the data. I want to use it to create an subset so the user sees her/his rows, but the data should not change based on the parameter.
i.e.
Year
2011
Department
All
Month
5
Product
Sales
Apple
100
Bananna
150
Orange
200
Lemon
150
Pineapple
200
Year
2011
Department
East
Month
5
Product
Sales
Apple
100
Bananna
150
Orange
200
Only the products change (products are shown only sold by west based on salesdata). But the sales stay the same (including the sales from the other departments).
Is this possible?
Thank you for the help.
J2.0
June 28th, 2011 11:01am
Hi ,
Create 2 dataset and 2 tablix and Make these things independent.
Rakesh M J
Dont forget to mark it as Answered if found useful
MCTS,MCITP,MCSS
http://mycubeandreports.blogspot.com/
Free Windows Admin Tool Kit Click here and download it now
June 28th, 2011 11:08am
Thanks for the quick reply.
I know how to make tablixes independent. The example above is in one tablix showing how it sould be affected by the parameter.
June 28th, 2011 11:47am
Hi,
You can also use the Report level Filter rather than the Datsource Level.Rakesh M J
Dont forget to mark it as Answered if found useful
MCTS,MCITP,MCSS
http://mycubeandreports.blogspot.com/
Free Windows Admin Tool Kit Click here and download it now
June 28th, 2011 12:08pm
When i use a dataset filter, it still filters the data and not ONLY the rows.
June 28th, 2011 1:02pm
I don't understand what exactly you mean by filtering rows. Rows contain data, filtering rows filters the data.
Do you perhaps want to filter certain fields in a row?
Free Windows Admin Tool Kit Click here and download it now
June 28th, 2011 1:06pm
If you use a tablix, you have a row, column and data field.
Row = dimension (in the example above product) and data is de measure.
I want to filter the rows not affecting the measure. As in the example. Normaly if you use a filter, it also affects de measure showing only the sales for East in the example. I want to view the products that East sales, but the measure needs to be
overall (meaning all departments).
June 28th, 2011 1:59pm
Hi J2.0,
Does Product <--->Region Many to Many Relation ?
Create a table which links between Product and Region and select only those Products which are sold in the Given Region (EAST,WEST...)
Rakesh M J
Dont forget to mark it as Answered if found useful
MCTS,MCITP,MCSS
http://mycubeandreports.blogspot.com/
Free Windows Admin Tool Kit Click here and download it now
June 28th, 2011 2:03pm
Hi J2.0,
what you can do is:
1) Create a dataset DataSet1 containing data of all the products with their overall measures data (as you required in the reports).
2) Create another dataset DataSet2 with the list of all products and specify the parameter here (on the basis of which you want to filter the products).
Now, in the tablix use Lookup() function (works only in SQL server 2008).
= Lookup(Field!Product.value,Field!Product.value, Measure1, "DataSet3")
Note: Tablix's DataSetName property should be set to DataSet3
Regards
Manoj
June 28th, 2011 2:09pm
First off, thanks for all the replies!
Second, i think what Manoj discribes is what i need. I am affraid that the lookupfunctie is restricted to r2. We are still running 2008, but we are going to upgrade. I don't know when do...
Rakesh, there is no real relation. Only that there is sales. So there is products and sales and there is department and sales. But there is no link between department and products. The link is created if a product is ever sold by a department. In other
words if there is a measure.
Free Windows Admin Tool Kit Click here and download it now
June 28th, 2011 2:46pm
I tried the solution Manoj sugested on a testdatabase installed with r2 and it worked like a charm. I'm going to set this topic to answered. It did not solve my problem
yet, but since we're going to upgrade, I find it more sensible to wait and then fix the problem, then to create a complex workaround.
June 29th, 2011 3:58am