Merge lp:~yannick-buron/partner-contact-management/partner-contact-management into lp:~partner-contact-core-editors/partner-contact-management/7.0
Proposed by
YannickB (YOLO consulting)
Status: | Needs review |
---|---|
Proposed branch: | lp:~yannick-buron/partner-contact-management/partner-contact-management |
Merge into: | lp:~partner-contact-core-editors/partner-contact-management/7.0 |
Diff against target: |
405 lines (+368/-0) 7 files modified
base_partner_customer_fiability/__init__.py (+21/-0) base_partner_customer_fiability/__openerp__.py (+37/-0) base_partner_customer_fiability/base_partner_customer_fiability.py (+115/-0) base_partner_customer_fiability/base_partner_customer_fiability_view.xml (+71/-0) base_partner_customer_fiability/i18n/base_partner_customer_fiability.pot (+61/-0) base_partner_customer_fiability/i18n/fr.po (+61/-0) base_partner_customer_fiability/security/ir.model.access.csv (+2/-0) |
To merge this branch: | bzr merge lp:~yannick-buron/partner-contact-management/partner-contact-management |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Lorenzo Battistini (community) | Needs Resubmitting | ||
Pedro Manuel Baeza | code review | Needs Fixing | |
Review via email: mp+221742@code.launchpad.net |
Description of the change
Hello everybody,
Here is a little module I use for one of my customer. It is used for managing the fiability level of the customers, to know if they will pay or not.
It's really simple, but I hope it is a good base for adding more complex features later. What do you think?
To post a comment you must log in.
Unmerged revisions
- 40. By yannick@yannick_buron.synerpgy.fr
-
[ADD] Module base_partner_
customer_ fiability
Hi, Yannick, thanks for the contribution. Some remarks:
- Please respect PEP8. customer_ fiability. py?
- Use orm.Model instead of osv.osv.
- Do you need all imports in base_partner_
- Put relative imports in __init__.py.
From functional point of view: customer. fiability model? Isn't better to have a calculated field that makes the average from invoices delays?
- Why do you need a res.partner.
- I'm also worried by the overall performance of the system, due to payment_delay is not stored and general fiability of the customer changes with each paid invoice and the way you make it. You can improving calling methods with packed ids, using read for reading only one data, and so on.
Changing approach, I would put a cron job that updates once a day all the data, storing them. This only means a no real-time update, but with little differences.
Regards.