Odoo Addons (MOVED TO GITHUB)

[trunk] proposition to extend res.partner.address and base_contact

Bug #630672 reported by Ferdinand
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Confirmed
Wishlist
OpenERP R&D Addons Team 1

Bug Description

it is highly unlikely that a lead exists without a reference to a person / contact

hence it is a must to provide the following fields
* Partner Name = Company Name - exists
* Contact Name
* Contact First Name
* Contact Job (if base_contact is installed)

phone, fax, mobile exists

This will allow to "Create Partner" without changing data in partner form

Related branches

lp://staging/~openerp-commiter/openobject-addons/chricar_trunk_stock_SoPo_account_project_mrp_crm
qdp (OpenERP): Disapprove
Diff: 1053 lines (+338/-190)
17 files modified
account/account_invoice_view.xml (+56/-58)
account/account_view.xml (+9/-10)
account/project/project_view.xml (+4/-4)
account_tax_include/account_tax_include_view.xml (+1/-1)
mrp/mrp_view.xml (+8/-10)
procurement/procurement_view.xml (+3/-2)
project/project.py (+2/-2)
project/project_view.xml (+28/-31)
purchase/partner.py (+13/-5)
purchase/partner_view.xml (+14/-0)
purchase/purchase.py (+5/-3)
purchase/purchase_view.xml (+15/-12)
sale/sale.py (+96/-4)
sale/sale_view.xml (+21/-14)
sale/stock_view.xml (+16/-4)
sale_order_dates/sale_order_dates_view.xml (+11/-1)
stock/stock_view.xml (+36/-29)
Ferdinand (office-chricar)
summary: - [trunk] leads - it is mandatory to be able to records contact data
+ [trunk] leads - it is mandatory to be able to record contact data
Ferdinand (office-chricar)
Changed in openobject-addons:
status: New → Fix Committed
Revision history for this message
Antony Lesuisse (OpenERP) (al-openerp) wrote : Re: [trunk] leads - it is mandatory to be able to record contact data

crm.lead inherit res.partner.address, so they use exactly the same fields, and those fields are copied when creating the partner from the lead.

The merge proposal seems unrelated to crm.

Changed in openobject-addons:
status: Fix Committed → Invalid
Revision history for this message
Ferdinand (office-chricar) wrote :

what I am trying to say is that the Contact Name should be split in First / Last Name
then it is possible to fill the correct data fields when using base_contact ( which is sort of mandatory in many companies having a lot of b2b relations)

Changed in openobject-addons:
status: Invalid → New
Revision history for this message
Ferdinand (office-chricar) wrote :

another thing -
in our multicultural environment it would helpful to encode first name and last name ALWAYS seperately

Azazahmed Saiyed (OpenERP) (saz-openerp)
Changed in openobject-addons:
assignee: nobody → OpenERP R&D Addons Team 1 (openerp-dev-addons1)
importance: Undecided → Low
status: New → Confirmed
tfr (Openerp) (tfr)
Changed in openobject-addons:
importance: Low → Wishlist
Revision history for this message
Olivier Dony (Odoo) (odo-openerp) wrote :

note: keeping as wishlist, but out of scope for v6.0

summary: - [trunk] leads - it is mandatory to be able to record contact data
+ [trunk] proposition to extend res.partner.address and base_contact
Revision history for this message
Numérigraphe (numerigraphe) wrote :

Is this still an issue with the latest partner/address refactoring?
Lionel Sausin

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.