Odata service Url executing after 8 seconds

[Former Member]

hi,

I have a odata service to fetch the data from NGW system written in the view.The service is executing after 8 seconds and meanwhile my view has already rendered and i am able to bind the textview only after my service gets executed.so this field remains blank for 8 seconds and data will appear only after the service gets loaded.

guys help me out to solve this issue!!

Thank you.

[Former Member · Accepted solution]

Hello Anil,

why you not use an Busy Indicator on the Textview and register an callback on success for the OData Request.

So the TextView is Busy till the OData-Request is completed.

Hope this helps!

Regards!

[scott_stefanich]

Hello Anil,

Is the service executing after eight seconds or does the service take eight seconds to execute?

The SCN blog NW Gateway: Tips & Tricks has a section Service Analysis and Debugging which contains tips for getting started with browser debugging, ABAP method timing & error analysis, and Gateway performance trace.

If you determine the performance issue is being caused in the back-end system, for example, a poorly performing RFC to which a web service operation is mapped, you perform run-time analysis with standard transactions such as SAT.

Regards,

Scott

[Former Member]

hi scott,

Service is taking 8 seconds to execute

thank you.

[Qualiture]

Can you post some code?

Normally there shouldn't be a problem at all; just set up the databinding in your view, and once the data has been loaded, the content is automatically updated with the retrieved values

[Qualiture]

Taking a step back: why is your service executing after 8 seconds? That's a pretty long waiting time...