on 07-28-2014 2:03 PM
Hi,
We have used Dashboard Design tool to design Sales dashboard which has selector based on hierarchy LOV
Environment: BO 4.1 SP2 & BW 7.3 on HANA 1.7
Issue:
The overall query performance to fetch the actual dashboard data is quite satisfactory (within 2 secs), however the Query Prompt Selector takes long time to populate hierarchy LOV. (Hierarchy input variable in Bex query can only be binded to Query Prompt Selector). Unfortunately, each time the user selects a hierarchy node the dashboard executes a call to BW to retrieve the lower node.
In our scenario, there are 7 node levels and each node level has 5-20 values. When a user drills down from Node L1 to L2, a call is made to BW which takes 6-7 seconds to fetch the next level LOV. When they further wish to drill down from L2 to L3, another call is made to BW and so forth until the
lowest node.
Is there a way or work around to populate all the node level values in one go rather than making multiple calls. Due to this Query Prompt Selector behavior the performance has really hindered.
Regards,
Ritesh
Hi,
Why don't you create a Universe on top of BW data with LOVs and use query browsers to select the values.
There by it would be faster.
Arun
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ritesh,
I guess the way you are implementing the query in Dashboard is the optimum way.
If you go through BICS it will be slow.
There is a way where you can select during the creation of query in Dashboard how may levels to expand and display at the initial load. But again the initial load will be slow.
You could try that and see how it works for you.
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.