Pricelist flow isn't quite intuitive in its current state (and certainly not clean in a technical point of view).
# Improvements
1. Price Rules are opened in independent view from the product/product template.
2. Price rules of a product are still accessible in advanced pricelist mode.
* From a product.template : You see the rules on this product and on its variants
* From a product.product : You see the rules on the variant and on its template
3. UI refactorings
## Other changes
* Don't create a rule for all pricelist by default. If no rule is defined on a pricelist for a given product, it takes the sales price by default.
* Technical : multiple overly complicated pricelist settings are removed.
[Task 34788](https://www.odoo.com/web?#id=34788&action=333&active_id=1725&model=project.task&view_type=form&menu_id=4720)
closesodoo/odoo#35432
Signed-off-by: Damien Bouvy (dbo) <dbo@odoo.com>
Manage pricelists through a common configuration between sale and point_of_sale
Remove lots of technical fields
Improved Pricelist Flow
-----------------------
if pricelists enabled (product.group_product_pricelist), two modes are proposed:
* basic(default): pricelists enabled, but only with basic rules
* advanced: pricelists enabled, but with advanced rules (product.group_sale_pricelist)
When pricelists are enabled, we can always access them through the menu OR access their product-targeted rules from the products/templates views.
Prior to this commit, sale connectors (sale_amazon, sale_ebay, ...) had no dedicated section in sale's settings. If merged, this commit will allow to install such connectors in one click from the settings of the sale module.
task-19575
closesodoo/odoo#35120
Signed-off-by: Damien Bouvy (dbo) <dbo@odoo.com>
after this commit user can get a copy of the conversation with operator
task-2029660
closes#34620closesodoo/odoo#35083
Signed-off-by: Martin Geubelle (mge) <mge@openerp.com>
Before this commit it was no more possible to access website menu once
ecommerce installed, because the dashboard crashes with an
"Invalid field 'date_order' in leaf".
In the chatter composer, suggested partners were shown more than
necessary.
1. Create a new partner;
2. Open the chatter composer to send a message
(the new partner is suggested as a recipient);
3. Re-open the chatter composer
=> the partner is still suggested, but it is already a follower now!
Task-Id 2050102
closesodoo/odoo#35604
Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com>
Co-authored-by: jbm-odoo <jbm@odoo.com>
Modify tree view for MRP Production
Modify form view and tree view for Unbuild orders
Add group by for Bill of Materials
By default show line shart when opening MRP Production report
Modify view for Work Orders
Modify view for Work Centers
Modify view for Routings
Modify view for Maintenance Request
Modify view for Bill of Materials
task-2042304
closes - https://github.com/odoo/odoo/pull/35482
To reproduce the issue:
- configure a product with no_variant attributes
- select "grid" mode
- add this product to a sales order
- fill the grid
- confirm
-> Traceback
closesodoo/odoo#35701
Signed-off-by: Damien Bouvy (dbo) <dbo@odoo.com>
Before, we only had a public method that installed
the CoA for the current active company.
With the multi-company changes, it was not
possible anymore to install a module with a
demo company and then have the CoA installed
in that demo company correctly.
We changed that public method to be able to
put an extra optional parameter and shortened
its name to try_loading instead of
try_loading_for_current_company. The method that
it calls when there is no chart installed
is made private and renamed to _load.
closesodoo/odoo#35703
Signed-off-by: Quentin De Paoli (qdp) <qdp@openerp.com>
Introduces by #0679d0d54269ffe0664845e8e0bd1238110fd514 when you plan a
workorder, the corresponding workcenter will reserve a leave to avoid to
plan an another workorder in the same time slot.
But before this commit, when you unplan your workorder, the leave wasn't
unlinked, so the time slot stay reserved.
Now when a workorder is unlinked, its leave is too.
closesodoo/odoo#35003
Signed-off-by: Simon Lejeune (sle) <sle@openerp.com>
The purpose of this commit is to simplify the `mrp.production` model in
reducing the number of date field.
The following fields was kept:
- `date_planned_start`: the planned date for the beginning of the MO
- `date_planned_finished`: the planned date for the ending of the MO
- `date_start_wo`: the preferred date to start a Work Order in case
the MO will plan one.
- `date_deadline`: is only indicative and is automatically set when
the manufacturing order is needed for a sale order.
- `date_start` and `date_finished`: no changes.
Task #1935229
Co-authored-by: Whenrow <whe@odoo.com>
Add support for Six payment terminals.
TaskId: 1932416
Linked to odoo/enterprise#4435
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
closesodoo/odoo#33673
Signed-off-by: Quentin Lejeune (qle) <qle@odoo.com>
Simplify payment acquirer configuration.
Mostly screen changes, except the combination of website published/test mode in a single state button (disabled/test/enabled);
Rename ogone to ingenico in UI.
Slight changes in the message configurations.
Task 1832899
closesodoo/odoo#29064
Signed-off-by: Damien Bouvy (dbo) <dbo@odoo.com>
We will need to print Balance receipts for payment terminals from
Odoo's backend. The CSS and libraries need to be available there too.
TaskID: 1932416
Point of sale config have multiple fields that depends on the accounting
localisation, but when you create a new company, the default values for
the journals, accounts, etc are not yet created because there is no
chart of account installed for the company.
So to avoid user that create a pos config to manually create accounting
journals and accounts, we are warning them to install first an
accounting localisation that will create them all necessaries account
and journals.
TASK-ID: 2028954
closesodoo/odoo#35042
Signed-off-by: pimodoo <pimodoo@users.noreply.github.com>
For 10000 templates, of which around 1000 have variants, with 100 existing
attributes and 20 values for each:
- Displaying the /shop page takes 0.55s before the commit and 0.49s after.
That's a 60ms again, around 10% faster.
- The number of queries goes from 113 to 106.
- The specific line that is changed goes from 6.3% total request time down to
2.77%, so the line becomes 2.3 times faster.
closesodoo/odoo#34213
Signed-off-by: Sébastien Theys (seb) <seb@odoo.com>
Arnaud Baes