I totally forgot this was Qlik Sense discussion. But the idea might still work. Let me paste the script here:
CrossTable(Measurement, Data, 3)
[Price 1] & '|' & [Quantity 1],
[Price 2] & '|' & [Quantity 2]
(ooxml, embedded labels, table is Sheet1);
Replace(PurgeChar(SubField(Measurement, '|', 1), ''), ' & ' & Chr(39), '') as PriceType,
Replace(PurgeChar(SubField(Measurement, '&', -1), ''), ' & ' & Chr(39), '') as QuantityType,
SubField(Data, '|', 1) as Price,
SubField(Data, '|', 2) as Quantity
DROP Table Table;
it's not the load of the table itself, that is bothering me.
Later on in the script I do some calculations which are different dependent on the product and each record can contain info on each of the products. So I have to:
For every record check if it contains product A data; then do this
For every record check if it contains product B data; then do that
and so on
I think I already gained some speed because I decided to split the table and have to do the checking only once instead of several times (and by reducing the amount rows that I have to read not even containing any relevant data).
I was just wondering if I could gain some more speed, by being able to have the split in one go. But I see the point that a simple LOAD cannot provide this.
I think you are referring to a crosstable load, that pivots the column values into a single field.
You can do it and Michael made a helpful video on it for qlik sense users:
actually I am turning the data into a cross table further down the road to be able to do other things in the reporting itself. It's what I do (have to do) with the data before I can convert it to a cross table, that's bothering me and makes me wonder if a cross table what help at that point. But it's worth some additional thinking. I'll keep you updated, if it helped.