Base_contact: Missing Fields in new design [6.1]

Bug #923440 reported by Etienne Hirt on 2012-01-29
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Invalid
Wishlist
OpenERP R&D Addons Team 1

Bug Description

Thanks for the new design of base_contact. It fits well into the other
modules.

I appreciate the approach that the data from "location" and contact is
copied and stored thus accessible in the address itself efficiently.

I wonder however, that there are no triggers to update the location items or the contact items in case one of them changes (not the assigment!). Does 6.1 require no trigger for update as in 6.0:
(store={'model': (function, [Params],..)} ?

I'm missing the status fields of an adress as was available in the old design (up to 6.0):

'date_start': fields.date('Date Start',help="Start date of job(Joining Date)"),
'date_stop': fields.date('Date Stop', help="Last date of job"),
'state': fields.selection([('past', 'Past'),('current', 'Current')], \
                                'State', required=True, help="Status of Address"),

Further in order to select the main employer/function the following field was used:
 'sequence_partner': fields.integer('Partner Seq.',help='Order of importance\
                 of this job title in the list of job title of the linked partner'),

and for the order in contacts the following field was used:
'sequence_contact': fields.integer('Contact Seq.',help='Order of\
                     importance of this address in the list of addresses of the linked contact'),

In addition to the direct phone and fax number the 'other' phone number would be appreciated

Thanks

Etienne

P.S. As soon as we have a test installation on 6.1 running I can prepare patches

Related branches

Etienne Hirt (hirt) wrote :

Before adding fields the view has too be cleaned.
The location menu in the attached patch might be removed at the end but currently required for checking and corrections

Is there a branch to commit this work?

Etienne Hirt (hirt) wrote :

Patch adds new fields and ensures sorting for Partner view. Missing is the main function of a contact that has to be added by means of an lookup function getting the job with the lowest sequence number or is there a possibility to define order per parent object?

Etienne Hirt (hirt) wrote :

Patch adds new fields and ensures sorting for Partner view. Missing is the main function of a contact that has to be added by means of an lookup function getting the job with the lowest sequence number or is there a possibility to define order per parent object?

Changed in openobject-addons:
assignee: nobody → OpenERP R&D Addons Team 1 (openerp-dev-addons1)
importance: Undecided → Wishlist
status: New → Confirmed
Etienne Hirt (hirt) wrote :

Can we change the title or move the topic to a specific branch because if more an more covers finalising and correcting the new approach?

Etienne Hirt (hirt) wrote :

* The patch removes last_name and uses name instead in order to allow create of contacts
* The patch adds trigger for storage but for 'mobile' and 'title' as they lead to not understood errors
* All fields are now added and the views corrected

Todo:
* fix the main-job for contacts and the main-address for partners
* check the search function
* How to sort on a view basis the address trees for contacts and for partners?

Etienne Hirt (hirt) wrote :

* initial correction of search
* selection of main_job of contact based on 'sequence_contact'
* more triggers but even more required and strange bug (see @bug)

Etienne Hirt (hirt) wrote :

Now adding the on update contact_id but storage of name in address might be removed also and then this function is not required

More or less finished and ready for review

Missing is the correct sorting for the list of functions within contacts

Etienne Hirt (hirt) wrote :

The latest diff result that includes update to trunk version revision 6599 is available in the branch:
https://code.launchpad.net/~openerp-community/openobject-addons/trunk-bug-923440-base_contact_finalise6.1 that is linked but I can not see it in this bug form.

Work will be continued in the branch. Input including branch setup correction welcome

Etienne Hirt (hirt) wrote :

This is the diff for review that should fix all the mentioned bugs and more

Etienne Hirt (hirt) wrote :

Finalized usability in branch https://code.launchpad.net/~openerp-community/openobject-addons/trunk-bug-923440-base_contact_finalise6.1

Still waiting for any review

What shall be done with the base_contact module as it emptied in the current (6.2) trunk?

Amit Parik (amit-parik) wrote :

Hello Etienne and Stuart,

As Etienne said, base_contact module is empty for trunk because we have removed this functionality (res.partner.contact object).

That's why we have removed this module from trunk. So this feature can not be consider anymore for trunk.

For 6.1 it's big improvement. 6.1 is stable version, We have consider only blocking point and small change for stable version (because partner are used their production database on stable version, If we done a big commit as a improvement then many problem will occurs on their production database).

So we can not consider this improvement for stable 6.1.

Anyways thanks for contributions.

Hope you will understand this procedure.

Thanks again!

Changed in openobject-addons:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers