Hi,
I came across a situation with the drill-through functionality.
I have a master report (dimensional report) with a prompt on the Year level. Now, I want to pass the year parameter (by defining drill-through definitions in the master report) of the master report into the child report (relational report). The child report contains the year query item (data type: integer). Upon defining the drill through definitions, the master report unable to pass the parameter value to the child report, eventually throwing an error (cannot pass the parameter values from OLAP to Relational).
Is there any way/approach by which I can pass the parameter into the child report ? Please advise.
Thanks
Quote from: Ravisha on 10 Aug 2016 06:58:35 PM
Hi,
I came across a situation with the drill-through functionality.
I have a master report (dimensional report) with a prompt on the Year level. Now, I want to pass the year parameter (by defining drill-through definitions in the master report) of the master report into the child report (relational report). The child report contains the year query item (data type: integer). Upon defining the drill through definitions, the master report unable to pass the parameter value to the child report, eventually throwing an error (cannot pass the parameter values from OLAP to Relational).
Is there any way/approach by which I can pass the parameter into the child report ? Please advise.
Thanks
Hi,
What sort of dimensional source does your first report use? Is it a PowerCube? If so, the Year parameter probably looks like "Between 2012-01-01 00:00:00.000 and 2012-12-31 23:59:59.999" when it gets passed. You're not passing a year, in fact, you're passing a representation of a Member Unique Name. Still based on the assumption your source is a PowerCube, the trick in the target report is to filter on a date (not on a year) using the expression [Your date item] in_range ?Your parameter?
If your source is not a Power Cube, post back and give us more information so we can help.
MF.
Thanks a lot for your prompt reply.
Yes, it is a power cube. I'm using a DateKey as a 'Source' and the Date (yyyy-mm-dd) as the 'Label' to generate the categories for the Time dimension.
I have resolved the issue by creating a child report based on a power cube rather than a relation model. I have created a dimension in the transformer model feasible for list reporting required for the child report. Therefore the drill-through is from OLAP to OLAP.
But your answer definitely makes sense! "In_Range" would certainly work. That was a genius resolution. ;D
I wonder how did you figure out that there is "and" in the MUN when it gets passed as a parameter ? Usually, the MUN has "-".
For example: [Sales Cube ].[Time].[Time].[Month]->:[PC].[@MEMBER].[20040101-20040131]
Thanks
Quote from: Ravisha on 11 Aug 2016 09:11:49 PM
Thanks a lot for your prompt reply.
Yes, it is a power cube. I'm using a DateKey as a 'Source' and the Date (yyyy-mm-dd) as the 'Label' to generate the categories for the Time dimension.
I have resolved the issue by creating a child report based on a power cube rather than a relation model. I have created a dimension in the transformer model feasible for list reporting required for the child report. Therefore the drill-through is from OLAP to OLAP.
But your answer definitely makes sense! "In_Range" would certainly work. That was a genius resolution. ;D
I wonder how did you figure out that there is "and" in the MUN when it gets passed as a parameter ? Usually, the MUN has "-".
For example: [Sales Cube ].[Time].[Time].[Month]->:[PC].[@MEMBER].[20040101-20040131]
Thanks
You can see what gets passed from the source report to the target report if you add a layout calculation to your target report, using the expression paramValue('your passed parameter') then drill through to it. :)
Cheers!
MF.
:o Interesting !
Thanks a lot :)