# New validation for custom object names

**URL:** <https://community.hubspot.com/t/new-validation-for-custom-object-names/51782>\
**Category:** Developer Announcements\
**Tags:** api\
**Created:** [February 17, 2022, 7:04pm UTC](https://community.hubspot.com/t/new-validation-for-custom-object-names/51782 "2022-02-17T19:04:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dadams](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/dadams/32/21752_2.png) [@Dadams](https://community.hubspot.com/u/Dadams)\
**Post date:** [February 17, 2022, 7:04pm UTC](https://community.hubspot.com/t/new-validation-for-custom-object-names/51782/1 "2022-02-17T19:04:34Z")

</div>

Effective immediately, we will be enforcing new limits on the `name` field for [custom object schemas](https://developers.hubspot.com/docs/api/crm/crm-custom-objects).

### What’s changing?

Going forward, the `name` field for new custom object schemas will be limited to letters, numbers, underscores, and hyphens. Creating a new schema with a `name` containing any other characters will result in a 400 error response.  
Existing objects will not be affected by this change, as this validation is only applied when creating a new schema.  
No changes are being made for the `label` field, which is what users would see when viewing the objects in HubSpot.

### When is this happening?

The new validation is already in place, and will affect any new object schemas created.  
Please let us know if you have any questions by replying below.

---

<div class="post-metadata">

**Author:** ![tominal](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tominal/32/73018_2.png) [@tominal](https://community.hubspot.com/u/tominal)\
**Post date:** [February 17, 2022, 11:00pm UTC](https://community.hubspot.com/t/new-validation-for-custom-object-names/51782/2 "2022-02-17T23:00:57Z")

</div>

My bet is that someone tried setting a custom object internal name to the Log4j RCE pattern.