Very informative and useful. will use this field in my current project. we are dealing with json data and for that we had written python script to convert single column value into multi column.
Tx for sharing ! Do have some questions, Mike: 1. Where and how did you defined the customer_id as a key field between the original table and the new table ? 2. It seems to me that in case the JSON field has various subfields in different rows, there will be separate resident tables for each subset of subfields, while there is no more key to the main table. Is it the right behaviour to be expected ? 3. It seems to me that in case one row has the JSON cell empty , there will be a "file not found error" => perhaps the error handling need some improvements ? 4. Should FROM_FIELD work in Qlikview, as well ? Tx
First question has the answer in the video, actually: in the demo, the JSON contains, redundantly, the CustID that is also as a structured field within the original table.What should be done in case it's not!? First idea was to add to JSON also the extra Key(s) , with a replace of the ending }, during the fist load.
Hi Eduardo - yes there should be identifier "XmlSimple" check this out: community.qlik.com/t5/New-to-Qlik-Sense/Loading-an-XML-field-in-SQL-Server-into-Qlik-Sense/td-p/25978
@pauljohansson4809 16 seconds ago (edited) from_field is very easy to use. In my case though, the performance was simply to poor. Do you have performance issues when unwraping using from_field? - look into doing on the DB side.
Hi Paul - from_field using JSON is sort of experimental and is not meant to be used large data prep or transformations. Depending on what you are doing there may be a better way.
Very inspired and important clarification regarding the CustID field pre-existing in the json. Tx
very useful, thanks
Very informative and useful. will use this field in my current project. we are dealing with json data and for that we had written python script to convert single column value into multi column.
Awesome - thanks for sharing!
Wow, very informative, will try morrow.
Tx for sharing !
Do have some questions, Mike:
1. Where and how did you defined the customer_id as a key field between the original table and the new table ?
2. It seems to me that in case the JSON field has various subfields in different rows, there will be separate resident tables for each subset of subfields, while there is no more key to the main table. Is it the right behaviour to be expected ?
3. It seems to me that in case one row has the JSON cell empty , there will be a "file not found error" => perhaps the error handling need some improvements ?
4. Should FROM_FIELD work in Qlikview, as well ?
Tx
Hi Cotiso - let's continue this conversation in the qlik community - please send me the thread when you are ready and I can address.
First question has the answer in the video, actually: in the demo, the JSON contains, redundantly, the CustID that is also as a structured field within the original table.What should be done in case it's not!? First idea was to add to JSON also the extra Key(s) , with a replace of the ending }, during the fist load.
Can i use the From_Field to parse XML files?
Hi Eduardo - yes there should be identifier "XmlSimple"
check this out:
community.qlik.com/t5/New-to-Qlik-Sense/Loading-an-XML-field-in-SQL-Server-into-Qlik-Sense/td-p/25978
it worked perfectly ty@@QlikOfficial
@pauljohansson4809
16 seconds ago (edited)
from_field is very easy to use. In my case though, the performance was simply to poor. Do you have performance issues when unwraping using from_field? - look into doing on the DB side.
Hi Paul - from_field using JSON is sort of experimental and is not meant to be used large data prep or transformations. Depending on what you are doing there may be a better way.