Hi,
The situation here is :
- merge proposal for report_webkit have been ignored by the R&D team
until after 7.0
- R&D now accepts pull requests more willingly, but 8.0 is frozen so no
feature will go in
- pull requests for master will also be refused because report_wekbit is
removed
- OCA's ba
On 2014-09-21 04:35, Mario Arias wrote:
My suggestion is to use periods (or weeks, trimester, fiscal years,...)
for search. (only rare cases use the "DAY" as search criteria)
odoo must guarantee that users in different time zones product the same
results
if not - Odoo can't be used in multi-tim
Hi Ferdinand,
Problem is that any "period" that you define will suffer the same problem.
Datetimes at the very begining or end of any given period will be placed in
wrong one, accordingly to the timezone of the user and impact is bigger as
the timezone difference increases
How can you explain
+1 Mario
On Sep 22, 2014 9:08 AM, "Mario Arias" wrote:
> Hi Ferdinand,
>
> Problem is that any "period" that you define will suffer the same
> problem. Datetimes at the very begining or end of any given period will be
> placed in wrong one, accordingly to the timezone of the user and impact is
On 2014-09-22 05:38, Mario Arias wrote:
what I was trying to say:
if a user with time zone New York and another with Paris in their odoo
profile calls the same report for July 2014 it must return the same data
so if the "period_id" is stored in the data it's easy.
probably this is what "contex
5 matches
Mail list logo
