topic Re: Guesing the ScrambledHexCode for XML %KeyFieldNames in App Development

Guesing the ScrambledHexCode for XML %KeyFieldNames

cotiso_hanganu — Fri, 20 Oct 2023 21:33:13 GMT

Hi there,

I am trying to read some crazy XML files and it would realy help to identify the unique code Qlik's XML wizard is creating for each %Key_Field, but WITHOUT USING THE QLIK WIZARD !

Is there anyone in Qlik able to explain me the aglorithm used by the wizard to create the Hex codes like : %Key_AuditFile_87E72D7CCDAC9B8E

I assume is a kind of Hash applied some parts extracted from the XML, but cannot figure what.

In other words, I need to "gues" 87E72D7CCDAC9B8E while parsing some how the XML, but without using the Qlik wizard.

Tried with
Load * from File.XML (XMLsimple,table is XXX);
, but Qlik returns an error:

Load all (*) is not allowed in this file type

Re: Guesing the ScrambledHexCode for XML %KeyFieldNames

marcus_sommer — Mon, 23 Oct 2023 10:11:24 GMT

Should there be no hint from anyone you may consider a reverse approach by loading very simplified (dummy) xml-files with file/table/field-names of 'A' or 'B' or 1/2/3 and looking what happens especially if you change 'A' to 'B' or similar. Maybe any pattern is noticeable and/or you could compare the results with various common hash-algorithm.

Depending on the complexity of the xml-structures and your prediction of the containing data-set you may pre-load the file as a simple txt-file and applying various string-functions to detect the relevant table/field-names which you could use within a following final-load.

Re: Guesing the ScrambledHexCode for XML %KeyFieldNames

Ke_Sg — Wed, 22 Nov 2023 13:25:58 GMT

Hi,

It seems Qlik uses RipeMD-160 to hash the XML table name under the hood.

I have this example generated by the wizard :

LOAD %Key_Placemark_AA84FB6C10E27BB6
FROM [file.kml](XmlSimple, table is [kml/Document/Placemark]);

Using RipeMD-160 to hash "kml/Document/Placemark" return aa84fb6c10e27bb67290042a81d95e6be49054ae.

The file name, path, or file content doesn't matter. Qlikview and Qliksense will generate the same hash for the same XML table name.

However, I'm not sure it is possible to hash a string using RipeMD-160 in a pure Qlikview or Qliksense script.