Difficult question. I am not really clear on what this all means. I took an example and dove straight in. If by 'oData model' you mean using a gateway service then no, I am not using an oData model. I am doing simple http calls to the back end to get the data and it comes back in JSON format.
In my example, my call to the backend comes back with the data because I can see it using the debugger. It is all sitting in oModel.oData and the part of the data relating to the masterview shows in the Master View. However, when I click an entry on the masterview the detail view opens but has no data in it.
I find this Fiori stuff very good for User Experience but showing great big lumps of data all at once in the master view is a bit unrealistic. Hence my problem. In the example that I started in this discussion show one item but then want to give the user the chance to bring in more data.
I have this as a hurdle that I have to get over because I have plans to initially show only the last 7 days of data in a masterview. When the user hits an icon I want to bring more data into the masterview or perhaps show data in the masterview within a date range. Problem is that when the icon is hit the data is collected from the backend correctly and shows in the masterview (and can be seen using debugger) but clicking on an entry in the masterview does not show the detail.
On the other hand when the application starts and on the initial load of the data the system goes through the component controller and all data in the masterview is also already 'somehow' bound into the detail view so that when the masterview is clicked it shows in the detail view.
There is something I need to use to get the master refreshed and bound to the detail in the same way as when the application initially starts.