From 951768885ab9eea9c278d6b3aac3b96fe815d586 Mon Sep 17 00:00:00 2001 From: Ralf Becker Date: Fri, 5 Sep 2014 09:32:44 +0000 Subject: [PATCH] when refreshing some uids in a nextmatch, we need to send nextmatch filters too, as server-side will merge old version of filters from initial request data otherwise this can cause rows not to be returned because of different filters or search, or they are returned thought they should not --- phpgwapi/js/jsapi/egw_data.js | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/phpgwapi/js/jsapi/egw_data.js b/phpgwapi/js/jsapi/egw_data.js index 6eebc9f039..199304362c 100644 --- a/phpgwapi/js/jsapi/egw_data.js +++ b/phpgwapi/js/jsapi/egw_data.js @@ -811,7 +811,10 @@ egw.extend("data_storage", egw.MODULE_GLOBAL, function (_app, _wnd) { }; uid = uid.join("::"); - this.dataFetch(_execId, {'refresh':uid}, {}, nextmatchId,false, context, [uid]); + // need to send nextmatch filters too, as server-side will merge old version from request otherwise + this.dataFetch(_execId, {'refresh':uid}, registeredCallbacks[_uid][0].context.self._filters || {}, + nextmatchId, false, context, [uid]); + return true; } return false;