Validation Rules and the Default Contact Phone Number Field

Question

I see many different Validation Rules written to enforce certain formats of phone numbers in Phone Number fields. Are they necessary if the ONLY objective is to store the phone number in the field? Or is the real reason for these Validation Rules to format these phone numbers to allow a dialer app to be able to dial these numbers properly?

Without writing any validation rule on Phone field on Contact object, I am able to save phone numbers (with and without extensions) in the default “Phone Number” field on Contact records, and can save international phone number too (with or without extensions).

The phone field in my developer org accepted the following numbers:

512 757 6000 ext 4562

408 567 8900 ext 34

408 555 7000 ext 4

International Number

+91 9578909870

+01 (352) 000 000 000000

+01 (352) 000 000 000000 ext 222

+011 43 1 333 4444

+011 43 622 333 6789 ext 333

The only limitation on the default Phone Number field on the Contact object is that it limited to 40 characters as far as I am able to ascertain. Any comments, suggestions, or perspectives on this issue will be appreciated.

Thanks,

Neeraja

Jeff May · Accepted Answer

No. Validation Rules on Phone number field are not necessary, and I almost always advice against using them. You want your users to be able to add/update the phone number field with the information they have. Valid phone numbers can be in a really wide variety of formats and writing a VRule or rules to support all of them is not worth the effort since you don't really gain anything.

Validation Rules and the Default Contact Phone Number Field

Collaboration

Aprendizaje relacionado

Más ayuda