Hi Jakov

We can't replicate the case. After calling
table.setClearOnRemove(true);
page.removeTable(id);/
the table should disappear and trailing updates should be ignored.

If we understand well, the problem happens to you when you call those lines while the previous table is still loading. We also tried simulating this case, but we didn't notice any update from the previous table mixed with updates from the second one.

We need more details on your case.

Are you using Web Client Library version 4.3?

If you, for testing, only issue
table.setClearOnRemove(true);
page.removeTable(id);/
without adding the new table, can you see the table complete loading?

Does the table loading take 30 seconds because of bandwidth restrictions? Or because of CPU overload on the client? Or because of slow data generation by the Data Adapter?

Can you exclude any issue in the Data Adapter, perhaps mixing updates for different items?