The function field selected_seller_id is removed and must be replaced
by a direct call to method `_select_seller`. This is more conventional
than the previous 'browse with context' way of doing.
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.
In v8, some fields were added for the product.pricelist formview by
template inheritance : after the active field. For v9, this active
field was moved in a button_box button (archive stat_button), so the
added fields (inheritance) landed in the stat_button too.
* Group with 6 columns caused problem when inside a dialog because of
wrong use of labels.
* Use o_row to align input followed by a '%' sign.
* col=6 group should not be in a parent group (moreover: this group was
alone in this parent group).
With the new pricelist system, a price should be specified for any
supplier, otherwise the price chosen for a PO is zero.
Also add unit price for existing PO
As the standard price on the product template changed towards the product variant,
we should also change the product price history to be by variant.
Also the inventory value calculated in the Stock Valuation report should be by variant.
The function field `volume` and `weight` on product.template were not
recomputed correctly.
The function field `standard_price` should not be stored as it's based
on a property field. Add a search function on it.
How great is it to get Odoo (almost) 9.0 (almost) translated?
Clean .tx/config file
Regenerate .pot files
Fetch current translations from Transifex (10% completion)
As the transporter interfaces will put a label on every package,
it is in handy to have a field with the list of the final packages
(and their weights) treated in the picking.
We give a weight for the products that are not in a package also(bulk).
We only put the weight on the package in the views.
The weights in the product form views should appear entirely or not in
product / product templates (only when only 1 variant)
(attrs was only on the field, not label, ...)
The digits= for the weights are not needed as there is a decimal precision
on these fields.
- Move product_product 'Deposit' from demo to data + make it a product_template
- Remove group_no_one on archive button for product_product and template
- Remove a commented import_pdb; pdb.set_trace()
- Add in the sales config 2 fields to edit the account and the taxes for the deposit product
- On the sale orders lines invoicing wizard, display the account and the taxes for the deposit product
instead of the product itself
- Set the product 'Deposit' as inactive to be hidden to the users
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
In 8.0, the products labels report is a non-customizable
xml report. Among others, the product name is displayed.
In saas-6, this report has been converted into
a customizable, qweb report. Unfortunately, the product
name has been forgotten during the convertion.
opw-648643
Martin Trigaux