<?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: Another issue with SA in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Another-issue-with-SA/m-p/1438592#M1325540</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Okay,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have thought about this and there is an Option that should really make this foolproof - well, we won't put that to the test &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; - there is the function &amp;gt;&amp;gt; Documenttitle() &amp;lt;&amp;lt;, which, other than &amp;gt;&amp;gt; Documentname() &amp;lt;&amp;lt;, queries the Name of an app which you can enter in the "Document_properties". That always stays the same, no matter what Suffix you append to the filename, so the SA should Keep working throughout our standardized development_procedure - given there is an entry in that field in every app - but since we have to roll out this new SA_approach one app at a time anyway, that is just one more step to take - to enter the Name of the app (which should be identical to the filename without any Suffixes).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Sep 2017 14:43:11 GMT</pubDate>
    <dc:creator>datanibbler</dc:creator>
    <dc:date>2017-09-19T14:43:11Z</dc:date>
    <item>
      <title>Another issue with SA</title>
      <link>https://community.qlik.com/t5/QlikView/Another-issue-with-SA/m-p/1438591#M1325538</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have developed a new Approach to all the SAs we Need, which seems to work and will probably save us a lot of time - there is an INCLUDE now which loads from a qvd, which in turn is made from a crosstable where we will stepwise build an overview of which user has what type of Access to what. When that qvd is up to date (there is a "Generator" to renew it whenever something new has been entered into that Excel_crosstable), then the INCLUDE just loads it and creates the SA_table from it.&lt;/P&gt;&lt;P&gt;The potential issue is to do with our "development_Standards": When a productive app is to be altered in any way, the Standard Approach is to create a copy with a Suffix (the Initials of the developer and the date) and move it to the development_area - before ever reloading it.&lt;/P&gt;&lt;P&gt;=&amp;gt; If that Standard is really adhered to, nothing should happen - unless someone renames the productive Version of an app and then reloads it - BEFORE copying it &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; That is something that noone in this Position should even consider - but who knows, shit happend ...&lt;/P&gt;&lt;P&gt;=&amp;gt; So, can we somehow enter a "fallback solution" to make sure that at least one of us can still open an app even if, according to the SA, no one can open it anymore?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-users/34352" target="_blank"&gt;awhitfield&lt;/A&gt;‌, do you think this could be achieved using that Special "key_app" from your method?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks a lot!&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DataNibbler&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Another-issue-with-SA/m-p/1438591#M1325538</guid>
      <dc:creator>datanibbler</dc:creator>
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: Another issue with SA</title>
      <link>https://community.qlik.com/t5/QlikView/Another-issue-with-SA/m-p/1438592#M1325540</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Okay,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have thought about this and there is an Option that should really make this foolproof - well, we won't put that to the test &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; - there is the function &amp;gt;&amp;gt; Documenttitle() &amp;lt;&amp;lt;, which, other than &amp;gt;&amp;gt; Documentname() &amp;lt;&amp;lt;, queries the Name of an app which you can enter in the "Document_properties". That always stays the same, no matter what Suffix you append to the filename, so the SA should Keep working throughout our standardized development_procedure - given there is an entry in that field in every app - but since we have to roll out this new SA_approach one app at a time anyway, that is just one more step to take - to enter the Name of the app (which should be identical to the filename without any Suffixes).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Sep 2017 14:43:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Another-issue-with-SA/m-p/1438592#M1325540</guid>
      <dc:creator>datanibbler</dc:creator>
      <dc:date>2017-09-19T14:43:11Z</dc:date>
    </item>
  </channel>
</rss>

