We introduce a new field on supplierinfo: product_id. Thanks to this
field, the vendor information which will be used in a purchase order can
be specific to the product variant.
Now that most refactoring has been merged
It is better to have red a great work of another culture in translation than never to have read it at all.
― Henry Gratton Doyle
The res_partner squash has added several information to the res_partner_2
Now the is a purchase order for which he's the supplier. In that case, the
planned date on the purchase order line is influenced by the planned date
of the other purchase orders where this partner is the supplier.
Here we create a new res_partner for this test who has no purchase orders related
In that case, the planned date will always the date planned in the calendar at the
basis, which is 3.
NB : Some tests have been modified.
One assert statement in orderpoint_calendar.yml has been modified,
but the change is legit has no python method has been modified at all
- Preserved explicit 3rd-party copyright notices
- Explicit boilerplate should not be necessary - copyright law applies
automatically in all countries thanks to Berne Convention + WTO rules,
and a reference to the applicable license is clear enough.
[FIX] Message_post happens one by one and add test for next delivery date
[IMP] Add float_compare in orderpoint confirm
[FIX] Typo
[FIX] Use next_by_code instead of deprecated get
Update views for date_to on calendars
[IMP] Will add a date_to in the calendar attendance and date_from and date_to should be applied/ check backwards also
[IMP] get_attendance_for_weekday will pass date instead of weekday
[IMP] should assign correct procurements in run
Nicolas Martinelli