Hi All,
Need your help with the design approach to be followed in the following scenario :
We have 3 cascaded data radio button groups (Grandparent(Ex: G1), Parent (P1,P2,P3 etc)and Child(P1C1,P1C2,P2C1).
A bar graph which depicts month wise amount distribution for any of the entity selected above(At any point of time for only entity Ex: P1, P1C2 etc).
Approach followed :
We have put the graph in a data deck.
Each of the Radio button group is connected to data deck.
Master detail relationship is created between graph query and data deck query on Grandparent name, parent name and child name.
This approach is taking around 5 hrs to run the report.
If we delete the master detail relationship, then it takes around 15 mins to run. It could be a possibilty that huge data causing the performance issue.
Your suggestion in changing the design or making corrections in the existing approach would be highly appreciated.
Thanks in advance.
Quote from: bheemrao.walikar on 09 Mar 2015 03:47:40 AM
Hi All,
Need your help with the design approach to be followed in the following scenario :
We have 3 cascaded data radio button groups (Grandparent(Ex: G1), Parent (P1,P2,P3 etc)and Child(P1C1,P1C2,P2C1).
A bar graph which depicts month wise amount distribution for any of the entity selected above(At any point of time for only entity Ex: P1, P1C2 etc).
Approach followed :
We have put the graph in a data deck.
Each of the Radio button group is connected to data deck.
Master detail relationship is created between graph query and data deck query on Grandparent name, parent name and child name.
This approach is taking around 5 hrs to run the report.
If we delete the master detail relationship, then it takes around 15 mins to run. It could be a possibilty that huge data causing the performance issue.
Your suggestion in changing the design or making corrections in the existing approach would be highly appreciated.
Thanks in advance.
Hi,
If you're using 10.2.1 or later an alternative might be to use a bar visualization rather than a bar chart. The difference is that you can filter visualizations (unlike charts which are rendered as static png images). In theory you can dump all of your data decks and have all three data radio button groups filter the visualization directly. I'm guessing it will be a lot more efficient.
Cheers!
MF.
Thanks for your reply !
Yes we are using 10.2.1
Please note that the data items on which we want to filter the chart (Grandparent/Parent/Child) are not dragged on the chart rather chart is displaying data for amount against calendar month ?
Does this direct filtering of visualizations work even in the above mentioned case ?
Quote from: bheemrao.walikar on 09 Mar 2015 06:27:31 AM
Thanks for your reply !
Yes we are using 10.2.1
Please note that the data items on which we want to filter the chart (Grandparent/Parent/Child) are not dragged on the chart rather chart is displaying data for amount against calendar month ?
Does this direct filtering of visualizations work even in the above mentioned case ?
Yes - you just need to drag the items you want to filter on into the "Extra Categories" fields in the visualization. Once you have done this, they are available when setting up your variable to filter the visualization.
Cheers!
MF.
There is a change in requirement we are supposed to use line chart instead of bar chart. We have downloaded the vis files from IBM website. Will keep you posted for any progress we make.
Quote from: bheemrao.walikar on 11 Mar 2015 06:53:35 AM
There is a change in requirement we are supposed to use line chart instead of bar chart. We have downloaded the vis files from IBM website. Will keep you posted for any progress we make.
Same technique for any of the visualizations - you can right-click your current bar chart viz and convert it to another type without having to re-create from scratch :)
Cheers!
MF.
Thanks a lot MF ! That really helped ! :)