<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: New validation for custom object names in Developer Announcements</title>
    <link>https://community.hubspot.com/t5/Developer-Announcements/New-validation-for-custom-object-names/m-p/578808#M207</link>
    <description>&lt;P&gt;My bet is that someone tried setting a custom object internal name to the Log4j RCE pattern.&lt;/P&gt;</description>
    <pubDate>Thu, 17 Feb 2022 23:01:23 GMT</pubDate>
    <dc:creator>tominal</dc:creator>
    <dc:date>2022-02-17T23:01:23Z</dc:date>
    <item>
      <title>New validation for custom object names</title>
      <link>https://community.hubspot.com/t5/Developer-Announcements/New-validation-for-custom-object-names/m-p/578561#M206</link>
      <description>&lt;SECTION class="section section--has-sidebar page-center"&gt;
&lt;SECTION class="content__wrapper content__wrapper--narrow"&gt;
&lt;DIV class="developers-blog__post-content" role="article"&gt;
&lt;ARTICLE class="developers-blog__post-content-body"&gt;
&lt;P&gt;Effective immediately, we will be enforcing new limits on the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;name&lt;/CODE&gt;&amp;nbsp;field for&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://developers.hubspot.com/docs/api/crm/crm-custom-objects" rel="noopener" target="_blank"&gt;custom object schemas&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;What's changing?&lt;/H3&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Going forward, the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;name&lt;/CODE&gt;&amp;nbsp;field for new custom object schemas will be limited to letters, numbers, underscores, and hyphens. Creating a new schema with a&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;name&lt;/CODE&gt;&amp;nbsp;containing any other characters will result in a 400 error response.&lt;BR /&gt;&lt;BR /&gt;Existing objects will not be affected by this change, as this validation is only applied when creating a new schema.&lt;BR /&gt;&lt;BR /&gt;No changes are being made for the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;label&lt;/CODE&gt;&amp;nbsp;field, which is what users would see when viewing the objects in HubSpot.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;When is this happening?&lt;/H3&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The new validation is already in place, and will affect any new object schemas created.&lt;BR /&gt;&lt;BR /&gt;Please let us know if you have any questions by replying below.&lt;/P&gt;
&lt;/ARTICLE&gt;
&lt;/DIV&gt;
&lt;/SECTION&gt;
&lt;/SECTION&gt;</description>
      <pubDate>Thu, 17 Feb 2022 19:04:34 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Developer-Announcements/New-validation-for-custom-object-names/m-p/578561#M206</guid>
      <dc:creator>Dadams</dc:creator>
      <dc:date>2022-02-17T19:04:34Z</dc:date>
    </item>
    <item>
      <title>Re: New validation for custom object names</title>
      <link>https://community.hubspot.com/t5/Developer-Announcements/New-validation-for-custom-object-names/m-p/578808#M207</link>
      <description>&lt;P&gt;My bet is that someone tried setting a custom object internal name to the Log4j RCE pattern.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Feb 2022 23:01:23 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Developer-Announcements/New-validation-for-custom-object-names/m-p/578808#M207</guid>
      <dc:creator>tominal</dc:creator>
      <dc:date>2022-02-17T23:01:23Z</dc:date>
    </item>
  </channel>
</rss>

