Skip to main content

Split first name and last name for non company partners

Project description

License: AGPL-3

Partner first name and last name

This module was written to extend the functionality of contacts to support having separate last name and first name.

Configuration

You can configure some common name patterns for the inverse function in Settings > General settings:

  • Lastname Firstname: For example ‘Anderson Robert’

  • Lastname, Firstname: For example ‘Anderson, Robert’

  • Firstname Lastname: For example ‘Robert Anderson’

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 lastname and firstname from a simple string and also _get_computed_name to get a name form the lastname and firstname. These methods can be overridden to change the format specified above.

Usage

The field name becomes a stored function field concatenating the last name and the first name. This avoids breaking compatibility with other modules.

Users should fulfill manually the separate fields for last name and first name, but in case you edit just the name field in some unexpected module, there is an inverse function that tries to split that automatically. It assumes that you write the name in format configured (“Lastname Firstname”, by default), but it could lead to wrong splitting (because it’s just blindly trying to guess what you meant), so you better specify it manually.

For the same reason, after installing, previous names for contacts will stay in the name field, and the first time you edit any of them you will be asked to supply the last name and first name (just once per contact).

Try me on Runbot

For further information, please visit:

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.

Credits

Contributors

Translations

  • Danish: Hans Henrik Gabelgaard

  • Italian: Leonardo Donelli

  • Spanish: Antonio Espinosa

  • Antonio Espinosa <antonioea@antiun.com>

Maintainer

Odoo Community Association

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 http://odoo-community.org.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

odoo11_addon_partner_firstname-11.0.1.0.1-py2.py3-none-any.whl (83.7 kB view details)

Uploaded Python 2 Python 3

File details

Details for the file odoo11_addon_partner_firstname-11.0.1.0.1-py2.py3-none-any.whl.

File metadata

File hashes

Hashes for odoo11_addon_partner_firstname-11.0.1.0.1-py2.py3-none-any.whl
Algorithm Hash digest
SHA256 b830ff7a421375ce207610646b6a191e6526fed9d6f6ebd7ee1dfe6b47a00835
MD5 456537a7951af12e0b70f31af51001e3
BLAKE2b-256 6697ffbe86a48e87ae9d09b019eaed7c214e7ea3ae39d8283ef8bdd923e7a9bb

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page