Expanding Partner fields and views

greno · Joined: 18 Aug 2007 Posts: 749

I would like to expand the fields available in the Partner for use in a specific business domain as well as the Partner Contacts. I also would like the new fields displayed in the views. I read through this post http://tinyerp.org/forum/topic4540.html?highlight=inherit%20partner which was helpful but still need some clarification. My goal is to not affect the ability to upgrade TinyERP so I am thinking that the best way to do this may be to create a custom module that would inherit and override the partner and partner contact adding the new fields and also creating new view files. Is this possible? And if so what exactly would need to be modified? Or is it better to just modify the original partner files under addons/base/res/partner?

Gerry

gegard · Joined: 21 Apr 2006 Posts: 1295 Location: Cambridge, UK

greno wrote:

... the best way to do this may be to create a custom module that would inherit and override the partner and partner contact adding the new fields and also creating new view files. Is this possible? And if so what exactly would need to be modified? ...

This is very much the best way. I've got some examples that I will look out and I'll post one here in the next day or so.

Regards,
Geoff
_________________
Regards,
Geoff
Seath Solutions Ltd

greno · Joined: 18 Aug 2007 Posts: 749

Hi Geoff,
Thanks, that would be great. I'm also debating whether to implement this using properties. Is there a way to group properties so that in a view you lookup one key and then all the related property fields get populated?

Gerry

knerz · Joined: 24 Oct 2006 Posts: 590

I agree with gegard. You can edit views using the inherit function and naming a position of the new view characteristics (e.g. "in", "after", "replace"). If you want to fully reset a view, the "replace" might be the right one. For a change in the partner_view.xml an possible custom_view.xml looks like this:

Code:

   <record model="ir.ui.view" id="view_partner_form_custom">
      <field name="name">res.partner.form.custom</field>
      <field name="model">res.partner</field>
      <field name="inherit_id" ref="base.view_partner_form" />
      <field name="type">form</field>
      <field name="arch" type="xml">
         <form string="Partners" position="replace">
               <form string="Partners">
======== your custom view tags ========
</form>
</form>
      </field>
   </record>

knerz

gegard · Joined: 21 Apr 2006 Posts: 1295 Location: Cambridge, UK

gegard wrote:

... I've got some examples that I will look out and I'll post one here in the next day or so. ...

A complete and very tiny example here: new module partner_extension in addons.

Regards,
Geoff

partner_extension/__init__.py

Code:

# <copyright and GPL license>
import partner_extension

partner_extension/__terp__.py

Code:

# <copyright>
{
"name" : "Partner Extension",
"depends" : ["partner"],
"init_xml" : [],
"demo_xml" : [],
"update_xml" : ["partner_extension_view.xml"],
"active": False,
"installable": True,
# ... and so on
}

partner_extension/partner_extension_view.xml

Code:

<terp>
<data>



<record model="ir.ui.view" id="view_partner_form1">
<field name="name">res.partner.form</field>
<field name="model">res.partner</field>
<field name="inherit_id" ref="base.view_partner_form" />
<field name="type">form</field>
<field name="arch" type="xml">
<separator string="Categories" position="before">
<separator string="Important Alerts for this Partner" colspan="4" />
<field name="alert" colspan="4" select="1" />
</separator>
</field>
</record>
</data>
</terp>

partner_extension/partner_extension.py

Code:

# <copyright>

from osv import fields, osv

##########
# Extend the partner to include an 'Alert' field
# The default view is also affected
#
class res_partner(osv.osv):
_name = 'res.partner'
_inherit = 'res.partner'
_columns = {
'alert' : fields.char('Alert', size=250),
}
res_partner()

_________________
Regards,
Geoff
Seath Solutions Ltd