<?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: Qliksense: URL Encoding ($=%24) in Integration, Extension &amp; APIs</title>
    <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/24615#M378</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Chr(36) is $ .... Chr(39) is not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Was it a typo?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 29 May 2018 13:06:29 GMT</pubDate>
    <dc:creator>petter</dc:creator>
    <dc:date>2018-05-29T13:06:29Z</dc:date>
    <item>
      <title>Qliksense: URL Encoding ($=%24)</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/24614#M377</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Folks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Iam facing a problem with the automatic encoding of links (URL) in a Qliksense Table Chart.&lt;/P&gt;&lt;P&gt;We are using Navision as ERP System.&lt;/P&gt;&lt;P&gt;If you build a link that should open a Tab from Navision, it usually contains a '$' (Dollar Sign) in the link.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Something like this: &lt;EM&gt;...your$company\runpage?page=...&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you now click on the link, it will open the $ as %24, which is no problem for Website links, but for Navision it is.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So i tried to put chr(36) instead of $, to maybe solve the Problem, but that didnt help either.&lt;/P&gt;&lt;P&gt;This problems only accure with Chrome, Firefox, Opera browser, in IE it works, but since QS is optimized for Chrome, i dont want to switch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anybody has a solution?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Greetz Lukas&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nachricht geändert durch Lukas Amann&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 May 2018 11:28:47 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/24614#M377</guid>
      <dc:creator>luke1986</dc:creator>
      <dc:date>2018-05-29T11:28:47Z</dc:date>
    </item>
    <item>
      <title>Re: Qliksense: URL Encoding ($=%24)</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/24615#M378</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Chr(36) is $ .... Chr(39) is not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Was it a typo?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 May 2018 13:06:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/24615#M378</guid>
      <dc:creator>petter</dc:creator>
      <dc:date>2018-05-29T13:06:29Z</dc:date>
    </item>
    <item>
      <title>Re: Qliksense: URL Encoding ($=%24)</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/24616#M379</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yea sorry, just a typo &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp; I will fix that.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 May 2018 13:09:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/24616#M379</guid>
      <dc:creator>luke1986</dc:creator>
      <dc:date>2018-05-29T13:09:03Z</dc:date>
    </item>
    <item>
      <title>Re: Qliksense: URL Encoding ($=%24)</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/24617#M380</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please contact Qlik Support. From my side, I've seen a scenario where &amp;amp;pi was interpreted as π by the client side JavaScript code in Qlik Sense but this should be fixed in Qlik Sense February 2018. So if the behavior is presenting the past that build for your scenario then there is a potential defect there.&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 May 2018 14:37:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/24617#M380</guid>
      <dc:creator>Levi_Turner</dc:creator>
      <dc:date>2018-05-31T14:37:04Z</dc:date>
    </item>
    <item>
      <title>Re: Qliksense: URL Encoding ($=%24)</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/24618#M381</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="font-size: 13.3333px;"&gt;Iam running the newest Version of Qliksense, so that shouldnt be a problem.&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;Its not wrong per se, it is just the URL encoder which makes it to a %24.&amp;nbsp; &lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;I solved the problem by using a Branch Add on called "simple table". Which at least interpret the $ as Dollar sign.&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;But you are right, i think a supp ticket might help, i will try that to. &lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;Greetz Lukas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 May 2018 15:55:50 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/24618#M381</guid>
      <dc:creator>luke1986</dc:creator>
      <dc:date>2018-05-31T15:55:50Z</dc:date>
    </item>
    <item>
      <title>Re: Qliksense: URL Encoding ($=%24)</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/24619#M382</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Update, this is what Qlik R&amp;amp;D wrote me:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt; font-family: 'Calibri',sans-serif;"&gt;&lt;STRONG&gt;--&amp;gt;&amp;nbsp; bug-fix is targeted for Qlik Sense November 2018.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt; font-family: 'Calibri',sans-serif;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt; font-family: 'Calibri',sans-serif;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt; font-family: 'Calibri',sans-serif;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt; font-family: 'Calibri',sans-serif;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Sep 2018 11:44:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/24619#M382</guid>
      <dc:creator>luke1986</dc:creator>
      <dc:date>2018-09-26T11:44:58Z</dc:date>
    </item>
    <item>
      <title>Re: Qliksense: URL Encoding ($=%24)</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/24620#M383</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just faced the same problem here. &lt;/P&gt;&lt;P&gt;Thanks for reaching out to them - frustrating to see them take so long to respond.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Oct 2018 18:22:46 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/24620#M383</guid>
      <dc:creator>william_fu</dc:creator>
      <dc:date>2018-10-08T18:22:46Z</dc:date>
    </item>
    <item>
      <title>Re: Qliksense: URL Encoding ($=%24)</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/24621#M384</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Same problem here. We we had successfully linked to OpenAir (NetSuite/Oracle) invoices from Qlik before the June 2018 release. It has been broken since then, and we look forward to the fix in the November 2018 release!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FYI, there's what appears to be a somewhat related threat at &lt;A href="https://community.qlik.com/thread/313071"&gt;Qlik Sense June 2018 - URL address cut at "equal" (%3D)&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Nov 2018 14:48:24 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/24621#M384</guid>
      <dc:creator>kwdaniels</dc:creator>
      <dc:date>2018-11-01T14:48:24Z</dc:date>
    </item>
    <item>
      <title>Re: Qliksense: URL Encoding ($=%24)</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/1552888#M10118</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I just upgrated from Feb 2018 to Qliksense Nov 2018 version. Now we are facing the same URL problem. Actually i am using some angularjs method in mashup javascript file. Now it is not working due to URL encoding automatically. Is there any solution for this issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2019 11:33:23 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/1552888#M10118</guid>
      <dc:creator>microland</dc:creator>
      <dc:date>2019-03-06T11:33:23Z</dc:date>
    </item>
    <item>
      <title>Re: Qliksense: URL Encoding ($=%24)</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/1583165#M10603</link>
      <description>Seems like it still hasn't been implemented as of Feb 2019.</description>
      <pubDate>Wed, 22 May 2019 08:50:40 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/1583165#M10603</guid>
      <dc:creator>Aladdin</dc:creator>
      <dc:date>2019-05-22T08:50:40Z</dc:date>
    </item>
    <item>
      <title>Re: Qliksense: URL Encoding ($=%24)</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/1657453#M11997</link>
      <description>&lt;P&gt;I have a similar problem with URLs in Qlik Sense. Part of the URL I am using is "type=&amp;amp;M=414". Qlik Sense translates this as "type&amp;amp;M=414", in other words the equal sign that don't have any content is removed. I have also tried with the chr() function but without luck. Are there any news regarding solutions to this or similar issues?&lt;/P&gt;</description>
      <pubDate>Fri, 13 Dec 2019 09:08:41 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qliksense-URL-Encoding-24/m-p/1657453#M11997</guid>
      <dc:creator>heltok</dc:creator>
      <dc:date>2019-12-13T09:08:41Z</dc:date>
    </item>
  </channel>
</rss>

