<?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: 'Previous Version' Table on API Refresh in Developer</title>
    <link>https://community.fabric.microsoft.com/t5/Developer/Previous-Version-Table-on-API-Refresh/m-p/1154035#M24128</link>
    <description>&lt;P&gt;The CRM system is Dynamics. Thanks for the reply, I expected as much.&lt;/P&gt;</description>
    <pubDate>Thu, 11 Jun 2020 22:44:12 GMT</pubDate>
    <dc:creator>CLeDane</dc:creator>
    <dc:date>2020-06-11T22:44:12Z</dc:date>
    <item>
      <title>'Previous Version' Table on API Refresh</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Previous-Version-Table-on-API-Refresh/m-p/1154007#M24126</link>
      <description>&lt;P&gt;I manage a Power BI tool that is linked to my company's CRM database which tracks and forecasts potential business identified by managers. I have this report scheduled to refresh every week and automatically distribute. I would like to create a view that shows the difference between our forecasted numbers since the last refresh.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a way to program Power BI to clone the current data into, say, a "previous version" table everytime the report is refreshed? Then I could use measures to find the differences I want to report from those two tables (the newly refreshed data, and the previous version data)?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a manual workaround, but if this could be automated it would make me look really cool &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jun 2020 22:25:06 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Previous-Version-Table-on-API-Refresh/m-p/1154007#M24126</guid>
      <dc:creator>CLeDane</dc:creator>
      <dc:date>2020-06-11T22:25:06Z</dc:date>
    </item>
    <item>
      <title>Re: 'Previous Version' Table on API Refresh</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Previous-Version-Table-on-API-Refresh/m-p/1154014#M24127</link>
      <description>&lt;P&gt;Power BI doesn't have that. Nor should it (in my opinion) - I think it is better to do that versioning further upstream.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ideally you don't want to do snpashots. Better if you can record just the changes between snapshots (which would require a unique opportunity ID). Much, much better if you could actually do this event based, ie record all changes to your data as they happen.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Snapshots are plagued by the Nyquist-Shannon distance.&amp;nbsp; Event based records are not.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Not sure what your CRM system is, but Salesforce.com (for example) has event based record keeping baked in.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jun 2020 22:32:41 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Previous-Version-Table-on-API-Refresh/m-p/1154014#M24127</guid>
      <dc:creator>lbendlin</dc:creator>
      <dc:date>2020-06-11T22:32:41Z</dc:date>
    </item>
    <item>
      <title>Re: 'Previous Version' Table on API Refresh</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Previous-Version-Table-on-API-Refresh/m-p/1154035#M24128</link>
      <description>&lt;P&gt;The CRM system is Dynamics. Thanks for the reply, I expected as much.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jun 2020 22:44:12 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Previous-Version-Table-on-API-Refresh/m-p/1154035#M24128</guid>
      <dc:creator>CLeDane</dc:creator>
      <dc:date>2020-06-11T22:44:12Z</dc:date>
    </item>
  </channel>
</rss>

