Steps to reproduce:
-Create a first journal with a sequence
-Create a second journal with the same sequence
-Create a first SO, create the invoice for the fist journal and validate it
-Create a second SO, create the invoice for the second journal and validate it (the second invoice has the exact same name as the first one)
-Refund the second invoice (linked to the second SO)
-Go to the first SO => In the invoice button, you see 2 linked invoices (there is normally only one)
When searching the refunds corresponding to the invoices in function
_get_invoiced, the refund must take the journal of the invoice into account.
opw:684144
If you create a picking, with an owner, for qty x, and confirm it.
Next transfer x+1, it will raise a traceback 'cannot adapt res.partner'
Now, we pass the id, and not the browse record.
This commit closes#12978
* product.category: remove complete_name field as display_name can be used
where the field was used
* product.supplierinfo: remove computed qty field. This field originally
contained the min_qty computed into the product_uom. However commit
3c186c5807 broke that field without reason.
Since 2011 no one complained about this field being unnecessary, so let us
remove it.
* product.template: shorter and less spaghetti version of create_variant
method
* product_product._sellect_seller: fix use of default parameter in method
kwargs + use odoo standard datetime default value
A new API is introduced for price computing using pricelists. It is simplier
to use in most use cases, which is computing the product price in a given
pricelist. Old methods return dictionnaries and tuples, which are rarely
used in the code.
product_uom._compute_quantity is an ensure one multi method taking a browse
record as second paramter. It replaces _compute_qty and _compute_qty_obj
to have a single and standard computation method.
product_uom._compute_price() is now an ensure_one multi methods, taking
a browse record as second unit. This helps simplifying and unifying the
various calls and price computation methods.
Old price_get method is now replaced by price_compute and ready for migration.
Explicit parameters for unit of measure and currency have been added to ease
code understanding.
In case of event not all day, the timezone has an impact.
So if we search for date >= 2016-01-31 (00:00:00) and that the current timezone
is +5, we should search for date >= 2016-01-30 19:00:00.
date_to_str will drop the time.
This commit closes#12878
This commit closes#12971
When creating a new exchange rate, the default date is always the date
of the last server restart.
This is because `fields.Date.today() + ' 00:00:00'` is a fixed string
and the field is instanciated only at startup.
opw-684622
In some cases, the "Sales total(Revenue)" of the report is different
from the sum of the payments. To reproduce:
- create a product with a sale price of 1.00
- sell 3 times a quantity of 0.333 of this product
- the "Sales total(Revenue)" will be equal to 1.00, while the total of
payments is 0.99.
This is because in the report, we first sum all order lines, then we
perform a global rounding.
The solution is to use the total amount calculated for each order, which
is rounded at the appropriate time.
opw-682782
Now, if the first post of a user is marked as spam, we remove 10x the karma.
(by default 10 * -100= -1000)
That will avoid to the moderators too many click to 'kill' a spammer.
This commit is related to #12803
Before this commit, a user was able to post withtout limit new post.
They was added to the modarator queue.
Now we only support 1 post by user.
This commit is related to #12803
product.py and product_views.xml contained code related to several models.
This commit split those files to separate submodels :
* decimal_precision
* product_attribute: product.attribute, product.attribute.value,
product.attribute.line
* product_template: product.template
* product_uom: product.uom and product.uom.categ
* res_currency
Product now contains product.product model, along with some smaller
models (product.packaging, product.supplierinfo, product.category,
product.price.history)
The id of the user to browse has been omitted
during the below forward port revision:
95a2f8b121
We can see in the original revision that it was
correctly there:
cbb51610ee
This had as wrong side-effect to not display
views with a group set in the customize menu,
as it checked the groups of a null user browse
recordset.
opw-684326
Closes#12895
The module `sale_service` has been merged in the module
`sale_timesheet` in the revision
234f88a6af
We only remove the field from the view due
to the fact saas-11 is a stable. The field
has already been removed from the model
in newest releases (`saas-12`)
opw-682816
Rashik Kalathiya