Followup questions/comments on the discussion here. Example page is here.
1. Clicking on the link is designed to invoke a server side action and refresh the master row from the server. All this works fine but looks like clicking on a column link in the master region is not sufficient to trigger the detail region to refresh, the detail region shows a message. Is this by design?
2. When a server side process initiated from the master region updates detail data, I was surprised to note that the detail region is not automatically refreshed. Even when I step off the affected master row and step back on it, the detail region displays old data. An explicit apex.region("detail").refresh() is needed to refresh data from the server.
Question: Does the APEX client-side model store all the detail data as we click through the master/detail grids?! For non-trivial datasets, wouldn't that cause the page to consume a ton of memory? When is this memory released?
3. At times, I have noticed that the detail region doesn't display any data (lazy loading is not enabled) even though the pagination shows Total: 15. At other times, there are console errors about method not found and such. An F5 page refresh clears everything up. This is a little troubling. Is this related to the resource usage in #2?
Is the IG master-detail component stable enough for Production use for critical data entry tasks? I would hate to be in a position where users spend couple of hours on a page, navigating and updating data in the master/detail region only to lose it all due to a quirk that requires a page reload.
@"John Snyders-Oracle" Your thoughts?
Thanks