Daily updates from Odoo
Navigate
Branch
Monday, May 14, 2018
3 changes
Enhancements to existing features
This update makes date and time information easier and safer for Odoo to handle across accounting, HR, manufacturing, project, and resource planning workflows. It reduces the risk of timezone-related mistakes and simplifies future maintenance by standardizing how dates and datetimes are processed.
Original PR description
Task : https://www.odoo.com/web?#id=1834094&view_type=form&model=project.task&action=333&active_id=133&menu_id=4720 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
The cash flow statement now accounts for long-term loans and debt repayments in financing activities. This helps businesses get a more accurate view of cash movement when debt is issued or paid back, even when no income or expense account is involved.
Original PR description
Currently the cash flow statement, specifically the financing activities, relies and uses only the income and expense accounts to determine positive cash flow or negative cash flow. This is only partially correct because financing activities this also involves issuance of debt and payment of debt. Neither of these two items involve income or expense accounts. This leads to an incorrect cash flow statement in these specific cases. Related to task: https://www.odoo.com/web#id=31220&view_type=form&model=project.task&action=333&active_id=248&menu_id=4720
This fix updates Mexican e-invoicing tests so invoices and related refunds consistently use refreshed data. It reduces inconsistent test outcomes caused by cached information when records are created under different users.
Original PR description
Since invoices are created in the tests using a different user, they get its own new environment. Moreover, since they are under a test class, the cache is not automatically invalidated. Because of the above, when an invoice is created and a refund is created for that invoice, the invoice's values and the refund's values related to that invoice may differ, leading to inconsistencies depending on which one the information is retrieved from. This change ensures the cache for the refund to be refreshed before any operation is done, to ensure both the invoice and the refund refers to the same information.