summaryrefslogtreecommitdiff
path: root/addons/phone_validation/wizard
diff options
context:
space:
mode:
authorThibault Delavallée <tde@odoo.com>2020-09-25 07:09:30 +0000
committerThibault Delavallée <tde@odoo.com>2020-09-25 09:27:16 +0000
commitcecc4ca6f02e599e193c3fa688bfcbd02ac0580b (patch)
tree81bf0009b183f47c5f0f927dfa2ec498701ed561 /addons/phone_validation/wizard
parentc884a29b6b0f2cbc8b0aebbaed93d6f211621d1d (diff)
[FIX] crm: remove unnecessary warning in phone format
In this commit we remove the warning logger when not being able to format a phone number. Indeed this does not indicate there was a real issue. It simply indicates that either the phone number is not parsable or not matching given country format. It happens in a lot of situation that phone numbers are not valid: bad encoding, country mismatch due to {lead, task, ticket} / partner not always being the same, ... This should not raise a server warning. When using frontend SMS composer for phone number, a warning is displayed to the user telling the number is probably incorrect. This is considered as sufficient from UX point of view as it warns users. We do not think we should warn admins that some data is incoherent in database. This commit also * Revert "[FIX] crm: avoid linking demo leads with an unrelated partner" This reverts commit 2c94c4c81ffa171158586cd64828d27c537cd1d6 -> having "invalid" data should be a valid use case of real life * Revert "[FIX] crm: get correct country for phone validation" This reverts commit a58f9fc154c038d72031b281e2bec2c0fc2915ba -> country of a lead comes from its partner if set but can be different. Same for phone numbers. Values on a lead after a compute are considered as complete. Sales persons could effectively have incoherent data on their form view but that is the result of what has been encoded. Task ID-2325228
Diffstat (limited to 'addons/phone_validation/wizard')
0 files changed, 0 insertions, 0 deletions