Update user's and partner's data fields from employee record
When using HR, there are a couple of partners involved per employee: The employee’s work address, the employee’s private address and the partner assigned to the employee’s user (if any). The latter is used to store some data about the user, like the email address. In many cases, it would be more convenient to edit this data from the employee record. This module assumes you assign a (different) partner for the work address to every employee, and synchronizes its values with the employee record. Then you should use this partner record also for the user record. When assigning an existing user, the module will replace this user’s partner with the current work address’s partner.
Table of contents
After installation, updating an employee’s work_email, work_phone, mobile_phone and image fields transparently changes the linked partner’s appropriate field and vice versa. For obvious reasons, the default for the work address being the company’s address has been lifted. Partners created through the work address field will have the employee-flag set, and the partner_id field on the user record filters for this flag.
When creating a user, you can select the existing partner record for your employee, so it will be updated transparently too. Creating a user via the user field in the employee form preselects this partner record.
As it would be problematic to have work addresses pointing to the company’s partner with this module, all employees are updated with either a new partner as work address in case they are not linked to a user, or with the user’s partner otherwise. This may take some time if you have a lot of employees. For existing work addresses, the partner’s data win, so if your employee as ha different email/phone number/image than the corresponding partner, those fields will be overwritten - but only if it is set in the partner.
Also multiple employees pointing to the same partner is problematic. This is fixed by creating new partners for all employees involved, and flagging all of them with the label ‘Duplicate work address’ and the newly created ones with ‘Duplicate work address / Newly created’. Then after installation, search for partners with this labels to do whatever cleanup you consider necessary. After this, it’s safe to delete the labels again.
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
- Icon courtesy of http://www.picol.org (refresh.svg) and https://github.com/odoo/odoo/blob/8.0/addons/hr/static/description/icon.png
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
This module is part of the OCA/hr project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size odoo10_addon_hr_employee_data_from_work_address-10.0.1.0.0.99.dev2-py2-none-any.whl (35.2 kB)||File type Wheel||Python version py2||Upload date||Hashes View|
Hashes for odoo10_addon_hr_employee_data_from_work_address-10.0.1.0.0.99.dev2-py2-none-any.whl