clientOnly remove operation failed: unable to find matching record

[pratik.thaker]

Whenever I try to add some member to Canvas after the layout has been drawn, i am getting "clientOnly remove operation failed: unable to find matching record" popup message on my screen.

Please note that, the issue is coming after migrating from SmartGWT 2.5 to SmartGWT 3.1

Please provide solution for this.

[pratik.thaker]

Can anyone provide solution for this ?
Let me know if a standalone test case is required.

[deepak1891]

"clientOnly remove operation failed: unable to find matching record

I am getting this issue while dropping a record into list griid. Any solution for this?

[RC]

I got this when removing all records from a client-only data source, like this:

public void removeAllRecords() {
		Record[] records = this.getCacheData();
		for (Record record : records) {
			this.removeData(record);
		}
	}

Cause: The problem was that this method was invoked multiple times in a row from different parts of my code. I guess the records are removed asynchronously even for client-only data.

Solution: make sure the method is invoked only once.

In smartGWT3.1p.

[atul78]

ClientOnly: add operation failed for datasource, duplicate key in record

Can anyone provide solution for this ?
Let me know if a standalone test case is required.

Hi Pratik

Were you able to resolve this issue ? Even i m also facing same issue when i shifted from 2.5 to 3+ version.

Thanks
Atul

[rk9930]

Hello All,
I was facing same issue while removing record from ListGrid.
ListGrid.setSaveLocally(true) can be used to prevent this error. It will basically prevent the server call if you want to perform operation locally.

Thanks,
Roshan

[discipline19810128]

I got the same error.I will try rk9930,ListGrid.setSaveLocally(true),latter upload result.

[discipline19810128]

I think istGrid.setSaveLocally(true) not work.

[discipline19810128]

I hope some body can resolve this bug !~~~~~~~~~~~~~~~~~~~~~~~~~~~

[Isomorphic]

There is no test case showing a bug in this thread. If you believe there is a framework issue here, please put together a minimal, ready-to-run test case demonstrating the issue.