# Property Validation using basic rules

**URL:** <https://community.hubspot.com/t/property-validation-using-basic-rules/149854>\
**Category:** HubSpot Ideas\
**Created:** [May 30, 2026, 12:15am UTC](https://community.hubspot.com/t/property-validation-using-basic-rules/149854 "2026-05-30T00:15:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![HUr-Rehman](https://avatars.discourse-cdn.com/v4/letter/h/e480ec/32.png) [@HUr-Rehman](https://community.hubspot.com/u/HUr-Rehman)\
**Post date:** [May 30, 2026, 12:15am UTC](https://community.hubspot.com/t/property-validation-using-basic-rules/149854/1 "2026-05-30T00:15:47Z")

</div>

For context, we use a lot of custom properties for various parts of our business. The most important at this is customer onboarding.

When creating custom properties (or adding validation for existing ones), I have found two field types that leave me wanting more from the rules that are available.

1. Number
  - Have a validation rule to allow use of special characters, specifically hyphen/dash, colon, and any others that may commonly be used for fields that are predominantly numbers.
  - The goal is to allow users to enter a range of numbers.
  - For example, a form field asking for expected number of shipments per month. Then answer could be “10-25.”
  - Since this is not allowed, we are forced to change the property to a single-line text.

2. Single-line text (specifically in regards to “Validate using basic rules”)
  - The error message provided to the users is very misleading or not properly informative.

  - Ideally the message needs to be tweaked or allow HubSpot users to modify the verbiage for each case.

  - Allowed Spaces: Don’t allow leading or trailing spaces provides the error message "

  - Case-sensitivity: Require title casing provides the error message "

  - No validation in Title casing for Contact Names (e.g. Contact First name, Last name) since it cannot handle names like McDonald, MacDuff, O’Brian, Jean-Francois, etc.

It would be great to see some implementation to handling number properties to apply ranges or ratios, without having to use Single-line text field type.

For Single-line text basic rules, would really love the ability to customize the error message handling.

Best Regards,

Haseeb Ur-Rehman