topic Re: Problem with long digit key column in QlikView

Problem with long digit key column

Fri, 07 Jun 2013 04:03:29 GMT

Hi All,

I am facing very strange issue.

This is my Load Statement.

Exp:

Load ExpRecID,

ExposureID,

BorrowerID;

Select ExpRecID, ExposureID,BorrowerID

From tblExposure;

Here, ExpRecID is an autogenerated number in table and it contains 18 digits. The values of ExpRecID is 100000000075607570, 100000000075607571,100000000075607572 etc etc. After loading, initially the ExpRecID list box is not showing any values. After adding Number format ################## (18), i can see the values but it is not showing all values. Actuallt ExpRecID and ExposureID are in 1 to 1 ratio.For each ExposureID, the corresponding ExpRecID exists. But the values are not coming properly in the dash board. I am using version 9.

ExpRecID is the key column and i have to use it in further joins. Please guide me to solve this issue. I have tried Text(). evaluate() etc but no use.

Attaching the required files now. Exp.csv is having the correct data.

Message was edited by: ManiKolli

Re: Problem with long digit key column

sushil353 — Fri, 07 Jun 2013 04:49:29 GMT

Try to use NUM() function.

HTH

Sushil

Re: Problem with long digit key column

Fri, 07 Jun 2013 04:58:39 GMT

Tried NUM() but not working. Getting some internal format number and is not inline with corresponding ExposureID.

Re: Problem with long digit key column

sushil353 — Fri, 07 Jun 2013 05:01:58 GMT

Please post the sample application.

Re: Problem with long digit key column

Fri, 07 Jun 2013 05:30:20 GMT

Attached the necessary files.

Re: Problem with long digit key column

sushil353 — Fri, 07 Jun 2013 05:41:11 GMT

Please find attached.

Is it what you are looking for?

HTH

Sushil

Re: Problem with long digit key column

Fri, 07 Jun 2013 05:53:23 GMT

ExpRecID values are not coming properly. Please cross check the ExpRecID values from Exp.csv. I need that values. QV is displaying some default things. For each ExposureID, there should be a matching unique ExpRecID which is not happening here.

Re: Problem with long digit key column

sushil353 — Fri, 07 Jun 2013 05:59:45 GMT

Is this Exp.csv is the data file for your..?

is your UI issue is resolved?

Re: Problem with long digit key column

sushil353 — Fri, 07 Jun 2013 06:03:59 GMT

I loaded data from the CSV file..

It is showing correct relation... check your data source.. it might be the datasource issue.

HTH

Sushil

Re: Problem with long digit key column

Fri, 07 Jun 2013 06:12:34 GMT

Thanks a lot sushil,yes..here data is loading properly. But my source is SQL table , not csv file.

For your refernce, i have loaded the sample data into a csv file as i can not share the table data.

Re: Problem with long digit key column

sushil353 — Fri, 07 Jun 2013 06:16:27 GMT

Try to load your data again and remove the "num(ExpRecID) as ExpRecID_Temp2";

i dont think that is required for you..

and if your issue is resolved then please close this thread by making it correct answered so that other will get benefited too.

HTH

Sushil

Re: Problem with long digit key column

Fri, 07 Jun 2013 06:23:10 GMT

No Sushil, the issue is not resolved. When i load the data from table, i am getting the same issue. values are not coming properly. If possible, it would be create if you create a sample table with data as given in csv file and check from your end.

I have given the Exp.csv file, by selecting sample records from table. But as per the requirement, i have to load from a table itself.

Re: Problem with long digit key column

sushil353 — Fri, 07 Jun 2013 06:28:04 GMT

I have loaded data from csv file which is correct..

try one thing..Use the below query and see if it is working or not

Exp:

LOAD BorrowerID,

ExposureID,

ExpRecID;

SQL SELECT BorrowerID,

ExposureID,

ExpRecID

FROM "GEC_PRO".dbo.tblExposure

where siteid='5451'and periodid='201212';

Re: Problem with long digit key column

Fri, 07 Jun 2013 06:37:51 GMT

while extracting from table, Cast(ExpRecID as VarChar(50)) as ExpRecID solves the issue.

Now the issue is resolved.