Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Data being altered from original source

Can anyone assist or has seen this before.

I am extracting data from a FoxPro table via ODBC.

Some data, in this isntance a serial number field is having a 0 (zero) appended to the fron of the serial no (see attached document)

Any help would be greatly appreciated.

1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

Hi,

When QlikView stores data in a field it references the first stored value for each repetition of this value, using the format of the first one.

Example:

Field X

001

01

1

QlikView will interpret all these values as 1, but it will show as 001 in the front end.

In your case you have loaded a number 0021 in the serial no field before you get to the 21 which is why it's represented as 0021.

If you need to have the 0021 represented as is, I would suggest using Text() around the field name to load the values as different values.

Otherwise I would suggest stripping leading zeros from the serial no values.

View solution in original post

2 Replies
Anonymous
Not applicable
Author

Hi,

When QlikView stores data in a field it references the first stored value for each repetition of this value, using the format of the first one.

Example:

Field X

001

01

1

QlikView will interpret all these values as 1, but it will show as 001 in the front end.

In your case you have loaded a number 0021 in the serial no field before you get to the 21 which is why it's represented as 0021.

If you need to have the 0021 represented as is, I would suggest using Text() around the field name to load the values as different values.

Otherwise I would suggest stripping leading zeros from the serial no values.

Not applicable
Author

Hi Johannes

Many thank for that information, wouldn't have found that in 100 years.

I guess it is an inbuilt "feature".

The base data field is character (varchar) so the data needs to be represented as text in its original format so the TEXT() solution worked great.

Now I am off to fix this on the rest of my reports.

Regards

Martin