Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I know QlikView support JSON like data source but not natively. Is this functionality implemented in Qlik Sense?
BR
Hello Efrain - take a look at this video I just posted and see if this helps you out for the time being:
Qlik Sense Desktop - Using QVSource Data Connectors (video)
QVSource has a JSON web connector
Regards,
Mike T
Currently the Qlik Sense ships with connectivity to flat files, ODBC, OLE and Web files. Other connectors can be added (they would appear under "Custom Connectors"). Qlik will be continuing to develop additional connectivity. We also anticipate our partner to create connectors, just like with QlikView.
Hello Efrain - take a look at this video I just posted and see if this helps you out for the time being:
Qlik Sense Desktop - Using QVSource Data Connectors (video)
QVSource has a JSON web connector
Regards,
Mike T
It is possible to use the Web file option in the Data connections. I was able to test and load using the Northwind ODATA source available http://services.odata.org/Northwind/Northwind.svc/Orders
I defined the Web File and load data from using the following scripts. I used the wizard and edited it as required.
For Example see the below script.
tblOrders:
Load
OrderID,
CustomerID,
EmployeeID,
OrderDate,
RequiredDate,
ShippedDate,
ShipVia,
Freight,
ShipName,
ShipAddress,
ShipCity,
ShipRegion,
ShipPostalCode,
ShipCountry ;
LOAD
// id,
// updated,
// "content/type",
"content/properties/OrderID" as OrderID,
"content/properties/CustomerID" as CustomerID,
"content/properties/EmployeeID" as EmployeeID,
"content/properties/OrderDate" as OrderDate,
"content/properties/RequiredDate" as RequiredDate,
"content/properties/ShippedDate" as ShippedDate,
"content/properties/ShipVia" as ShipVia,
"content/properties/Freight" as Freight,
"content/properties/ShipName" as ShipName,
"content/properties/ShipAddress" as ShipAddress,
"content/properties/ShipCity" as ShipCity,
"content/properties/ShipRegion" as ShipRegion,
"content/properties/ShipPostalCode" as ShipPostalCode,
"content/properties/ShipCountry" as ShipCountry
// "content/properties/ShipPostalCode/m:null",
// "content/properties/ShipRegion/m:null",
// "content/properties/Freight/m:type",
// "content/properties/ShipVia/m:type",
// "content/properties/ShippedDate/m:type",
// "content/properties/RequiredDate/m:type",
// "content/properties/OrderDate/m:type",
// "content/properties/EmployeeID/m:type",
// "content/properties/OrderID/m:type",
// "category/term",
// "category/scheme",
// %Key_feed_353A984E43E5258F,
// %Key_entry_DBF4DB52A7786704
FROM 'lib://NWOrders'
(XmlSimple, table is [feed/entry]);
That is a great approach, another example where it is great to have the scripting capability available to those who need it. Please note that we are discussing the best approach to handle and flatten JSON data without using the scripted method.
Thanks for your contribution Shiva!
Mike T
Michael,
I see this is an old comment, did this discussion allready lead to a standar way to import JSON data into Qliksense without the need for 3° party connectors?
Jasper
Have you already had a look at the REST connector?
Hi Jasper - check this out as well:
QlikView - Using the REST Connector - Qlik Sense as well