<?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: Use the history of a property for reporting/workflow/etc in Tips, Tricks &amp; Best Practices</title>
    <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Use-the-history-of-a-property-for-reporting-workflow-etc/m-p/962626#M5305</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/662694"&gt;@NT_&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Unfortunately, at this time it is still not possible to populate a field with the HubSpot user who made a change to another field without using code.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This may be possible with a custom-coded workflow action using the API.&amp;nbsp; This would require an OperationsHub Professional subscription and the support of a developer.&lt;/P&gt;</description>
    <pubDate>Thu, 18 Apr 2024 12:58:12 GMT</pubDate>
    <dc:creator>trevordjones</dc:creator>
    <dc:date>2024-04-18T12:58:12Z</dc:date>
    <item>
      <title>Use the history of a property for reporting/workflow/etc</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Use-the-history-of-a-property-for-reporting-workflow-etc/m-p/962407#M5302</link>
      <description>&lt;P&gt;Hey community,&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;I haven't been able to find a solution here, but hopefully somebody knows a nice trick that doesn't involve exporting the property history or an API workaround.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Our problem is that two different persons can fill out individual properties on the same company. So right now, person 1 can fill out property A, and person 2 can fill out property B, but we don't know if it's the same person who filled out the two properties.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;I was then wondering if it's possible to create another property that, based on a property, can tell us who filled out the property – property history? For example, it can be a company property called "Filled out by" that lists the different team names that fill it out. I then hoped that I could put it in a workflow that automatically gets updated whenever someone fills out property A or B.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Is this still not possible to do?&lt;/P&gt;</description>
      <pubDate>Thu, 18 Apr 2024 07:43:42 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Use-the-history-of-a-property-for-reporting-workflow-etc/m-p/962407#M5302</guid>
      <dc:creator>NT_</dc:creator>
      <dc:date>2024-04-18T07:43:42Z</dc:date>
    </item>
    <item>
      <title>Re: Use the history of a property for reporting/workflow/etc</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Use-the-history-of-a-property-for-reporting-workflow-etc/m-p/962626#M5305</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/662694"&gt;@NT_&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Unfortunately, at this time it is still not possible to populate a field with the HubSpot user who made a change to another field without using code.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This may be possible with a custom-coded workflow action using the API.&amp;nbsp; This would require an OperationsHub Professional subscription and the support of a developer.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Apr 2024 12:58:12 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Use-the-history-of-a-property-for-reporting-workflow-etc/m-p/962626#M5305</guid>
      <dc:creator>trevordjones</dc:creator>
      <dc:date>2024-04-18T12:58:12Z</dc:date>
    </item>
  </channel>
</rss>

