Refreshing screen 2nd time after loading the data sources

[Former Member]

Hello Experts,

I created a Design Studio dashboard with 3 data sources (3 BEX Queries) and 3 components namely One Chart and two crosstab components.

To improve performance, I am loading DS_2 and DS_3 with script on doBackgroundProcessing() and calling this method On Startup of application.

I followed below scn link

http://scn.sap.com/community/businessobjects-design-studio/blog/2013/11/29/optimize-the-performance-...

Performance is improved little bit. When I run the dashboard, Chart will be displayed first, again after 4 secs the same chart gets refreshed automatically. The reason is by that time, DS_2 and DS_3 are loaded through doBackgroundProcessing().

Is there any way to avoid refreshing the first screen again(Chart component) once DS_2 and DS_3 are loaded? Chart component uses only DS_1.

I have searched for this information in SCN but I did not get any information on it.

Regards,

Satyam

[Former Member]

Hi,

Did you get a solution to this.

Coz I have Design Studio 1.6 and am facing same issue.

Queries are getting loaded twice whenever we use background processing.

And the weird part is queries load twice only when we use background processing. And once this has been used in our design studio application even I remove background processing the query loading twice issue remains.

Seems like a bug which once introduced does not seem to leave.

Regards,

Pragathi

[former_member189205]

hi,

i have steen this issue to start in my applications after upgrading from DS 1.4 to DS 1.5. Now we are in 1.6 where this behavior not occurs anymore.

[xjhacking]

Hi Gerben,

What is the exact version of Design Studio 1.6 that you are using? Are you on SP0 or on one of the later service packs?

Thanks,

Xavier

[Former Member]

Hi Satyam,

What about disabling data loading\updating animation in the additional properties of the chart component?

[Former Member]

Hi Satyam,

Do your data sources by any chance use optional or mandatory variables? Is merge prompts set to "true" (Application Properties)?

Thanks and Regards,

Eshwar Prasanna

[Former Member]

Hi Eashwar,

There are no variables. Merge Prompts is false.

Regards,

Hari

[xjhacking]

Has somebody found a solution for this issue, or at least an explanation of why this second time refresh is occurring?

Thanks,

Xavier

[Bob0001]

Data Sources which should be executed in parallel have to be assigned to different processing groups. All data sources in one group will be executed sequentially. Therefore your first approach putting all data sources into one group has only negative effects since they will be executed one after another and in an additional backend session.

For more details and examples of using processing groups read

and

[MustafaBensan]

Hi Satyam,

I am quite surprised that in the scenario you have described DS_1 is being reloaded after the completion of doBackgroundProcessing().  This behaviour should not occur, otherwise it would defeat the purpose of doBackgroundProcessing().  Can you confirm how you have verified that DS_1 is in fact reloaded?

Also, can you share the data source related scripts in your application and a screenshot of your dashboard?

Regards,

Mustafa.

[Former Member]

Hi Mustafa,

In my case DS_1 is not reloaded, but the initial screen is refreshing / flashing after few secs. I am assuming the dashboard is refreshing once the other two data sources (DS_2 and DS_3) are loaded in the back ground.

Regards,

Hari

[Former Member]

Hello Satya.

As said, Parallel Processing in one amazing fact that increases performance well and good and I would recommend the same option for your requirement.

And, For your case, I tried the same scenario which you'd mentioned in two methods.

( i ) Using dobackgroundProcessing() function as per your application.

( ii ) Using Parallel Execution thru Processing Group property as per Tammy's suggestion.

     When I executed it in method ( i ) ,

Now for method ( ii ) ,

I put all three datasources in the same Processing group(PROC_1) in the datasources' Properties Pane.

and on executing it,

Thus, I noticed a 25% increase in the performance, without blinking or a 2 time refreshing.

So i would suggest you try the same to avoid the second time refreshing and also to have a better performance of the dashboard on iPad.

This method is one of the ways to achieve the requirement this may not be the best or the easiest way.

Please correct me if I was wrong at any part of my answer.

Thanks,

Anoovendhan

[Former Member]

Hi Anoovendhan,

I totally agree with you and I also observed the similar behavior. When we use doBackgroundprocessing method, the initial loading of the dashboard is faster than parallel processing but the issue is dashboard screen will be refreshed 2^nd time also after loading remaining data sources.

Regards,

Satya

[Former Member]

Exactly! If the case was with the two crosstabs on a different tab, background processing would've been the best choice! But now, with all in the same tab, without compromising on performance and on the image, you can very well use the processing group.

Am sure by now you'd have got an idea as to where and when to use the processing group and not to.

Thanks.

Anoo

[TammyPowlas]

Hi - which version of Design Studio are you using?  Have you considered using parallel processing instead?  See Martin's blog

[Former Member]

Hi Tammy Powlas,

I am using Design Studio 1.5 and I tried Parallel processing. Basically I have two BEX queries (DS_1 and DS_2 are pointing to 1st BEX query and DS_3 pointing to 2nd BEX query).

I have tried it in two ways.

1st Method:

I have made DS_1 and DS_2 and DS_3 are part of Group1 (processing group) and run the dashboard.

2nd Method:

I have made DS_1 and DS_2 as Group1 and DS_3 as Group2 and run the dashboard.

I found that do background processing method is quicker by 2 secs  than parallel processing as I am loading 1st data source on startup and remaining are loading with do background processing.

My dashboard will run on iPad, so performance is important.

Regards,

Hari