I would like to suggest applying the validation rules for properties in the forms tool as well.
I'm trying to create properties with specific validation rules, characters limit and type, but this is something that just works if you complete the property inside the CRM, not for forms. So anyone can fill these properties with any text or value that doesn't meet the rules without the form displaying any type of error.
I’m Ian, the Product Manager for HubSpot’s Forms tool.
Thank you all for taking the time to submit, upvote, and comment on this Idea. I'm happy to report that CRM Property Validation supports min and max character limits and is available in the new Forms Editor.
Agreed! Applying property rules to values set via forms and workflows would enhance data management in HubSpot. Here are some additional functionality that might support this feature:
Notification on Form - If the value entered does not meet property rules, show a user-facing message prompting them to revise their entry before submitting the form.
Customizable Rules - Allow HubSpot users to decide if the rules applies to data entered directly into CRM, forms, workflows, or all.
Internal error handling/notifications - A mechanism to identify records that violate the rule, with the option to notify internal users about the issue and how to resolve it.
Agreed- We can't enforce validation rules in the forms that are included in our customer ticketing portal. Without these, we run the risk of incorrect data inconsistencies
I’m Ian, the Product Manager for HubSpot’s Forms tool.
Thank you all for taking the time to submit, upvote, and comment on this Idea. I'm happy to report that CRM Property Validation supports min and max character limits and is available in the new Forms Editor.
@IMcDonald When will the new forms editor allow ticket properties? We frequently use forms to create tickets, making the new editor virtually useless to us. Also, there are other important rules that you allow on properties, but don't show up on the forms. For instance, you allow date properties to be restricted to future dates. Great! But it's not on the forms. To me, that's the WHOLE reason to create that kind of property. Thank you for listening to my gripe :).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.