I was wrong with the assumption that is is related to the datacollection itself. The problem seems to be the sync code. Please see the following example:
The datatable should show data with value == “b” only. Instead you will see the error message shown that the value property does not exist.
The source for the datatable is a DataCollection synced from another collection. The data stored in the master collection (“ca”) is fine but not the data on the synced collection (“cb”).
Yep, it is a side effect of some other fix. Sorry for the inconvenience. The correct build will be available on Monday.
Please beware that for TreeDataCollection the above issue will still occur ( during treestore sync, component will do the full copy of objects, which will result in loss of advanced object properties )