Today, consistent NANP‑compliant phone validation requires configuring the Validation Setup app for each individual data item or building custom logic blocks that throw clunky errors. Validation Setup looks clean, but it cannot be applied to NW base Phone fields, and changing the customization pattern would require extensive manual work across several data items per environment.
This makes phone number validation time‑consuming, inconsistent, and not scalable across modules.
We already have a great model with the Address data type, where Format Definitions can be defined once and defaulted in Module Settings.
What we’re asking for
- Phone Number data type format/validations can be defaulted
- Support for a standard NANP format (10 digits, NPA/NXX rules)
- Ability to apply the default to all Phone data type fields, including NW base fields without customizations
This would eliminate repetitive configuration and custom logic, improve data quality, and create a consistent, platform‑wide phone number experience.