<?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 Managing and publishing community sheets in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Managing-and-publishing-community-sheets/m-p/1120151#M19338</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Qlik Community,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;We are on Qlik Sense 2.2 and planning to do the Dev upgrade to 3.0 this weekend and most probably the Prod migration next weekend. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;We recently encountered challenge around managing community sheets when ready to roll-out to the primary audience. The business and our developers are co-developing a lot of exciting dashboards (sheets). The order of operation is generally:&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;1) An app is architected and a prototype base sheet is produced by IT and published&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;2) The business and/or finance clones these sheet templates and starts customizations working with our Qlik developers in a UAT stream&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;3) We currently cannot figure out how to move the developed sheet out of the UAT stream to roll-out to the larger organization&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;We can see in QMC console where the community APP object (tagged as unapproved) is located but see no move/copy functionality.&amp;nbsp; Any attempt to export or duplicate the app only carries the base sheets originally produced by IT.&amp;nbsp; Researching &lt;A href="http://help.qlik.com/"&gt;&lt;SPAN class="s2"&gt;http://help.qlik.com&lt;/SPAN&gt;&lt;/A&gt; did not clearly identify this limitation/bug or provide a solution.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;Hoping you can point us in the right direction and/or advise what the ideal framework is for coordinating sheet development between business and developers.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;Ventsi&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 21 Jul 2016 17:39:02 GMT</pubDate>
    <dc:creator />
    <dc:date>2016-07-21T17:39:02Z</dc:date>
    <item>
      <title>Managing and publishing community sheets</title>
      <link>https://community.qlik.com/t5/App-Development/Managing-and-publishing-community-sheets/m-p/1120151#M19338</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Qlik Community,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;We are on Qlik Sense 2.2 and planning to do the Dev upgrade to 3.0 this weekend and most probably the Prod migration next weekend. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;We recently encountered challenge around managing community sheets when ready to roll-out to the primary audience. The business and our developers are co-developing a lot of exciting dashboards (sheets). The order of operation is generally:&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;1) An app is architected and a prototype base sheet is produced by IT and published&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;2) The business and/or finance clones these sheet templates and starts customizations working with our Qlik developers in a UAT stream&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;3) We currently cannot figure out how to move the developed sheet out of the UAT stream to roll-out to the larger organization&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;We can see in QMC console where the community APP object (tagged as unapproved) is located but see no move/copy functionality.&amp;nbsp; Any attempt to export or duplicate the app only carries the base sheets originally produced by IT.&amp;nbsp; Researching &lt;A href="http://help.qlik.com/"&gt;&lt;SPAN class="s2"&gt;http://help.qlik.com&lt;/SPAN&gt;&lt;/A&gt; did not clearly identify this limitation/bug or provide a solution.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;Hoping you can point us in the right direction and/or advise what the ideal framework is for coordinating sheet development between business and developers.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;Ventsi&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Jul 2016 17:39:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Managing-and-publishing-community-sheets/m-p/1120151#M19338</guid>
      <dc:creator />
      <dc:date>2016-07-21T17:39:02Z</dc:date>
    </item>
  </channel>
</rss>

