Hi John,

First thank you for your helpful reply. I know it was a while ago, but I had given up on this and resorted to a page refresh to resolve the issue. However, I still have the problem since my rather complex app is under testing and this is one of the issues that has been raised.

I think I now understand a bit better the behaviour of the master-detail Interactive Grids. The key is in your reply - "... as long as you don't go back and forth between two master records...". (That is exactly what the users will do in this app and I can't control that.) I had seen that "detail" data isn't refreshed after the first time you select its master record. But what if another user (or in my case a background process) has added new detail records in the meantime? These are not displayed unless the detail data is refreshed by the user after the master record is selected.

The behaviour I need is that the detail data is refreshed every time its master record is selected. There are only ever a small number of records in the detail and it doesn't take too long. I think from your reply that what I need is to set the cache size to 0, but unfortunately, as you say, that isn't working. I have tried an explicit refresh every time the master record changes, but that really messes things up. After the first time, a javascript error appears - Cannot read property 'serverOffset' of null - and no details are displayed at all.

One of my server processes creates new records in the detail of the currently selected master record and this works fine. A normal region refresh displays the new data. The issue occurs with a process that copies "components" - the detail records - from one master item to one or more others, of course changing the master key and record id values of the component records. This is where only a page refresh really works, but of course it is a bit ugly and long-winded.

I'm fairly sure this cannot be an unusual requirement. In a multi-user situation wouldn't the user want to see any details added by someone else as soon as possible?

Again, thank you for your responses. I wouldn't have been able to achieve anything close to the company's requirements without your many blogs and explanations. They are actually very happy with the results, and one of the IG apps that has gone live - not this one - is a great success.  It is just this one issue which is bugging me.

Regards,

Richard

Ah, thank you. We are on Apex 19.1 and will shortly upgrade to 19.2.

I have put your code in and it does seem to work, in spite of the fact I get an error the first time a master record is selected. The error is Uncaught TypeError: Cannot read property 'length' of undefined.

I am thinking though that I may not need to get the length in this case because the master grid is set to single selection mode - only one record can be selected at a time. Or perhaps I can get the model explicitly rather than by using "this".

Anyway, it does look like this could be the answer!

Regards,

Richard

Hi John, here is the code I have got now on the selection change event. This executes without errors (bearing in mind that only one record can be selected at a time):

var g = apex.region("est").call("getViews","grid"),

sr = g.getSelectedRecords(),

rec,

masterModel = this.data.model;

if ( typeof sr[0] != "undefined" ) {

    // removed section which sets some page item values

    rec = sr[0];

    detailModelName = [apex.region("cost-items").call("getCurrentView").model.name, masterModel.getRecordId(rec)]; // change emp to be your detail static ID

    detailModel = apex.model.get(detailModelName);

    if ( detailModel ) {

        detailModel.clearData();

        apex.model.release(detailModelName); // don't forget to release any models you get

     }

}

This is working well in this situation. Your help is very much appreciated.

Thanks,

Richard