bug in TileGrid.drop - tile is not added to destination TileGrid when dataFetchMode is "local"

[Isomorphic]

This should be resolved now for SmartClient 11.1+. The fix will be in the nightly builds dated 2022-11-14 and beyond.

[janusz]

Hi,

I have two TileGrids - databound to the same DS, so dragging tiles "moves" them updating one particular field using TileGrid.dropValues.
After dropping tile on the tileGrid2 transferRecords is run updating database, returning data.
ResultSets are correctly updated.
At some point tileGrid1.layoutTiles is called removing tile from source TileGrid.
However tileGrid2.layoutTiles is never called and as a result the tile is not added to the TileGrid despite new record being present in tileGrid2.data.

You can see it in showcase https://smartclient.com/smartclient/...ategorizeTiles by adding

dataFetchMode: "local"

to both tileGrids.

Best regards,
Janusz