Developer Announcements

Dadams
HubSpot Employee
HubSpot Employee

New validation for custom object names

Effective immediately, we will be enforcing new limits on the name field for custom object schemas.

 

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.

0 Upvotes
1 Reply 1
tominal
Guide | Partner
Guide | Partner

New validation for custom object names

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


Thomas Johnson
Community Champion


Kahu Software LLC
A Texan HubSpot consulting firm
https://kahusoftware.com
0 Upvotes