<?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>article Qlik Sense: Column empty when loading data from JSON file in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Column-empty-when-loading-data-from-JSON-file/ta-p/2523394</link>
    <description>&lt;P style="font-weight: 400;"&gt;A JSON file is loaded into Qlik Sense by selecting data through the Select Data dialog. All data is visible, as expected:&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px" style="font-weight: 400;"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="select data prompt.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/181882i0F5FAB8700E9775B/image-size/large?v=v2&amp;amp;px=999" role="button" title="select data prompt.png" alt="select data prompt.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P style="font-weight: 400;"&gt;After loading data into the app, columns from the JSON file are now empty (null) in both the data model and data preview:&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px" style="font-weight: 400;"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="empty columns.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/181883iE154B7FCB6716CF0/image-size/large?v=v2&amp;amp;px=999" role="button" title="empty columns.png" alt="empty columns.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;DIV id="tinyMceEditorSonja_Bauernfeind_1" class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;H3 style="font-weight: 400;"&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P style="font-weight: 400;"&gt;There are multiple ways to resolve this issue:&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI style="font-weight: 400;"&gt;Avoid using &lt;EM&gt;dot&lt;/EM&gt; in JSON attribute names. .&lt;/LI&gt;
&lt;LI style="font-weight: 400;"&gt;Load JSON data with a wildcard. During wildcard load, the Analytics Engine will parse the JSON file and name the output columns, similar to the parsing done during the data select dialog preview. This approach loads all the columns from the JSON, so additional processing like a preceding load may be needed to limit the store data to the desired result.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Example:&lt;BR /&gt;
&lt;PRE&gt;LOAD resource.attributes.telemetry.sdk.language;&amp;nbsp; &amp;nbsp;&lt;BR /&gt;LOAD *&lt;BR /&gt;FROM [lib://DataFiles/example.json] (json);&lt;/PRE&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Cause&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN&gt;The Analytics Engine parses the JSON file during the data selection process and correctly finds all the attributes in the JSON file. The columns are named based on the attribute value and path in the JSON file.&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The JSON file in this case has value names containing the &lt;EM&gt;dot&lt;/EM&gt; character.&lt;/SPAN&gt;&lt;/P&gt;
&lt;PRE&gt;"resource": {&lt;BR /&gt;&amp;nbsp; &amp;nbsp;"attributes": {&lt;BR /&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp; &amp;nbsp;"telemetry.sdk.language": "python"&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;}&lt;BR /&gt;&amp;nbsp; &amp;nbsp;}&lt;BR /&gt;}&lt;/PRE&gt;
&lt;P&gt;&lt;BR /&gt;&lt;SPAN&gt;The Analytics Engine has no problem parsing this valid JSON structure. The generated script has explicit field names, including the value name in the JSON file.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;PRE&gt;LOAD&lt;BR /&gt;&amp;nbsp; resource.attributes.telemetry.sdk.language&amp;nbsp;&lt;BR /&gt;FROM [lib://DataFiles/example.json] (json);&lt;/PRE&gt;
&lt;P&gt;&lt;SPAN&gt;During load, the Analytic Engine interprets the explicit field name as a path to a&amp;nbsp;&lt;/SPAN&gt;language&lt;SPAN&gt; child within an&amp;nbsp;&lt;/SPAN&gt;SDK&lt;SPAN&gt; object, as this is what the dot separator indicates.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;As this path does not exist in the JSON file, the parser correctly returns NULL for the lookup.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;PRE&gt;"resource": {&lt;BR /&gt;&amp;nbsp; &amp;nbsp;"attributes": {&lt;BR /&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp; &amp;nbsp;"telemetry" : {&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp;"sdk": {&lt;BR /&gt;"language": "python"&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;}&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;}&lt;BR /&gt;&amp;nbsp; &amp;nbsp;}&lt;BR /&gt;}&lt;/PRE&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environment&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;UL&gt;
&lt;LI&gt;Qlik Cloud Analytics&lt;/LI&gt;
&lt;LI&gt;Qlik Sense Enterprise on Windows&lt;/LI&gt;
&lt;/UL&gt;</description>
    <pubDate>Tue, 08 Jul 2025 07:35:10 GMT</pubDate>
    <dc:creator>AllenChung6</dc:creator>
    <dc:date>2025-07-08T07:35:10Z</dc:date>
    <item>
      <title>Qlik Sense: Column empty when loading data from JSON file</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Column-empty-when-loading-data-from-JSON-file/ta-p/2523394</link>
      <description>&lt;P style="font-weight: 400;"&gt;A JSON file is loaded into Qlik Sense by selecting data through the Select Data dialog. All data is visible, as expected:&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px" style="font-weight: 400;"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="select data prompt.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/181882i0F5FAB8700E9775B/image-size/large?v=v2&amp;amp;px=999" role="button" title="select data prompt.png" alt="select data prompt.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P style="font-weight: 400;"&gt;After loading data into the app, columns from the JSON file are now empty (null) in both the data model and data preview:&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px" style="font-weight: 400;"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="empty columns.png" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/181883iE154B7FCB6716CF0/image-size/large?v=v2&amp;amp;px=999" role="button" title="empty columns.png" alt="empty columns.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;DIV id="tinyMceEditorSonja_Bauernfeind_1" class="mceNonEditable lia-copypaste-placeholder"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;H3 style="font-weight: 400;"&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P style="font-weight: 400;"&gt;There are multiple ways to resolve this issue:&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI style="font-weight: 400;"&gt;Avoid using &lt;EM&gt;dot&lt;/EM&gt; in JSON attribute names. .&lt;/LI&gt;
&lt;LI style="font-weight: 400;"&gt;Load JSON data with a wildcard. During wildcard load, the Analytics Engine will parse the JSON file and name the output columns, similar to the parsing done during the data select dialog preview. This approach loads all the columns from the JSON, so additional processing like a preceding load may be needed to limit the store data to the desired result.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Example:&lt;BR /&gt;
&lt;PRE&gt;LOAD resource.attributes.telemetry.sdk.language;&amp;nbsp; &amp;nbsp;&lt;BR /&gt;LOAD *&lt;BR /&gt;FROM [lib://DataFiles/example.json] (json);&lt;/PRE&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Cause&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN&gt;The Analytics Engine parses the JSON file during the data selection process and correctly finds all the attributes in the JSON file. The columns are named based on the attribute value and path in the JSON file.&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The JSON file in this case has value names containing the &lt;EM&gt;dot&lt;/EM&gt; character.&lt;/SPAN&gt;&lt;/P&gt;
&lt;PRE&gt;"resource": {&lt;BR /&gt;&amp;nbsp; &amp;nbsp;"attributes": {&lt;BR /&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp; &amp;nbsp;"telemetry.sdk.language": "python"&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;}&lt;BR /&gt;&amp;nbsp; &amp;nbsp;}&lt;BR /&gt;}&lt;/PRE&gt;
&lt;P&gt;&lt;BR /&gt;&lt;SPAN&gt;The Analytics Engine has no problem parsing this valid JSON structure. The generated script has explicit field names, including the value name in the JSON file.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;PRE&gt;LOAD&lt;BR /&gt;&amp;nbsp; resource.attributes.telemetry.sdk.language&amp;nbsp;&lt;BR /&gt;FROM [lib://DataFiles/example.json] (json);&lt;/PRE&gt;
&lt;P&gt;&lt;SPAN&gt;During load, the Analytic Engine interprets the explicit field name as a path to a&amp;nbsp;&lt;/SPAN&gt;language&lt;SPAN&gt; child within an&amp;nbsp;&lt;/SPAN&gt;SDK&lt;SPAN&gt; object, as this is what the dot separator indicates.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;As this path does not exist in the JSON file, the parser correctly returns NULL for the lookup.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;PRE&gt;"resource": {&lt;BR /&gt;&amp;nbsp; &amp;nbsp;"attributes": {&lt;BR /&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp; &amp;nbsp;"telemetry" : {&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp; &amp;nbsp;"sdk": {&lt;BR /&gt;"language": "python"&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;}&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;}&lt;BR /&gt;&amp;nbsp; &amp;nbsp;}&lt;BR /&gt;}&lt;/PRE&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environment&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;UL&gt;
&lt;LI&gt;Qlik Cloud Analytics&lt;/LI&gt;
&lt;LI&gt;Qlik Sense Enterprise on Windows&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Tue, 08 Jul 2025 07:35:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Column-empty-when-loading-data-from-JSON-file/ta-p/2523394</guid>
      <dc:creator>AllenChung6</dc:creator>
      <dc:date>2025-07-08T07:35:10Z</dc:date>
    </item>
  </channel>
</rss>

