Design Studio RRI Jump Target and Conditions

[leewlewis]

Hi all,

We are trying to use Design Studio 1.6.2.2 jump targets with BW queries and the receiver has a Top N condition. The problem we are seeing is the receiver opens as expected with the BW RSBBS entry and the Design Studio app assigned to the Server, but performance is horrible (45s). It seems the receiver query is executing without the conditions, then applying the condition after the components are loaded.

The same query and RRI target in bex analyzer returns the filtered results in ❤️ seconds.

Any ideas?

[leewlewis]

BTW, this is using the latest Adhoc template

[former_member265529]

Hi Lewis,

It is an expected behavior that design studio takes higher time compared to that of BEX analyzer as the RRI opens an addition excel file with target query in which both are in BW environment but in Design studio dashboard the complete dashboard will be loaded inclusive of all components in the dashboard from BO environment and query from BW environment.

For your question about that the codition is applied after the components are loaded, the condition on a measure acts similar to that of the default value filter in query designer that hides the irrelavent data from query.

So, the complete data set will be downloaded into the application, after complete dat is downloaded, the condition is applied to that data in dashboard. That's why it looks like the condition is applied after the components are loaded in dashboard

Thanks,

Poovarasan

[leewlewis]

This was resolved in 4.1 SP6. Now we simply have to maintain the entries in BW RSBBS for the sender query and list the receiver queries

The other key is that you must specify a CUID for the default RRI receiver app, in our case a Design Studio app using the adhoc template

[TammyPowlas]

What does profiling show? RSRT? Can you share screen shots?