[MIG][9.0]product supplierinfo for customer#287
[MIG][9.0]product supplierinfo for customer#287AaronHForgeFlow wants to merge 14 commits intoOCA:9.0from
Conversation
d87d149 to
b5c009a
Compare
b5c009a to
a63f460
Compare
ae5fd49 to
4f34d6f
Compare
4f34d6f to
2a03f30
Compare
|
Please squash together adjacent "OCA Transbot.." commits using https://github.com/OCA/maintainer-tools/wiki/Merge-commits-in-pull-requests |
…tomer: Complete README.
2a03f30 to
8e2e814
Compare
|
@pedrobaeza done |
| Configuration | ||
| ============= | ||
|
|
||
| For these prices to be used in sale prices calculations, you will have |
There was a problem hiding this comment.
Is this feature still there?
|
|
||
| The product code / product name specified for the customer can be reflected | ||
| on the sale orders using module `product_supplierinfo_for_customer_sale | ||
| <https://github.com/OCA/product-attribute/tree/8.0/product_supplierinfo_for_customer_sale>`_ |
There was a problem hiding this comment.
s/8.0/9.0 You can use the new README by fragments system for avoiding to change this.
There was a problem hiding this comment.
that's not my PR. I will do fragments maybe in new modules for v11 or v12
There was a problem hiding this comment.
Then the version should be corrected. You can apply the system the same for <v11. It's more comfortable IMO, but as you prefer.
There was a problem hiding this comment.
the version has been corrected.
And I am not comfortable with the fragments yet 🙄
| Contributors | ||
| ------------ | ||
| * Oihane Crucelaegui <oihanecrucelaegi@avanzosc.es> | ||
| * Pedro M. Baeza <pedro.baeza@serviciosbaeza.com> |
There was a problem hiding this comment.
Put * Tecnativa - Pedro M. Baeza instead
| @@ -0,0 +1,5 @@ | |||
| # -*- coding: utf-8 -*- | |||
| ############################################################################## | |||
There was a problem hiding this comment.
Change this old style header to the proper one
| { | ||
| "name": "Use product supplier info for customers too", | ||
| "version": "9.0.1.0.0", | ||
| "author": "OdooMRP team, " |
e1a1ac8 to
9818e89
Compare
product_multi_category/README.rst
Outdated
| Open ERP connector | ||
| **Note: The additional categories are only for classification and does | ||
| not affect other operations | ||
| * Note: This module was built generically but in focus of the Magento |
There was a problem hiding this comment.
Note:
* This module was built generically but in focus of the Magento
OpenERP connector
* The additional categories are only for classification and do
not affect other operations
|
|
||
| * Product prices through this method are only guaranteed on the standard sale | ||
| order workflow. Other custom flows maybe don't reflect the price. | ||
| * The minimum quantity will not also be applied on sale orders. |
There was a problem hiding this comment.
Because it is not implemented in this PR. In v10 there's an option to create pricelist based on supplierinfo table but not here.
There was a problem hiding this comment.
Could you add a simple explanation in the README?
| "category": "Sales Management", | ||
| "license": 'AGPL-3', | ||
| "depends": [ | ||
| "base", |
There was a problem hiding this comment.
I think so, because it's inheriting from res.partner
There was a problem hiding this comment.
product is already adding the dependency IMO.
Not hurting but I usually prefer to have the strictly necessary
| @@ -0,0 +1,12 @@ | |||
| <?xml version="1.0" encoding="UTF-8"?> | |||
| <openerp> | |||
| @@ -0,0 +1,128 @@ | |||
| # Translation of Odoo Server. | |||
There was a problem hiding this comment.
With the new weblate server you are not supposed to add .po files unless this is the first time.
Are you sure?
There was a problem hiding this comment.
Transifex added this one, do we have to delete it?
There was a problem hiding this comment.
Since it's a migration, it also the first time the .po file appear on this branch. So you can keep them, there is no risk of conflict.
| @@ -0,0 +1,7 @@ | |||
| # -*- coding: utf-8 -*- | |||
| ############################################################################## | |||
| self.product.id, 1, partner=self.customer.id) | ||
| self.assertTrue( | ||
| price_unit.get(self.pricelist.id, False), | ||
| "Error: Price unit not found for customer") |
a27f9af to
5321d85
Compare
1694b1a to
2bab28e
Compare
|
@elicoidal comments attended |
2bab28e to
30607a5
Compare
30607a5 to
e1e6007
Compare
e1e6007 to
39de341
Compare
|
So @aheficent @mreficent this could be merged? @pedrobaeza could you unblock this one? |
|
@rafaelbn I am not sure, needs to be reviewed. I think the code here is not even to what it is in v10 |
Use product supplier info also for customers
This modules allows to use supplier info structure, available in Inventory tab of the product form, also for defining customer information, allowing to define prices per customer and product.
No extra features are added in this Pull Request.
As discussed here: #236 The module
product_customer_codeis deprecated in favor of this one.