<?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: qvuser()  and osUser()  for App data filtering? in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/qvuser-and-osUser-for-App-data-filtering/m-p/2473281#M99875</link>
    <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/149113"&gt;@MatheusC&lt;/a&gt;&amp;nbsp; &amp;amp;&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/49013"&gt;@eike_s&lt;/a&gt;&amp;nbsp; &amp;nbsp;-&amp;nbsp;&amp;nbsp;&lt;BR /&gt;I was trying to be smart by encapsulating the logic into a variable to make it easier to use.- what was odd, was under some visualizations referencing via the variable - presume had the original calculated value of the variable from the load and not the 'live' one.&lt;BR /&gt;&lt;BR /&gt;AS &lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/149113"&gt;@MatheusC&lt;/a&gt;&amp;nbsp; suggested,&amp;nbsp; doing the subfield 'live'&amp;nbsp; - without using variables works and works in some tests with other users.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;='You are logged in as : ' &amp;amp; vEmailLoggedInUser &amp;amp; ' Associated Site :' &amp;amp; only(if(KeyEmailMatchUpper = trim(upper(SubField(osuser(),'UserId=',2))),OfficeName))&lt;/P&gt;</description>
    <pubDate>Fri, 26 Jul 2024 15:18:10 GMT</pubDate>
    <dc:creator>110</dc:creator>
    <dc:date>2024-07-26T15:18:10Z</dc:date>
    <item>
      <title>qvuser()  and osUser()  for App data filtering?</title>
      <link>https://community.qlik.com/t5/App-Development/qvuser-and-osUser-for-App-data-filtering/m-p/2473252#M99869</link>
      <description>&lt;P&gt;So hopefully a quick, two part question&amp;nbsp; &amp;nbsp;-&amp;nbsp; it appears qvuser() doesn't return any data on Qlik SaaS , and osUser() only returns the user that reloaded the app.&lt;BR /&gt;&lt;BR /&gt;I was hoping to be able to retrieve the currently logged in user viewing the app - in order to allow that user to automatically filter their data with a button action.&lt;BR /&gt;&lt;BR /&gt;So&amp;nbsp; &amp;nbsp;- is there a plan to make a 'live' user function, so when referenced, it's aware of who is logged in ( similar to section access )&amp;nbsp; - or is there another function I'm not aware of to attain this info?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jul 2024 13:56:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/qvuser-and-osUser-for-App-data-filtering/m-p/2473252#M99869</guid>
      <dc:creator>110</dc:creator>
      <dc:date>2024-07-26T13:56:18Z</dc:date>
    </item>
    <item>
      <title>Re: qvuser()  and osUser()  for App data filtering?</title>
      <link>https://community.qlik.com/t5/App-Development/qvuser-and-osUser-for-App-data-filtering/m-p/2473266#M99871</link>
      <description>&lt;P&gt;In the Qlik Cloud, the OSUSER() function outputs the ‘Idp subject’ of the current user under userid. Depending on how and what kind of IdP is configured, the corresponding value is returned.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jul 2024 14:30:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/qvuser-and-osUser-for-App-data-filtering/m-p/2473266#M99871</guid>
      <dc:creator>eike_s</dc:creator>
      <dc:date>2024-07-26T14:30:34Z</dc:date>
    </item>
    <item>
      <title>Re: qvuser()  and osUser()  for App data filtering?</title>
      <link>https://community.qlik.com/t5/App-Development/qvuser-and-osUser-for-App-data-filtering/m-p/2473274#M99873</link>
      <description>&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/180799"&gt;@110&lt;/a&gt;&amp;nbsp; OSUser() will return the currently connected user. See the documentation below from Qlik Help.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://help.qlik.com/en-US/sense/May2024/Subsystems/Hub/Content/Sense_Hub/Scripting/SystemFunctions/system-functions.htm" target="_blank"&gt;https://help.qlik.com/en-US/sense/May2024/Subsystems/Hub/Content/Sense_Hub/Scripting/SystemFunctions/system-functions.htm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="MatheusC_0-1722005728663.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/169983iEDE602E0D51E9420/image-size/medium?v=v2&amp;amp;px=400" role="button" title="MatheusC_0-1722005728663.png" alt="MatheusC_0-1722005728663.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can use the expression below, which will evaluate and extract the user, then apply your filter condition:&lt;/P&gt;
&lt;P&gt;=SubField(OSUser(), '=', -1)&lt;/P&gt;
&lt;P&gt;As informed &lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/49013"&gt;@eike_s&lt;/a&gt;&amp;nbsp; by the configuration, it can return either the IDP or the email.&lt;BR /&gt;&lt;BR /&gt;- Matheus&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jul 2024 14:56:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/qvuser-and-osUser-for-App-data-filtering/m-p/2473274#M99873</guid>
      <dc:creator>MatheusC</dc:creator>
      <dc:date>2024-07-26T14:56:34Z</dc:date>
    </item>
    <item>
      <title>Re: qvuser()  and osUser()  for App data filtering?</title>
      <link>https://community.qlik.com/t5/App-Development/qvuser-and-osUser-for-App-data-filtering/m-p/2473281#M99875</link>
      <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/149113"&gt;@MatheusC&lt;/a&gt;&amp;nbsp; &amp;amp;&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/49013"&gt;@eike_s&lt;/a&gt;&amp;nbsp; &amp;nbsp;-&amp;nbsp;&amp;nbsp;&lt;BR /&gt;I was trying to be smart by encapsulating the logic into a variable to make it easier to use.- what was odd, was under some visualizations referencing via the variable - presume had the original calculated value of the variable from the load and not the 'live' one.&lt;BR /&gt;&lt;BR /&gt;AS &lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/149113"&gt;@MatheusC&lt;/a&gt;&amp;nbsp; suggested,&amp;nbsp; doing the subfield 'live'&amp;nbsp; - without using variables works and works in some tests with other users.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;='You are logged in as : ' &amp;amp; vEmailLoggedInUser &amp;amp; ' Associated Site :' &amp;amp; only(if(KeyEmailMatchUpper = trim(upper(SubField(osuser(),'UserId=',2))),OfficeName))&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jul 2024 15:18:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/qvuser-and-osUser-for-App-data-filtering/m-p/2473281#M99875</guid>
      <dc:creator>110</dc:creator>
      <dc:date>2024-07-26T15:18:10Z</dc:date>
    </item>
  </channel>
</rss>

