topic Re: Concatenate doing strange things in QlikView

Concatenate doing strange things

Thu, 12 Feb 2015 16:07:40 GMT

Struggling with this one....

My first stage is 2 concatenate 2 'CLIENT' tables

Then I load in 1 Address table

Everything at this stage is fine:-

Client ID	AddressNK
1001	AD4004
1001	AD4005

Then I concatenate another ADDRESS table from another source.

The link between the Client Table and Address Table appears ok in the Table viewer but when I in new Table charts to the tabs there are nulls showing..the link has dropped off.

AddressNK
1001	AD4004
1001	AD4005
1001	-

**I think what I am seeing here is the first 2 rows are actually data from the ADDRESS table, the 3rd row is data from the Client table which cannot seem to find the data in the Address table

Help please - totally stumped with this one.

Re: Concatenate doing strange things

Michiel_QV_Fan — Thu, 12 Feb 2015 16:12:06 GMT

Is it possible to attach (a sample / limited rows) of your data sources?

Re: Concatenate doing strange things

Thu, 12 Feb 2015 16:15:12 GMT

Unfortunately not due to the nature of the data

Re: Concatenate doing strange things

Michiel_QV_Fan — Thu, 12 Feb 2015 16:20:17 GMT

Can you post your script part?

Re: Concatenate doing strange things

rubenmarin — Thu, 12 Feb 2015 16:25:02 GMT

Hi Stuart, it's what you said in **, weird thing is this should happen when you concatenate the first address table.

ie:

Load from client --> this creates a row with Client Id unrelated to address

concatenate Load From address --> creates the 2 rows with Client related to address

Re: Concatenate doing strange things

Thu, 12 Feb 2015 21:28:28 GMT

Hi Ruben,

It's 2 address tables that are being concatenated thats the problem..

What I am expecting to happen is:

Load from Client = 1st entry created with nothing related

Load from Address = 1st entry from before now associated with 2 new address rows

It all works fine with the tables are not concatenated or joined. But as soon as I join or concatenate then I get this strange issue that I dont see with other data.