<?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: Any tips on archive control? in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Any-tips-on-archive-control/m-p/2547947#M32759</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Managing multiple QVF files for versioning often leads to clutter and confusion.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;A better approach is to use centralized version control. With SenseOps Code Management, you can maintain a single source of truth where changes are tracked automatically, making it easy to manage versions and roll back when needed.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;This helps keep your environment organized, especially with multiple developers.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;More info: &lt;/SPAN&gt;&lt;A href="https://www.senseops.com/code-management/" target="_blank"&gt;&lt;SPAN&gt;https://www.senseops.com/code-management/&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Documentation: &lt;/SPAN&gt;&lt;A href="https://www.senseops.com/resources/documentation/code-management/" target="_blank"&gt;&lt;SPAN&gt;https://www.senseops.com/resources/documentation/code-management/&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 28 Apr 2026 06:47:36 GMT</pubDate>
    <dc:creator>NS_Qlikupdates</dc:creator>
    <dc:date>2026-04-28T06:47:36Z</dc:date>
    <item>
      <title>Any tips on archive control?</title>
      <link>https://community.qlik.com/t5/Management-Governance/Any-tips-on-archive-control/m-p/1736617#M16543</link>
      <description>&lt;P&gt;Hi, hope you're doing well. The amount of dashboards that we create within our organisation is growing. Most of the dashboard are build incremental, which results in different versions of one QVF and many archived/old version. I know that Soterre can help you with versioncontrol, but do you have any tips/best practises when it comes to version &amp;amp; archive control?&lt;/P&gt;&lt;P&gt;We're a team with 4 developers, 800 potential users (readers) and a few selfservice users.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Aug 2020 07:10:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Any-tips-on-archive-control/m-p/1736617#M16543</guid>
      <dc:creator>glasaron</dc:creator>
      <dc:date>2020-08-18T07:10:03Z</dc:date>
    </item>
    <item>
      <title>Re: Any tips on archive control?</title>
      <link>https://community.qlik.com/t5/Management-Governance/Any-tips-on-archive-control/m-p/2547947#M32759</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Managing multiple QVF files for versioning often leads to clutter and confusion.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;A better approach is to use centralized version control. With SenseOps Code Management, you can maintain a single source of truth where changes are tracked automatically, making it easy to manage versions and roll back when needed.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;This helps keep your environment organized, especially with multiple developers.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;More info: &lt;/SPAN&gt;&lt;A href="https://www.senseops.com/code-management/" target="_blank"&gt;&lt;SPAN&gt;https://www.senseops.com/code-management/&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Documentation: &lt;/SPAN&gt;&lt;A href="https://www.senseops.com/resources/documentation/code-management/" target="_blank"&gt;&lt;SPAN&gt;https://www.senseops.com/resources/documentation/code-management/&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Apr 2026 06:47:36 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Any-tips-on-archive-control/m-p/2547947#M32759</guid>
      <dc:creator>NS_Qlikupdates</dc:creator>
      <dc:date>2026-04-28T06:47:36Z</dc:date>
    </item>
  </channel>
</rss>

