As one of the primary file types used by technologists it is so frustrating that people are still having to use the likes of XLSX or CSV to hold app configuration. XML is archaic.
It is simply to add JSON files to the standard Load capability of Qlik Sense.
I remember listening to technology people in a previous job way back in 2014 saying they would not touch QlikView because of lack of direct JSON support. It is now 2021 and nothing has appeared for Qlik Sense, so again projects being promoted and managed by tech teams might question "why ?".
I think any registered user can create ideas - not sure why Qlik would want to restrict that - @Meghann_MacDonald ? PS I am neither a partner or a luminary.
Hi @devan9876 and @AndrewMcIlwrick , the ideas board is open to view and like from everyone with an account, but in order to post an idea you need to be a customer, partner, luminary etc. Registering with your Qlik customer account allows you access.
I used Power BI Desktop to manipulate the JSON exported from Qlik CLI when doing a Client-Managed to SaaS migration recently. Mad that I have to use another tool to interrogate the data Qlik CLI provides as Qlik Sense does not support JSON file formats...
Agree 100% @Carl_Hunter it is one of the primary weaknesses of the Qlik Sense platform. Years old and no visible solution. So much of our infra config is built on JSON and we need powershell scripts to pre-process them.
I tried to load WebConnectors logs into Qlik yesterday and realized that Qlik's support for xml is pretty obsolete as well... It deserves some love (or QWCs logs should be in a different format)