c2c-oerpscenario team mailing list archive
-
c2c-oerpscenario team
-
Mailing list archive
-
Message #24924
[Bug 783915] Re: Entries analysis: current year and period filters doesn't work in
Vishal,
thanks for testing this. You're right, with the gtk client things work
properly, and I was testing with the webclient. Maybe it's a webclient
bug?
--
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/783915
Title:
Entries analysis: current year and period filters doesn't work in
Status in OpenERP Modules (addons):
Incomplete
Bug description:
Observed in trunk and v6
To reproduce: create two account moves, one in the current period and
one in a previous one. Go to Account/Statistics/entries analysis and
try the "current year" and "current period" buttons. There is no
effect.
This has to do with stuff going on in
http://bazaar.launchpad.net/~openerp/openobject-addons/trunk/view/head:/account/report/account_entries_report_view.xml#L77
pressing the "this period" button sets che context, whereas in
http://bazaar.launchpad.net/~openerp/openobject-
addons/trunk/view/head:/account/report/account_entries_report.py#L83
not the context, but the domain search args are used.
Changing the xml to set the args instead of the context quickly fixes that, i.e. substituting line
http://bazaar.launchpad.net/~openerp/openobject-addons/trunk/view/head:/account/report/account_entries_report_view.xml#L77
with
domain="[('period_id','=','current_period')]"
Still, before proposing a merge, can someone come up with something
cleaner that writing strange stuff into "args" and then deleting it in
the 'search' method?
Thanks a lot
References