On calling removeSelectedData() on the ListGrid, the grid is not getting updated automatically when the record deletion succeeds

[preeti_kanyal]

Hi Isomorphic;
My SmartGWT version is: 'v11.0p_2017-02-11/PowerEdition Deployment (built 2017-02-11)'.
My application is using SmartGWT + Spring + Hibernate.

I am using a ListGrid(DataBound Component) for displaying the list of records in one of my application pages. Also, I am using ToolStrip class to create mixed set of controls. In that, i am adding a ToolStripButton as a member to that. In the addClickHandler() of this ToolStripButton, i am calling a method within which i am trying to delete the selected record from my ListGrid. I am trying to do something like this -

SC.ask("XYZ", new BooleanCallback()
{

@Override
public void execute(Boolean value) {

if (value != null && value)
{
grid.removeSelectedData();
}
}
});

On executing the above listed code, the selected record does get deleted from the database but on the page, the record still appears until i refresh the page. Once i refresh the page, the record from the Grid does get refreshed.
What i am trying to achieve is that as soon as i click the ToolStripButton, the pop up comes up and once i press the YES button on the pop up, the selected record from the grid should get deleted and that deleted record should not appear any more on the grid. The grid should get refreshed and updated automatically.

I am using the same logic and have implemented same functionality in one of my other grid as well & there the selected record is getting deleted from the grid as soon as i click the ToolStripButton and then press YES on the popup message & the screen is also getting refreshed with the deleted record no more appearing on the grid. The grid is getting updated automatically when the record deletion succeeds.


Can you please help me on this thing?

I have also attached the error message in a text file which i am getting in the browser console.

[Isomorphic]

We've fixed the error you showed, and you can test out the fix in builds dated September 12 and later.

Note that the error was caused by an attempt to log a warning about the comparators used to find matches - after you've updated, you'll see the proper warning message in the log.

This warning can imply a missing primary key field, complex primary-keys involving dates or other objects, or PKs involving multiple fields - so you'll probably need to show your DataSource if you still see issues.

[preeti_kanyal]

We are using the isomorphic-version 6.1-p20170701. Ideally, the fix for this should be available in the 6.1 build we are using. It is not possible for us to go back and check the fix on the latest build of 6.0. Please let us know when can we text the fix in the 6.1 build?

[Isomorphic]

?? You said you were using 6.0 in your initial post.

Regardless, whichever version you are using (6.0 or 6.1), you will need to update to the latest build of that version to pick up the fix.