Skip to content

[MIG][9.0]product supplierinfo for customer#287

Closed
AaronHForgeFlow wants to merge 14 commits intoOCA:9.0from
ForgeFlow:9.0-mig-product_supplierinfo_for_customer
Closed

[MIG][9.0]product supplierinfo for customer#287
AaronHForgeFlow wants to merge 14 commits intoOCA:9.0from
ForgeFlow:9.0-mig-product_supplierinfo_for_customer

Conversation

@AaronHForgeFlow
Copy link
Contributor

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_code is deprecated in favor of this one.

@pedrobaeza pedrobaeza mentioned this pull request Jul 31, 2017
37 tasks
@AaronHForgeFlow AaronHForgeFlow force-pushed the 9.0-mig-product_supplierinfo_for_customer branch from d87d149 to b5c009a Compare July 31, 2017 15:18
@AaronHForgeFlow AaronHForgeFlow force-pushed the 9.0-mig-product_supplierinfo_for_customer branch from b5c009a to a63f460 Compare August 16, 2017 14:22
@AaronHForgeFlow AaronHForgeFlow force-pushed the 9.0-mig-product_supplierinfo_for_customer branch from ae5fd49 to 4f34d6f Compare September 8, 2017 15:27
@AaronHForgeFlow AaronHForgeFlow force-pushed the 9.0-mig-product_supplierinfo_for_customer branch from 4f34d6f to 2a03f30 Compare September 29, 2017 13:56
Copy link
Contributor

@MiquelRForgeFlow MiquelRForgeFlow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@pedrobaeza
Copy link
Member

Please squash together adjacent "OCA Transbot.." commits using https://github.com/OCA/maintainer-tools/wiki/Merge-commits-in-pull-requests

@MiquelRForgeFlow MiquelRForgeFlow force-pushed the 9.0-mig-product_supplierinfo_for_customer branch from 2a03f30 to 8e2e814 Compare June 28, 2018 15:39
@MiquelRForgeFlow
Copy link
Contributor

@pedrobaeza done

@pedrobaeza pedrobaeza added this to the 9.0 milestone Jun 28, 2018
Configuration
=============

For these prices to be used in sale prices calculations, you will have
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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>`_
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/8.0/9.0 You can use the new README by fragments system for avoiding to change this.

Copy link
Contributor

@MiquelRForgeFlow MiquelRForgeFlow Jun 29, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's not my PR. I will do fragments maybe in new modules for v11 or v12

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then the version should be corrected. You can apply the system the same for <v11. It's more comfortable IMO, but as you prefer.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Put * Tecnativa - Pedro M. Baeza instead

@@ -0,0 +1,5 @@
# -*- coding: utf-8 -*-
##############################################################################
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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, "
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can remove OdooMRP team

@MiquelRForgeFlow MiquelRForgeFlow force-pushed the 9.0-mig-product_supplierinfo_for_customer branch from e1a1ac8 to 9818e89 Compare June 29, 2018 10:43
@MiquelRForgeFlow
Copy link
Contributor

@elicoidal @oihane

Copy link

@elicoidal elicoidal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

some details

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
Copy link

@elicoidal elicoidal Jul 3, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why? in which case?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because it is not implemented in this PR. In v10 there's an option to create pricelist based on supplierinfo table but not here.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you add a simple explanation in the README?

"category": "Sales Management",
"license": 'AGPL-3',
"depends": [
"base",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you really need this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think so, because it's inheriting from res.partner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add copyright

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@@ -0,0 +1,128 @@
# Translation of Odoo Server.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the new weblate server you are not supposed to add .po files unless this is the first time.
Are you sure?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Transifex added this one, do we have to delete it?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure: @sbidoul ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 -*-
##############################################################################

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please use standard short headers

self.product.id, 1, partner=self.customer.id)
self.assertTrue(
price_unit.get(self.pricelist.id, False),
"Error: Price unit not found for customer")

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unit price

@AaronHForgeFlow AaronHForgeFlow force-pushed the 9.0-mig-product_supplierinfo_for_customer branch 2 times, most recently from a27f9af to 5321d85 Compare July 3, 2018 07:36
@MiquelRForgeFlow MiquelRForgeFlow force-pushed the 9.0-mig-product_supplierinfo_for_customer branch 2 times, most recently from 1694b1a to 2bab28e Compare July 3, 2018 10:28
@MiquelRForgeFlow
Copy link
Contributor

@elicoidal comments attended

@MiquelRForgeFlow MiquelRForgeFlow force-pushed the 9.0-mig-product_supplierinfo_for_customer branch from 2bab28e to 30607a5 Compare July 3, 2018 11:49
@MiquelRForgeFlow MiquelRForgeFlow force-pushed the 9.0-mig-product_supplierinfo_for_customer branch from 30607a5 to e1e6007 Compare July 3, 2018 11:59
@MiquelRForgeFlow MiquelRForgeFlow force-pushed the 9.0-mig-product_supplierinfo_for_customer branch from e1e6007 to 39de341 Compare July 3, 2018 14:22
@rafaelbn
Copy link
Member

rafaelbn commented Sep 4, 2019

So @aheficent @mreficent this could be merged? @pedrobaeza could you unblock this one?

@AaronHForgeFlow
Copy link
Contributor Author

@rafaelbn I am not sure, needs to be reviewed. I think the code here is not even to what it is in v10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.