<?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: JSON from REST endpoint assumes wrong form (Qlik Sense Enterprise for Windows) in Connectivity &amp; Data Prep</title>
    <link>https://community.qlik.com/t5/Connectivity-Data-Prep/JSON-from-REST-endpoint-assumes-wrong-form-Qlik-Sense-Enterprise/m-p/2515489#M14833</link>
    <description>&lt;P&gt;Hello Rob,&lt;BR /&gt;&lt;BR /&gt;thank you for your answer!&lt;BR /&gt;&lt;BR /&gt;As far as I know the JSONGet() works for for inline JSON data and .json files loaded directly from a drive / folder connection.&lt;BR /&gt;How would I use this on the REST Connector?&lt;BR /&gt;&lt;BR /&gt;Also this unfortunately kind of defeats my purpose as I don't want to hardcode the fields that are useful to extract from the response, but rather get the complete JSON response to begin with before doing anything to it.&lt;BR /&gt;The JSON response is subject to change, so hardcoding fields is not really a viable option as there might be more fields/arrays added or removed.&lt;BR /&gt;&lt;BR /&gt;As a little bonus: I'm not allowed to use anything other than Qlik Sense, so no parsing beforehand via external script etc...&lt;BR /&gt;&lt;BR /&gt;Best regards&lt;/P&gt;</description>
    <pubDate>Wed, 23 Apr 2025 15:18:59 GMT</pubDate>
    <dc:creator>NoNameFound</dc:creator>
    <dc:date>2025-04-23T15:18:59Z</dc:date>
    <item>
      <title>JSON from REST endpoint assumes wrong form (Qlik Sense Enterprise for Windows)</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/JSON-from-REST-endpoint-assumes-wrong-form-Qlik-Sense-Enterprise/m-p/2515448#M14828</link>
      <description>&lt;P&gt;I've stumbled upon the following problem recently:&lt;BR /&gt;When I load JSON data through the Qlik Sense REST Connector from an endpoint, the format of the data I get back is defined by the first entry in the response, at least I feel like that's the case.&lt;BR /&gt;&lt;BR /&gt;When the first entry in the response body contains a sub-array with no data, the script automatically assumes that this is the case for that specific sub-array in the following entries aswell, meaning I have no chance to know wether my load is complete and structurally sound when loading JSON through the REST connector.&lt;BR /&gt;&lt;BR /&gt;When the first entry of the response contains an empty sub-array, there will be no table created for it, regardless of the following entries having data in said sub-array.&lt;BR /&gt;&lt;BR /&gt;I would love to have a native way to parse JSON rather than explicitly parse everything out myself or lose data by Qlik interpreting empty sub-arrays as null in the first response entry and subsequently every entry that follows.&lt;BR /&gt;&lt;BR /&gt;Our temporary workaround is having a dummy entry return as the first entry with complete (albeit dummy) data incl. sub-arrays, so the tables are created.&lt;BR /&gt;&lt;BR /&gt;Has anyone else encountered this problem?&lt;/P&gt;</description>
      <pubDate>Wed, 23 Apr 2025 12:49:15 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/JSON-from-REST-endpoint-assumes-wrong-form-Qlik-Sense-Enterprise/m-p/2515448#M14828</guid>
      <dc:creator>NoNameFound</dc:creator>
      <dc:date>2025-04-23T12:49:15Z</dc:date>
    </item>
    <item>
      <title>Re: JSON from REST endpoint assumes wrong form (Qlik Sense Enterprise for Windows)</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/JSON-from-REST-endpoint-assumes-wrong-form-Qlik-Sense-Enterprise/m-p/2515468#M14830</link>
      <description>&lt;P&gt;"&lt;SPAN&gt;I would love to have a native way to parse JSON..."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;You may be able to parse as you want using &lt;A href="https://help.qlik.com/en-US/sense/November2024/Subsystems/Hub/Content/Sense_Hub/Scripting/StringFunctions/JsonGet.htm" target="_blank" rel="noopener"&gt;JsonGet() function&lt;/A&gt;. For example:&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;Raw:&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;Load * Inline [&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;json&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;"{"invoice": 123, "items": [{"item": "bread"}, {"item": "jam"}]]}"&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;"{"invoice": 456, "items": [{"item": "pants"}, {"item": "shoes"}, {"item": "socks"}]]}"&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;];&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;Data:&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;LOAD&amp;nbsp;&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;SPAN&gt;&amp;nbsp; JsonGet(json, '/invoice') as Invoice,&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;&lt;SPAN&gt;&amp;nbsp; JsonGet(json, '/items/*/item') as item&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face="courier new,courier"&gt;Resident Raw;&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="rwunderlich_0-1745417591419.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/179855i6EB4A57D5B5C2156/image-size/medium?v=v2&amp;amp;px=400" role="button" title="rwunderlich_0-1745417591419.png" alt="rwunderlich_0-1745417591419.png" /&gt;&lt;/span&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;-Rob&lt;BR /&gt;&lt;A href="http://www.easyqlik.com" target="_blank"&gt;http://www.easyqlik.com&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://masterssummit.com" target="_blank"&gt;http://masterssummit.com&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://qlikviewcookbook.com" target="_blank"&gt;http://qlikviewcookbook.com&lt;/A&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 23 Apr 2025 14:15:19 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/JSON-from-REST-endpoint-assumes-wrong-form-Qlik-Sense-Enterprise/m-p/2515468#M14830</guid>
      <dc:creator>rwunderlich</dc:creator>
      <dc:date>2025-04-23T14:15:19Z</dc:date>
    </item>
    <item>
      <title>Re: JSON from REST endpoint assumes wrong form (Qlik Sense Enterprise for Windows)</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/JSON-from-REST-endpoint-assumes-wrong-form-Qlik-Sense-Enterprise/m-p/2515489#M14833</link>
      <description>&lt;P&gt;Hello Rob,&lt;BR /&gt;&lt;BR /&gt;thank you for your answer!&lt;BR /&gt;&lt;BR /&gt;As far as I know the JSONGet() works for for inline JSON data and .json files loaded directly from a drive / folder connection.&lt;BR /&gt;How would I use this on the REST Connector?&lt;BR /&gt;&lt;BR /&gt;Also this unfortunately kind of defeats my purpose as I don't want to hardcode the fields that are useful to extract from the response, but rather get the complete JSON response to begin with before doing anything to it.&lt;BR /&gt;The JSON response is subject to change, so hardcoding fields is not really a viable option as there might be more fields/arrays added or removed.&lt;BR /&gt;&lt;BR /&gt;As a little bonus: I'm not allowed to use anything other than Qlik Sense, so no parsing beforehand via external script etc...&lt;BR /&gt;&lt;BR /&gt;Best regards&lt;/P&gt;</description>
      <pubDate>Wed, 23 Apr 2025 15:18:59 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/JSON-from-REST-endpoint-assumes-wrong-form-Qlik-Sense-Enterprise/m-p/2515489#M14833</guid>
      <dc:creator>NoNameFound</dc:creator>
      <dc:date>2025-04-23T15:18:59Z</dc:date>
    </item>
  </channel>
</rss>

