Entering Number in filed 'phoneNumber' creates Error 400
Collapse
X
-
Hi,
can you check these file :
https://github.com/espocrm/espocrm/b...eType.php#L119
https://github.com/espocrm/espocrm/b...eType.php#L188
and look metadata
https://github.com/espocrm/espocrm/b...terns.json#L27
can you too change function :
https://github.com/espocrm/espocrm/b...eType.php#L178
to
private function isValidNumber(string $number): bool
maybeLast edited by item; 12-02-2022, 11:17 AM.If you could give the project a star on GitHub. EspoCrm believe our work truly deserves more recognition. Thanks. -
Change the Default Value (Standardtyp) to "Office" and then Save.
Thing is that you have the default value set to "Buro" that is not a valid option. It's a translation.
I also recommend to update all values in the phone_number table from Buro to Office.Last edited by yuri; 12-02-2022, 02:19 PM.Comment
-
Translation: OMG, will I ever get it right? Thanks for the hint!
Change type "Büro" to "Office": It's because of the Umlauts? I will have to delete my "Büro" types then and set new "Office" ones. I will loose data, won't I?Comment
-
It's because you had the Büro (not translation) option before and removed it after. But it did not remove it from the Default Value (the bug we had before). So now you had Office as a valid value, but Büro as a default value (not valid value).
You won't loose any data if you run an SQL query updating Büro => Office.Last edited by yuri; 12-02-2022, 03:18 PM.Comment
-
Well, just what you would type in into a phone number field. Such as just numbers or an combination like "+49 (0) 1234/6789". Should be no problem, referring to "phoneNumberLoose" in \var\www\html\custom\Espo\Custom\Resources\metadat a\app\regExpPatterns.json
I must appologize, if I didn't get you right!Comment

Comment