Shulou(Shulou.com)05/31 Report--

This article mainly introduces "what is the reason of redundant round trip in SAP CRM Fiori application". In daily operation, I believe that many people have doubts about the cause of redundant round trip in SAP CRM Fiori application. The editor has consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubt of "what is the reason for SAP CRM Fiori application redundant round trip"! Next, please follow the editor to study!

Some colleagues complain that every time they save an appointment, there are three inexplicable read operations in addition to normal batch operations.

The callstack clearly shows that the three roundtrips are NOT issued by customer extension, or else the customer js file could be observed in the callstack.

Set a breakpoint on the top most callstack, h function. Check the content of e.target.data:

This is actually the batch request payload which could be observed in Chrome network tab:

This finding gives me more confidence that these roundtrips are issued by framework, not standard or customer application code.

So I just continue debugging until I reach this suspicious stack:

In line 1957, this.bRefreshAfterChange = true.

However, in our internal system (where everything works fine, there is no duplicate read operations), this.bRefreshAfterChange = false, which has suppressed the refresh operation. This is the reason why the read operation could not be found in my internal system, since they are not executed at all. But in customer system, _ isRefreshNeeded returns true, which leads to the execution of all subsequent read operations.

So why is this difference between two systems? In Chrome development tool, search the boolean variable name and we found one function setRefreshAfterChange defined for ODataModel. Just set a breakpoint in this method and re-launch the application in my internal system from beginning:

Breakpoint is triggered:

However, this line in customer system is missing, which is the root cause-our latest standard code didn't reach customer system.

This line is missing from the standard code on the faulty system, which I tried in local's Eclipse. If commented out, behavior will be able to reproduce the three redundant reads as on the faulty system.

At this point, the study on "what is the reason for redundant round trip in SAP CRM Fiori applications" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.