Merge lp:~openerp-dev/openobject-addons/7.0-opw-596732-msh into lp:openobject-addons

[Mohammed Shekha(Open ERP)]

Hello,

Fixed the issue of add to dashboard and evaluated domain, while adding dashboard we should add row domain as it is and should evaluate it when dashboard action is loaded otherwise dynamic domain value like context.today etc will not work, instead evaluated date is applied and dashboard will not give proper result.

Demo:- Open any tree view which has Filter based on date/relative_delta/today, filter your data using that date, say for example I have filter like ('date_action','<=', (context_today() + relativedelta(days=7)).strftime('%Y-%m-%d’)) so when I filter data with this filter and then add this view into dashboard then next day that view will give wrong result.

Reason: While Adding view into dashbaord, evaluated domain and context stored in the dashboard action, domain and context should be stored as it is and when action is loaded at that time action domain and context should be evaluated.

Thanks.

Unmerged revisions

9856. By Mohammed Shekha(OpenERP)<email address hidden> on 2014-02-27

[FIX]Re-fixed the issue of add to dashboard and evaluated domain, while adding dashboard we should add row domain as it is and should evaluate it when dashboard action is loaded otherwise dynamic domain value like context.today etc will not work, instead evaluated date is applied and dashboard will not give proper result.

=== modified file 'board/static/src/js/dashboard.js'
--- board/static/src/js/dashboard.js	2013-10-27 12:31:04 +0000
+++ board/static/src/js/dashboard.js	2014-03-20 05:02:17 +0000
@@ -177,6 +177,11 @@
             view_mode = action_attrs.view_mode;
 
         // evaluate action_attrs context and domain
+
+        var comp_domain = new instance.web.CompoundDomain();
+        _.each(eval(action_attrs.domain), comp_domain.add, comp_domain);
+        action_attrs.domain = comp_domain.eval();
+
         action_attrs.context_string = action_attrs.context;
         action_attrs.context = instance.web.pyeval.eval(
             'context', action_attrs.context || {});
@@ -377,10 +382,21 @@
         }
         var data = getParent.build_search_data();
         var context = new instance.web.CompoundContext(getParent.dataset.get_context() || []);
-        var domain = new instance.web.CompoundDomain(getParent.dataset.get_domain() || []);
+        //used dataset.domain instead of dataset.get_domain, because model domain will be evaluated domain
+        //We need unevaluated domain of action as well as search build
+        var domain = new instance.web.CompoundDomain(getParent.dataset.domain || []);
         _.each(data.contexts, context.add, context);
         _.each(data.domains, domain.add, domain);
 
+        var dd = [];
+        _(domain.__domains).each(function(dom) {
+            if (dom instanceof instance.web.CompoundDomain) {
+                dd.push(instance.web.pyeval.eval('domain', dom));
+            } else if (dom.length) {
+                dd.push(dom);
+            }
+        });
+
         context.add({
             group_by: instance.web.pyeval.eval('groupbys', data.groupbys || [])
         });
@@ -393,13 +409,12 @@
         }
         // TODO: replace this 6.1 workaround by attribute on <action/>
         c.dashboard_merge_domains_contexts = false;
-        var d = instance.web.pyeval.eval('domain', domain);
 
         this.rpc('/board/add_to_dashboard', {
             menu_id: this.$el.find("select").val(),
             action_id: view_parent.action.id,
             context_to_save: c,
-            domain: d,
+            domain: JSON.stringify(dd),
             view_mode: view_parent.active_view,
             name: this.$el.find("input").val()
         }).done(function(r) {