Friday, December 4, 2020
5 changes
Enhancements to existing features
The Documents app test setup now uses shared test assets in a more consistent way. This is an internal quality improvement that helps keep automated tests easier to maintain without changing how users work with documents.
Original PR description
task-2411138
Deletion safeguards were moved to a safer standard mechanism across several Odoo apps. This helps keep business rules consistent when records are removed, reducing the risk of accidental data issues without changing day-to-day workflows.
Original PR description
With this commit, all instances of errors being raised inside `BaseModel.unlink` overrides are moved into methods decorated with `api.ondelete` which is safer. Linked to https://github.com/odoo/odoo/pull/58517
Miscellaneous changes
- Install Studio - Enable debug mode - Go to Apps - Activate Studio & go to Reports - Create an External Reports - Click on Company address The following error is raised: "Error: Invalid Prop 'value' in component 'CustomCheckbox'" "no_marker" option has "true" as value, which is not correctly parsed as True Boolean value. When options are parsed with py.js, true is treated like a "Name", unlike True & False that are "Constants". Therefore, the parsed value of true is {expr: "true",
Original PR description
- Install Studio
- Enable debug mode
- Go to Apps
- Activate Studio & go to Reports
- Create an External Reports
- Click on Company address
The following error is raised:
"Error: Invalid Prop 'value' in component 'CustomCheckbox'"
"no_marker" option has "true" as value, which is not correctly parsed as True Boolean value.
When options are parsed with py.js, true is treated like a "Name", unlike True & False that
are "Constants".
Therefore, the parsed value of true is {expr: "true", params: undefined, isField: true},
instead of expected boolean value "true".
Then, it raises an error during validation in owl.js (only in dev mode), because value for
"no_marker" is supposed to be a Boolean but it is an object instead.
opw-2393926
Forward-Port-Of: odoo/enterprise#15150When we have 0 statements on the journal, two connection buttons where displayed because the xpath were incorrect for that case. This commit fixes this behavior. Forward-Port-Of: odoo/enterprise#15070
Original PR description
When we have 0 statements on the journal, two connection buttons where displayed because the xpath were incorrect for that case. This commit fixes this behavior. Forward-Port-Of: odoo/enterprise#15070
When having a spanish company, it may be impossible to export the tax report (Mod 347). To reproduce the error: 1. Configure the company: - Set the country: Spain - Set the VAT (e.g. ESA12345674) 2. Create a customer - Set a spanish state (e.g. Alicante) - Remove the country 3. Invoice the customer - The amount must be greater than 3005.06€ 4. Save & Post 5. Accounting > Reporting > Tax Report (Mod 347) 6. Export (BOE), Generate BOE => An error occured OPW-2308155 Forw
Original PR description
When having a spanish company, it may be impossible to export the tax report (Mod 347). To reproduce the error: 1. Configure the company: - Set the country: Spain - Set the VAT (e.g. ESA12345674) 2. Create a customer - Set a spanish state (e.g. Alicante) - Remove the country 3. Invoice the customer - The amount must be greater than 3005.06€ 4. Save & Post 5. Accounting > Reporting > Tax Report (Mod 347) 6. Export (BOE), Generate BOE => An error occured OPW-2308155 Forward-Port-Of: odoo/enterprise#15126