Yes, I thought it has to be something like that. Others have reported the same and I know ppl. were looking into that. See
8.1.3 release thread.
If it wasn't for that it should have worked.
If you want/have to stay on 8.1.2 for the moment you can always update your data on client not based on promise or timeout, but generally (not only when you request a change) based on incomming changes in the foundset property type. You have to watch many of those anyway - I suspect just in case something changes on server for that foundset due to another form/component or another client that operates with the same data.
So for example:
- Code: Select all
$scope.$watch("model.foundset", function (newValue, oldValue) { ... }); // will let you know when foundset property value changed by reference
$scope.$watch("model.foundset.serverSize", function (newValue, oldValue) { ... }); // will let you know when foundset property value's serverSize changed
$scope.$watch("model.foundset.viewPort", function (newValue, oldValue) { ... }); // will let you know when foundset property value's viewPort has completely changed
$scope.$watch("model.foundset.viewPort.rows", function (newValue, oldValue) { ... }); // will let you know when foundset property value viewPort's rows has completely changed
$scope.$watchCollection("model.foundset.viewPort.rows", function (newValue, oldValue) { ... }); // will let you know when foundset property value's rows have changed (any item in the rows array was changed by reference/added/removed or the rows itself changed by reference)
$scope.$watch("model.foundset.viewPort.rows", function (newValue, oldValue) { ... }, true); // will let you know when foundset property value's rows have changed in depth (so any change at any level after rows will be reported)
$scope.$watchCollection("model.foundset.model.foundset.selectedRowIndexes", function (newValue, oldValue) { ... }); // will let you know when foundset property value's selection has changed
All these watches can be replaced with a listener on the foundset property in 8.2 (wiki page describes that), as the more data you watch for the slower the page will get + the listener details nicely the changes that happened.