Since Odoo 18, emails coming in to an alias creating account moves
(vendor bills) get rejected if they do not contain an attachment that
can be read by the system. This means that sending a plain email receipt
with no attachment bounces, when it would be nice to have a vendor bill
with the message in the chatter as a minimum.
This module checks for attachments and injects one, in the form of a
simple pdf containing the email header and contents, if there was no
attachment to begin with.
This should enable sending of a simple email and not having it bounce
due to there being no attachment.
Fixes an issue where creating the bills from the purchase orders could
create a bill with quantities vastly different from the received batch
quantities. This would happen when the purchase orders had lines with
quantities to invoice that did not match the receipt quantities.
Instead of creating the bills from the POs, we now generate the bill
and its line values directly from the quantities on the move lines
related to the batch.
Fixes a bug where sale orders with a partner_shipping_id not within the
same commercial entity as their partner_id could not have collect
carrier accounts set after being confirmed.
The issue stemmed from the fact that the sale order's recipient_id field
was being set to partner_id, while the created delivery order had
recipient_id set to its partner_id, which is the partner_shipping_id of
the sale order. In other words, the sale order recipient was incorrectly
set to the main partner instead of the shipping address.
This commit adds a test that was previously failing in this scenario. It
also properly sets the recipient_id on the transport selection wizard
and on sale orders themselves, fixing the issue.
- Default to zero is now functional
- Checkbox ("Picked" field) visible on move lines in the batch view
- Checking the Picked field marks the line green
- More tests written to validate functionality
purchase_customer_requisition:
* Make sure to check the validity (state + dates) on purchase
requisitions being selected for PO lines.
shipping_information_on_customer_invoice:
* Rework how the picking is selected, going through the sale lines
related to the invoice lines instead of the non-existing picking_id
field previously coded.
* Fixed an issue where accepting events from an external organizer would send emails
to the all event attendees upon synchronization.
* Corrected the data model for events where multiple Odoo users are attendees for the
same event. Now, only one event is created in Odoo, with all the attendees on the
same event. This conforms to Odoo's existing calendar event data model.
* Updated the setting of the organizer field (user_id) on the calendar events upon
synchronization. Previously, the organizer field was always set to the current user
whose events were being synchronized. Now, it is set based on the ORGANIZER parameter
of the iCalendar event, if present. If not present, it defaults to the current synchronizing
user. In the case that the organizer is external, the user_id field is left blank.
