|
|
Re: report calling themselves [message #1277825 is a reply to message #1277819] |
Wed, 26 March 2014 14:12 |
Marc Arbour Messages: 36 Registered: March 2014 |
Member |
|
|
Thanks. It's not quite what I am looking for.
The thing is that in the first call, I want to see years, then months, then weeks and days, hours, minutes... Keeping the parameters as we go along.
- It's like the first time around on a report I need no parameter, grouping on years
- The second report call, I need to know for what year, grouping on month
- Then the year AND month, grouping on week
- etc
I forgot to mention that this needs to be from the interactivity option of a chart... Where there is only one category variable passed per click.
Is this at all possible?
[Updated on: Wed, 26 March 2014 16:51] Report message to a moderator
|
|
|
Re: report calling themselves [message #1278369 is a reply to message #1277825] |
Thu, 27 March 2014 08:32 |
donino donino Messages: 183 Registered: July 2011 |
Senior Member |
|
|
In interactivity of a chart we can define regular drillthrough actions, i don't see why you only have access to a category variable? May be you make use of "Invoke script" interactivity action, when we have to use "Hyperlink" action to define a drillthrough.
I think what you are trying to do is possible,for example we should declare:
- a report parameter per level (Year, Month, Week, Day,..), and set for each one a default value such -1 meaning "no filter".
- a report parameter to identifiy the current level, with a default value to 1 (Years)
- The dataset should be defined consequently, to ignore filters when the value of the relevant report parameter is -1. There are several options to achieve this, depending on the type of a datasource.
- Drillthrough actions should send :
---- all levels as report parameters
---- report parameter current level ++
Within drilltrhrough actions, for each level expression we need to test the current level to decide if we send:
- value from the dataset binding (if this level is the current level)
- current report parameter value of the level (else)
[Updated on: Thu, 27 March 2014 08:33] Report message to a moderator
|
|
|
|
|
|
|
|
|
|
|
Re: report calling themselves [message #1281147 is a reply to message #1279778] |
Mon, 31 March 2014 12:34 |
Marc Arbour Messages: 36 Registered: March 2014 |
Member |
|
|
donino donino wrote on Sat, 29 March 2014 03:56
That said, in this drillthrough action we should drill to the next level by sending an expression for "niveau" such:
params["niveau"].value+1;
HAHA! That is where I am stuck.
Where should this code go? In the script section of the base url script? in the mouseclick section? I can't code javascript in there because I now have a drill through action that prevents me.
[Updated on: Mon, 31 March 2014 12:36] Report message to a moderator
|
|
|
|
Re: report calling themselves [message #1281275 is a reply to message #1281263] |
Mon, 31 March 2014 16:39 |
donino donino Messages: 183 Registered: July 2011 |
Senior Member |
|
|
Marc Arbour wrote on Mon, 31 March 2014 12:17donino donino wrote on Sat, 29 March 2014 03:56
That said, in this drillthrough action we should drill to the next level by sending an expression for "niveau" such:
params["niveau"].value+1;
HAHA! That is where I am stuck.
Where should this code go? In the script section of the base url script? in the mouseclick section? I can't code javascript in there because I now have a drill through action that prevents me.
This code goes in the value expression of your drillthrough parameter "niveau". See this example, by editing or double-clicking a drillthrough parameter it displays an expression builder. Most of the time we just map it to a report parameter or a column binding, but we can also build complex expressions with loops, conditions, declare variables etc. In your case, just increment report parameter "niveau".
Let me know if it helps.
[Updated on: Mon, 31 March 2014 16:56] Report message to a moderator
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04939 seconds