I had similar issues with ngTable pagination and for those with the same problem the fix is to reference the ngTable $data
scope within the ng-repeat
directive (regardless of where/how you store the table data).
i.e. <tr ng-repeat="item in $data">
It appears that $defer.resolve()
will assign table data (i.e. selectedItems
) to the $data
scope to observe model mutations - which is tricky since referencing selectedItems
in ng-repeat
still displays the data (just without pagination!).