Possible Bug related to "neverDropUpdatedRows" for Resultset

Hello, I think I've found a bug related to the neverDropUpdatedRows property for resultset. I've recreated in your Feature Explorer. Please advise.

Go to:
http://www.smartclient.com/docs/6.5/a/system/reference/SmartClient_Explorer.html#enterNewRows

Then, use the following code:

isc.ListGrid.create({
    ID: "countryList",
    width:500, height:224, alternateRecordStyles:true, showAllRecords:true, cellHeight:22,
    // use server-side dataSource so edits are retained across page transitions
    dataSource: countryDS,
    // display a subset of fields from the datasource
    fields:[
        {name:"countryName"},
        {name:"continent"},
        {name:"member_g8"},
        {name:"population", 
         formatCellValue:"isc.Format.toUSString(parseInt(value))"},
        {name:"independence"}
    ],
    dataProperties: {
      neverDropUpdatedRows:true
    },
    canEdit: true,
    editEvent: "click",
    listEndEditAction: "next"
})

countryList.fetchData({continent:'Europe'});

isc.ListGrid.create({
    top:250,
    ID: "countryList2",
    width:500, height:224, alternateRecordStyles:true, showAllRecords:true, cellHeight:22,
    // use server-side dataSource so edits are retained across page transitions
    dataSource: countryDS,
    // display a subset of fields from the datasource
    fields:[
        {name:"countryName"},
        {name:"continent"},
        {name:"member_g8"},
        {name:"population", 
         formatCellValue:"isc.Format.toUSString(parseInt(value))"},
        {name:"independence"}
    ],    canEdit: true,
    editEvent: "click",
    listEndEditAction: "next"
})

countryList2.fetchData({continent:'Asia'});

Now, edit the population of the first record in the second grid and click to another row to save it. It will then show up in the first grid even though the first grid is filtered by the continent of Europe. This is because of the "neverDropUpdatedRows" property on the first grid. It shouldn't be showing up in the first grid in this scenario because of the criteria applied to the first grid, right?

Hi there, I understand you may still be investigating this issue. But, can you confirm this is indeed a bug?

[Isomorphic]

Yep, this looks like a bug. Thanks for the concise test case. We'll get this fixed for the next release.