Partner second lastname
This module was written to extend the functionality of partner_firstname to support having a second lastname for contact partners.
In some countries, it’s important to have a second last name for contacts.
Contact partners will need to fill at least one of the name fields (First name, First last name or Second last name).
Configuration
You can configure some common name patterns for the inverse function in Settings > Configuration > General settings:
Lastname SecondLastname Firstname: For example ‘Anderson Lavarge Robert’
Lastname SecondLastname, Firstname: For example ‘Anderson Lavarge, Robert’
Firstname Lastname SecondLastname: For example ‘Robert Anderson Lavarge’
After applying the changes, you can recalculate all partners name clicking “Recalculate names” button. Note: This process could take so much time depending how many partners there are in database.
You can use _get_inverse_name method to get firstname, lastname and second lastname from a simple string and also _get_computed_name to get a name form the firstname, lastname and second lastname. These methods can be overridden to change the format specified above.
Usage
To use this module, you need to:
Edit any partner’s form.
Make sure the partner is not a company.
Enter firstname and lastnames.
If you directly enter the full name instead of entering the other fields separately (maybe from other form), this module will try to guess the best match for your input and split it between firstname, lastname and second lastname using an inverse function.
If you can, always enter it manually please. Automatic guessing could fail for you easily in some corner cases.
Known issues / Roadmap
Patterns for the inverse function are configurable only at system level. Maybe this configuration could depend on partner language, country or company, as discussed at this OCA issue
Bug Tracker
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 here.
Credits
Contributors
Jairo Llopis <jairo.llopis@tecnativa.com>.
Antonio Espinosa.
Pedro M. Baeza <pedro.baeza@tecnativa.com>.
Maintainer
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.
To contribute to this module, please visit https://odoo-community.org.
1 maintainer
Metadata
1 maintainer
Release files for odoo10-addon-partner-second-lastname 10.0.2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo10_addon_partner_second_lastname-10.0.2.0.0-py2-none-any.whl | Python 2 | none | any | Details for odoo10_addon_partner_second_lastname-10.0.2.0.0-py2-none-any.whl |
Release files / odoo10_addon_partner_second_lastname-10.0.2.0.0-py2-none-any.whl
| Download URL | odoo10_addon_partner_second_lastname-10.0.2.0.0-py2-none-any.whl |
|---|---|
| Size | 65.0 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
6600654ba3afe462ab5342bb4ecdcf7c45c82bac09ffd693f4b9f73ba4256c80
|
|
BLAKE2b-256 checksum How to use checksums |
3ebe5b39c4bb0fe9b0f3bc12b5fc40fb1e012a5d3bf0286baff1729167d73dfa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/30.4.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.3
|
Security for odoo10-addon-partner-second-lastname 10.0.2.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
