Hi All,
Here's a scenario for you...Go ahead and start up the local Web IDE and create yourself one of the template Fiori/Mobile UI5 projects. Hook it up to Northwind or a Gateway service. Now unplug your network, and press Run and see how the lack of connection is handled...
As far as I can tell, I can't see any guides or examples anywhere explaining best practice for handling errors when doing XML OData binding of an Entity Set and the screen usually, just like the template example above, appears and just shows no results and maybe a busy indicator.
It is possible to hook everything in like follows:
var oModel = new sap.ui.model.odata.ODataModel(sServiceUrl, true);
oModel.attachRequestFailed(this.myHandleRequestFailed);
But even this doesn't seem to trap all errors like above.
Hence my question: what is the correct/recommended way of doing this, and does this allow you have a more fine grained approach, or at least a per view approach? Obviously when you are JavaScript doing OData updates, you can have success and failure handlers, but the automated binding seems to be carefree in it's handling of errors from what I can tell.
Help??? Our enterprise code needs answers to these types of questions on SCN (I did try to find an answer on SCN - though will look at StackOverflow now just to be sure).
Cheers,
Matt
Message was edited by: Margot Wollny