Hi everyone! Some additional updates: 1. We've increased the character limit from 100 to 1,000 for text properties which have regex validation applied.
Thanks for the feedback @NBBeale ! We are investigating whether it's possible to increase the 100-character limit. This limit is outlined in the Knowledge Base but we're also looking into ways to make it more explicit in-app so it's more transparent when you are building the property.
Hi @CBirkett1 - could you please file a Support ticket so my team can take a look? The validation should apply regardless of whether a field is required in the Form.
👋I'm Rachel from the HubSpot Product team. Regular expressions for property validations are now in private beta (request access via Product Updates; Pro/Enterprise). Would love to hear any feedback you have on this feature via our in-app survey or this thread. Thanks!
👋I'm Rachel from the HubSpot Product team. Regular expressions for property validations are now in private beta (request access via Product Updates; Pro/Enterprise). Would love to hear any feedback you have on this feature via our in-app survey or this thread. Thanks!
Some feedback from us. In forms, the validation doesn't apply unless the field is required. See examples below where a email based validation doesn't show an error on a non-required field but the same field does when required.
Hi @CBirkett1 - could you please file a Support ticket so my team can take a look? The validation should apply regardless of whether a field is required in the Form.
If the plan is to retain the 100 character limit for now, that'll need to be more transparent in the documentation and during the property creation screen. I spent quite awhile attempting to troubleshoot why my regex was showing a test value to be invalid because it just showed the standard error message. But when I finally just created the property and went to a record to test it, the error explicitly indicated that the value must contain 100 characters or less, which was not conveyed during property creation regex setup or testing that is available.
I would still strongly advocate for increasing the character limit there if possible, but at a minimum the limit needs to be more transparent in documentation and as a part of property creation. Thanks!
Thanks for the feedback @NBBeale ! We are investigating whether it's possible to increase the 100-character limit. This limit is outlined in the Knowledge Base but we're also looking into ways to make it more explicit in-app so it's more transparent when you are building the property.
Hi everyone! Some additional updates: 1. We've increased the character limit from 100 to 1,000 for text properties which have regex validation applied.
But this rule by regex validation, does not work if that property is used in a legacy form editor, it only works with the new form editor. It would be VERY useful that works on legacy editor, as the new form editor do not have the to set the form as RAW HTML like the legacy one does
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
