Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Is there any way to store the data into XML (just like qvd)?
If so, how?
The second poster was correct on this one, here is the Help link behind things:
The only thing of which I can think would be to store to CSV and then if you have a third-party utility that can convert, you could use that, and you could write a .bat or .cmd and use Publisher to run that as a support task, best I idea I have on this one.
Regards,
Brett
XML is not available.
You can save it as a csv file.
store mytable into myfile.txt (txt);
You could try it with qvx like:
store table into table.qvx (qvx);
- Marcus
The second poster was correct on this one, here is the Help link behind things:
The only thing of which I can think would be to store to CSV and then if you have a third-party utility that can convert, you could use that, and you could write a .bat or .cmd and use Publisher to run that as a support task, best I idea I have on this one.
Regards,
Brett
Hi there,
We've made 2 years ago a dynamic script that is creating an XML file, according to a tree structure definition, read from a set of 2 definition tables (XMLtables and XMLfields).
It is using to store as a "fake" CSV, that actually has a full XML inside.
Not always giving a perfect result ...
So we had to run an additional PY script to clean some messy characters afterwards.
(Can create JSON as well)
We are using this to create, quite fast, pretty big SAF-T.XML files.
(Still tinkering from time to time)
If somebody needs a Qlik script for creating complex XML or JSON , let us know !
Sempre fi,
C
Hi @cotiso_hanganu ,
I'd be very interested to see how you build the script for creating a complex XML. I sent you a private message.
Kind regards,
Marijn
Marijn was asking for help... they had a Qlikview environment where they did the solution previuoulsy mentioned. But after moving to Qlik Sense, they faced some issues in reusing the same approach.
Following is my answer, perhaps it is of use for others ,as well:
Is it Sense Client Managed or Saas you are working now with ?
If it is On Prem (Desktop/Server) you can still use the old ways, just convert to Scripting Legacy Mode.
If it is SaaS or you don't want server running in Legacy Mode, you could use a Sense Desktop licensed from SaaS/OnPrem in Legacy Mode to do the CSV + BAT post processing for XML. (Or perhaps a 2nd server in a Qlik Sense Server Cluster that is in legacy mode, but I am not sure if you can have a mixed Standard-Legacy Mode in a Cluster)
Have a look also at the new Qlik functions GetJson / SetJson that might help you create a JSON file that maybe can replace the XML... or use a JSON to XML convertor afterwards....