I had the same problem and ended up doing a sort / filter / paging manually:
var app = angular.module("myApp", ["ngTable", "ngResource", "ngTableDemoFakeBackend"]); (function() { app.controller("demoController", demoController); demoController.$inject = ["NgTableParams", "$resource", "$filter"]; function demoController(NgTableParams, $resource, $filter) { //var Api = $resource("/data"); var Api = $resource("https://jsonplaceholder.typicode.com/posts", {}, { // Let make the `query()` method cancellable query: {method: 'get', isArray: true, cancellable: true} }); this.tableParams = new NgTableParams({ count: 5 }, { getData: function(params) { // ajax request to api return Api.query().$promise.then(function(data) { params.total(data.length); // recal. page nav controls var filteredData = params.filter().id ? $filter('filter')(data, params.filter()) : data; var orderedData = params.sorting() ? $filter('orderBy')(filteredData, params.orderBy()) : data; var page = orderedData.slice((params.page() - 1) * params.count(), params.page() * params.count()); return page; }); } }); } })();
The disadvantage of this approach is that you use filtering, the more columns you add, the more checks you need to do, because how it works, when you clear the filter, it will not set this object to undefined. It will create an object like this:
{ id: null }
This means that you cannot use params.filter() on this line:
var filteredData = params.filter().id ? $filter('filter')(data, params.filter()) : data;
Yaser source share