Monday, February 12, 2024
11 changes · master
New functionality added to Odoo
The German DATEV export from the General Ledger now includes a VAT column for invoice-related entries. This helps accounting teams export more complete audit data, using the VAT number from the invoice address or its parent company when needed.
Original PR description
Before this commit, If "DATEV" was exported from the general ledger of the audit report. There is no VAT column present on the EXTF_accounting_entries.csv report. As a result, we added a VAT field to the invoice, and it's value is propagated from the VAT field defined on the invoice address. If the VAT number is not present on the invoice address, the commercial entity of the invoice address is used. We added the VAT column to the DATEV report of General Ledger. Steps to reproduce: 1. Assign the VAT number on the invoice address or it's parent customer. 2. Create an invoice for the customer, and the VAT is automatically propagated. 3. Accountancy—>Audit report—>General Ledger—> Export the DATEV report by clicking the "DATEV" button. 4. Based on the invoice, VAT is added to the EXTF accounting entries.csv report.
Enhancements to existing features
The Kenya accounting setup now separates VAT amounts into dedicated payable and receivable accounts for tax closing. This improves clarity in tax reporting and helps businesses track VAT owed to or recoverable from KRA more accurately.
Original PR description
In this pr I renamed account 220100 to KRA - VAT payable and created the new KRA - VAT receivable accounts. These accounts are now used as the Tax Payable and Tax Receivable accounts on all the tax groups task: 3725559 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
Point of Sale now shows the correct error details when an unexpected server communication error occurs. This helps staff and support teams understand what went wrong faster, reducing confusion during troubleshooting.
Original PR description
When an RPCError isn't handled in any PoS workflow, the system doesn't show the correct error message. This is because the registered error handle for uncaught RPCError isn't not properly discriminating the error. After this commit, proper error message, with the traceback is now shown in the error dialog.
Adds a setting to store mailing contacts with separate first and last name fields instead of one full name. This helps businesses capture cleaner subscriber data for newsletters and mailing lists, while keeping the existing single-name behavior by default.
Original PR description
[WIP] Alternative to group and context to configure visible columns of the list view using an override of the ListRenderer. Probably not the right solution but to be exhaustive. Add an option that…
[WIP] Alternative to group and context to configure visible columns of the list view using an override of the ListRenderer. Probably not the right solution but to be exhaustive. Add an option that allows to fill the contact name by providing a first and a last name instead of a single name. This option is not set by default. If the option is enabled, the name will automatically be filled when filling the first and the last name (as first name followed by last name). In the front-end, inserting the form subscription of the newsletter block, insert a form with a first name and last name field instead of a single name field. Unfortunately, when changing the option, it won't update the subscription form automatically (it must be done manually). A small inconvenient is that when updating first or last name, it will update the name so that the other part of the name is lost. To mitigate that problem, we have enabled the tracking on "name" so that any change on that field is logged in the chatter. If the option is not enabled, only names can be filled. First and last name will remain empty. Enabling the option won't convert name to first and last name; that works should be done manually (maybe using an export and an import). When not enabled, we make the first and last name fields not searchable so that they don't appears in custom filters or dynamic placeholder. Notes: - the first and last name are not alligned with the rest of the form because we have set them in a different group to force the correct tabindex. - the columns of the mailing contact list view change depending of the system parameter mass_mailing.split_contact_name. If it is true, the "name" column is replaced by a first and a last name column. Technically, it has been implemented through a context variable (name_is_split) as it is not possible to use the system parameter directly. For the list view, to avoid redefining actions with that context variable, we override the list renderer to configure the columns. Task-3597124
Mailing contacts can now optionally use separate first and last name fields, with the full name filled automatically when the option is enabled. This gives businesses more structured contact data for newsletters and mailing lists, while keeping the existing single-name behavior as the default.
Original PR description
Add an option that allows to fill the contact name by providing a first and a last name instead of a single name. This option is not set by default. If the option is enabled, the name will…
Add an option that allows to fill the contact name by providing a first and a last name instead of a single name. This option is not set by default. If the option is enabled, the name will automatically be filled when filling the first and the last name (as first name followed by last name). In the front-end, inserting the form subscription of the newsletter block, insert a form with a first name and last name field instead of a single name field. Unfortunately, when changing the option, it won't update the subscription form automatically (it must be done manually). A small inconvenient is that when updating first or last name, it will update the name so that the other part of the name is lost. To mitigate that problem, we have enabled the tracking on "name" so that any change on that field is logged in the chatter. If the option is not enabled, only names can be filled. First and last name will remain empty. Enabling the option won't convert name to first and last name; that works should be done manually (maybe using an export and an import). When not enabled, we make the first and last name fields not searchable so that they don't appears in custom filters or dynamic placeholder. Notes: - the first and last name are not alligned with the rest of the form because we have set them in a different group to force the correct tabindex. - the columns of the mailing contact list view change depending on the config setting group_mass_mailing_split_contact_name implemented with a group: mass_mailing.group_split_contact_name. If it is enabled, the "name" column is replaced by a first and a last name column. We have implemented it with a group because using a context variable and column_invisible implied to modify multiple action to pass that context variable which is prone to error. Task-3597124
Newsletter and mailing contacts can now be configured to capture first and last names separately instead of a single full name. This helps businesses collect cleaner contact data for personalization, while existing forms and contact records remain unchanged until updated manually.
Original PR description
[IMP] {website_}mass_mailing: split contact name into first and last name Add an option that allows to fill the contact name by providing a first and a last name instead of a single name. This option…
[IMP] {website_}mass_mailing: split contact name into first and last name
Add an option that allows to fill the contact name by providing a first and a
last name instead of a single name. This option is not set by default.
If the option is enabled, the name will automatically be filled when filling
the first and the last name (as first name followed by last name).
In the front-end, inserting the form subscription of the newsletter block,
insert a form with a first name and last name field instead of a single name
field. Unfortunately, when changing the option, it won't update the
subscription form automatically (it must be done manually).
A small inconvenient is that when updating first or last name, it will update
the name so that the other part of the name is lost. To mitigate that problem,
we have enabled the tracking on "name" so that any change on that field is
logged in the chatter.
If the option is not enabled, only names can be filled. First and last name
will remain empty. Enabling the option won't convert name to first and last
name; that works should be done manually (maybe using an export and an import).
When not enabled, we make the first and last name fields not searchable so that
they don't appears in custom filters or dynamic placeholder.
Notes:
- the first and last name are not alligned with the rest of the form because we
have set them in a different group to force the correct tabindex.
- the columns of the mailing contact list view change depending of the system
parameter mass_mailing.split_contact_name. If it is true, the "name" column is
replaced by a first and a last name column. Technically, it has been
implemented through a context variable (name_is_split) as it is not possible to
use the system parameter directly.
Task-3597124The preparation display now uses clearer action labels, replacing delete-style wording with "Done" so staff better understand when orders are completed. Links were also converted into better-aligned buttons, making the interface easier and more consistent to use during order preparation.
Original PR description
rename "delete" and "delete all" as "done" in preparation Display UI rename and move all links as buttons and correct alignement of those buttons tasks id : 3721465
WhatsApp templates can now each have their own action instead of sharing one action per related model. This makes it easier for users to launch the exact template they need, while action names and cleanup behavior are clearer when templates are removed, archived, or reset.
Original PR description
Before this commit: `Allow Multi` creates only a single `Window action` for templates associated with a single model even if there is more than one template. If 5 templates apply to the `contacts` module then only one `Window action` will be created for those 5 templates. After this commit: This commit adds functionality to create a `Window action` for every template. `Allow Multi` and `Disallow Multi` are renamed to `Add Action` and `Remove Action` respectively. While deleting or archiving a template, the respective `Window action` will be deleted. The confirmation box is also removed while removing action. Task - 3565219
Project start dates and deadlines are now visible directly in the task Gantt planning view, making it easier to see key project dates alongside tasks and milestones. Milestone markers are clearer when they overlap with project dates, and the view now only shows milestones relevant to the tasks currently displayed.
Original PR description
This commit displays the project dealine in the gantt view tasks. Until this commit, the milestones linked to the tasks of the project are displayed in the Gantt view with a diamond on the milestone deadline. When hovered, this diamond shows a pop-up indicating the milestone(s) and their states. This commit imitate this behavior to display the deadline of the project in the Gantt view with a red line and a pin on the relevant date. When one or multiple milestones occured on the same day as the deadline: - The diamond is replaced by a circle - The pop-over indicate, on top of the milestones name, that this is the project deadline. A small functionnal change introduced by this commit is that only milestones related to current tasks are displayed, instead of all milestones that relates to projects of the current tasks. task-2647326
The Planning app now groups the 'copy previous week' and 'auto plan' actions under a dropdown next to the publish button, making the main planning screen less cluttered. The layout is adjusted for both desktop and smaller screens so these actions remain accessible while improving visibility and usability.
Original PR description
This PR moves the 'copy previous week' and 'auto plan' buttons under a dropdown right next to the 'publish' button. These changes are done for the visibility of the planning app. Since it is impossible to prevent the gantt view's ControlPanel from putting all the available buttons in a dropdown on mobile view, the buttons had to be duplicated in the views. One set of buttons will appear only when display = xl and the other set of buttons will appear only when display < xl. The tour was also edited to add an extra step, since clicking on the 'copy previous week' button now requires you to click on the dropdown first. task-3613692
Fixed an issue in Point of Sale where using the “Search more” option during product search could trigger an error and leave the screen blank. This improves checkout reliability by keeping the product search flow usable for store staff.
Original PR description
ISSUE: ====== In the pos session product screen clicking on the Search more throws a traceback and completely blank the screen. Steps to Reproduced: ==================== Step 1: Open POS Step 2: Search product Step 3: Click on Search more button. Screen will blank and traceback occurred Reference Video: https://drive.google.com/file/d/1h5qka_BukOWP0kKfBi5pg4XrrgW0AyW8/view Traceback Log: https://pastebin.com/mzQ2dYyQ After this commit: ================== With this commit, the traceback will not appear when we trying to click on more in the pos session product screen.