Thank you, AeyPKA. We understand that. One of the requirements we have is to enforce the cashier to use the proper format while keying in the customer phone number. For example, <+> <Country code> <phone no.>. Since the phone number is a standard field, we want to utilize the same and not to create attributes. We thought of couple of options
1. Create attributes for country code and phone number and update the standard phone number field while updating the phone number related attributes. The standard phone number field will be made non-editable. This way, the cashiers are not comfortable scrolling down to the attributes section all the time and do this, as a matter of fact, we have lots of attributes created and it is hard to locate phone number every time they do this.
2. If we can hide the standard phone number, and bring up only the phone number related attribute to the position where the standard phone number is, is another option. Not sure if this is even possible though. But this does not require a major customization on the functionality as we can make use of the existing attributes feature, it is just that we need to position the selected attributes in a different place.
This is one of the requirements and we do have many data quality checks on the customer data which requires us to extend the customer add/edit page. Any inputs on this would be greatly appreciated. Thanks!
