| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Contacts (contacts)
• Discuss (mail) |
| Lines of code | 71 |
| Technical Name |
unique_contact_alert |
| License | LGPL-3 |
| Versions | 17.0 18.0 19.0 |
Unique Contact Alert
The Unique Contact Alert module allows administrators to define one or more contact fields as unique identifiers. During contact creation and updates, Odoo automatically validates these fields and prevents duplicate contact records from being saved.
This ensures better data quality, eliminates duplicate contacts, and helps maintain a clean and reliable customer database across your organization.
Why Use Unique Contact Alert?
- Dynamic unique field selection.
- Supports multiple contact fields.
- Prevents duplicate contact records.
- Case-insensitive duplicate detection.
- Ignores leading and trailing spaces.
- User-friendly validation messages.
Demo
The module automatically validates contact data and instantly alerts users when duplicate values are detected.
Configuration
Navigate to:
Administrators can choose one or more contact fields that should be treated as unique identifiers.
- Select one or more contact fields.
- Save the configuration.
- Selected fields become unique automatically.
- Duplicate contacts are blocked during creation and updates.
Features
- Dynamic field selection from contact fields.
- Supports multiple unique fields.
- Case-insensitive validation.
- Automatic whitespace trimming.
- Clear validation error messages.
- Works during create and write operations.
Master = master = MASTER = master
Duplicate Email Validation
When Email is configured as a unique field, Odoo prevents users from saving contacts that already exist with the same email address.
Duplicate Name Validation
When Name is selected as a unique field, duplicate contact names are detected and blocked automatically.
Benefits
- Maintains clean contact data.
- Reduces duplicate customer records.
- Improves reporting accuracy.
- Enhances CRM data quality.
- Simple administrator configuration.
- No coding required.
Best Practices
- Use Email as a primary unique identifier.
- Combine multiple fields when necessary.
- Review uniqueness settings periodically.
- Avoid selecting fields that frequently change.
- Validate existing data before enabling uniqueness.
Contact
For implementation support, customization requests, technical assistance, or functional guidance regarding this module, please contact:
Vashmitha | Developer
Email: vashmitha@rightangle.dev
Please log in to comment on this module