<?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: Delete HubSpot standard properties (i.e. Salutation) in &amp;#128172 RevOps Discussions</title>
    <link>https://community.hubspot.com/t5/128172-RevOps-Discussions/Delete-HubSpot-standard-properties-i-e-Salutation/m-p/647610#M1410</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/399745"&gt;@Sebastian_Lauk&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Default properties cannot be deleted/archived. I understand your challenge and know it too well. &lt;EM&gt;Country/Region&lt;/EM&gt; would be another example where a dropdown is a better option.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To make sure that the correct property is used, I usually name the custom property accordingly, e.g. &lt;EM&gt;Country (use instead of Country/Region)&lt;/EM&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It's not ideal but a solid workaround.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards!&lt;/P&gt;</description>
    <pubDate>Fri, 10 Jun 2022 11:10:14 GMT</pubDate>
    <dc:creator>karstenkoehler</dc:creator>
    <dc:date>2022-06-10T11:10:14Z</dc:date>
    <item>
      <title>Delete HubSpot standard properties (i.e. Salutation)</title>
      <link>https://community.hubspot.com/t5/128172-RevOps-Discussions/Delete-HubSpot-standard-properties-i-e-Salutation/m-p/647599#M1409</link>
      <description>&lt;P&gt;Hi HubSpot community!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm not that new to HubSpot, but nonetheless new to this community. Happy to be here!&lt;BR /&gt;&lt;BR /&gt;The HubSpot Standard property for salutation is a "Single Line Free Text" field type.&lt;BR /&gt;Because we wanted to use a Dropdown field type for form submissions for the salutation, we created a new property. In order to ensure high data quality and easy of manual use, I'd like to delete the standard property, so that no one has to mind which of the two salutation fields is the correct one.&lt;BR /&gt;&lt;BR /&gt;Is this even possible in HubSpot?&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jun 2022 10:44:36 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/128172-RevOps-Discussions/Delete-HubSpot-standard-properties-i-e-Salutation/m-p/647599#M1409</guid>
      <dc:creator>Sebastian_Lauk</dc:creator>
      <dc:date>2022-06-10T10:44:36Z</dc:date>
    </item>
    <item>
      <title>Re: Delete HubSpot standard properties (i.e. Salutation)</title>
      <link>https://community.hubspot.com/t5/128172-RevOps-Discussions/Delete-HubSpot-standard-properties-i-e-Salutation/m-p/647610#M1410</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/399745"&gt;@Sebastian_Lauk&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Default properties cannot be deleted/archived. I understand your challenge and know it too well. &lt;EM&gt;Country/Region&lt;/EM&gt; would be another example where a dropdown is a better option.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To make sure that the correct property is used, I usually name the custom property accordingly, e.g. &lt;EM&gt;Country (use instead of Country/Region)&lt;/EM&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It's not ideal but a solid workaround.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards!&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jun 2022 11:10:14 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/128172-RevOps-Discussions/Delete-HubSpot-standard-properties-i-e-Salutation/m-p/647610#M1410</guid>
      <dc:creator>karstenkoehler</dc:creator>
      <dc:date>2022-06-10T11:10:14Z</dc:date>
    </item>
  </channel>
</rss>

