Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I have two tables I created via my load script using the crosstable statement for both. See below:
CrossQtr:
CROSSTABLE(Measure, QtrValue,5)
LOAD *
RESIDENT TempQtr;
CrossYr:
CROSSTABLE(Measure, YrValue,4)
LOAD *
RESIDENT TempYr;
[/CODE]
Both tables end up having several fields that are identical, except for the last field being QtrValue & YrValue. What I want to do is JOIN both tables into a single table. I used the following code but it ends up not doing anything:
<pre>
Data:
JOIN(CrossQtr) LOAD * RESIDENT CrossYr;
DROP TABLES CrossQtr, CrossYr;
Can anyone tell me what i'm doing wrong?
Very usefull, Thanks!
Aldo.
I have a similar case. Can you help me with this issue? The idea is have no synthetic keys.
[View:http://community.qlik.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/11/3835.Dash1.rar:550:0]
I can't unpack RAR files, and don't want to download software from the web onto my work computer in order to do so. Can you post it as a QVW? I believe that's already a compressed format.
Of course...There Goes Thanks...
On the surface, it looks like you could simply concatenate your tables together.
DIRECTORY C:\Documents and Settings\pgalvezt\Desktop\COMMAND CENTER\2 UNILEVER\BRAZIL\Proyecto\QVD;
MyData:
LOAD ... FROM FRETES_INBOUND.qvd (QVD);
CONCATENATE (MyData) LOAD ... FROM FATURA_DE_SERVIÇO.qvd (QVD);
CONCATENATE (MyData) LOAD ... FROM FATURAS.qvd (QVD);
CONCATENATE (MyData) LOAD ... FROM FRETES_OUTBOUND.qvd (QVD);
Or you might want to outer join, assuming that the synthetic key really can be considered the key to all of these tables. In that case, it's probably better to have one row for each key instead of four.
MyData:
LOAD ... FROM FRETES_INBOUND.qvd (QVD);
OUTER JOIN (MyData) LOAD ... FROM FATURA_DE_SERVIÇO.qvd (QVD);
OUTER JOIN (MyData) LOAD ... FROM FATURAS.qvd (QVD);
OUTER JOIN (MyData) LOAD ... FROM FRETES_OUTBOUND.qvd (QVD);
As an aside, I would also typically use a calendar table instead of having all of those date-related fields in the main data table(s). I'd just put a date in the main data table, and put the rest of the fields in the calendar table. It should work either way, though.
Hi John. Please could you send me a example with your data table explanation?
Basically my dashboard works fine. But i would like to see other examples and to have the better options.
I mention John, I'm working on a major project with one of my clients and I am in the final stages of automating their processes. That is, I think an application that automatically downloads files to csv format, and passes it to xls. Currently, I've created the QVD's, to perform incremental and through the server to perform daily recharges. These dashboards will be showing on screens LCDs 42 '. Dashboards really give you a bonus to the business.
[quote user="Pablo Gálvez T"]Please could you send me a example with your data table explanation?
I'm sorry, but I don't understand what you want. What do you want an example of? What do you want explained?
Function Concatenate was the solution to the problem. Thanks John. I needed an example of calendars but i think my calendar works fine 🙂