SAP UI5裡Batch操作和Read操作的區別

i042416發表於2020-09-09

I would like to share with you my story today about fighting with one customer incident. We can make changes on Appointment and click save button:


SAP UI5裡Batch操作和Read操作的區別


There is a batch operation observed in Chrome network tab to update appointment as expected. However, why every time there are three subsequent appointment read roundtrips?


SAP UI5裡Batch操作和Read操作的區別


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.


SAP UI5裡Batch操作和Read操作的區別


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


SAP UI5裡Batch操作和Read操作的區別


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


SAP UI5裡Batch操作和Read操作的區別


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:


SAP UI5裡Batch操作和Read操作的區別


in line 1957, this.bRefreshAfterChange = true.


SAP UI5裡Batch操作和Read操作的區別


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.


SAP UI5裡Batch操作和Read操作的區別


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:


SAP UI5裡Batch操作和Read操作的區別


Breakpoint is triggered:


SAP UI5裡Batch操作和Read操作的區別


However, this line in customer system is missing, which is the root cause – our latest standard code didn’t reach customer system. After I found the root cause, I search in SCN to check whether there are other poor guy which had encountered the same issue with me, and actually I found one: scn.sap.com/thread/3724


SAP UI5裡Batch操作和Read操作的區別


If I read this thread several months earlier, I would save my hours’ debugging today.


SAP UI5裡Batch操作和Read操作的區別


要獲取更多Jerry的原創文章,請關注公眾號"汪子熙":

SAP UI5裡Batch操作和Read操作的區別


來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/24475491/viewspace-2718379/,如需轉載,請註明出處,否則將追究法律責任。

相關文章