Data is Doubling After QVD Loading - Qlik Community

Report Inappropriate Content · ‎2015-02-26

Hello All,

I'm new at this company and they are using Qlikview to report all of their metrics. I recently created a new fact table in the database and I had the reporting analysts verify that the numbers were correct straight from the table before importing them into Qlikview. However, after bringing the data from the new fact table into the QVDs, the data is doubled across the spectrum for all reports. I'm pretty sure that this is happening in the data model/table view and things aren't joining as they should, but we can seem to find the issue.

I'm just wondering - has this happened to any of you and how to did you resolve?

I'm pretty new to Qlikview and the analysts don't really seem to know how it works on the backend. In short, there is nobody here whom really knows the product very well. They are pointing at my team to figure this out, but i'm feeling blind here. Any help or advice would be appreciated.

Thanks!!

Anonymous · ‎2015-02-26

couple of things you could check:

1. see if there are any resident or otherwise loads where you load the same fields. a keyword "Noconcatenate" is a must or you are going to end up with a concatenated table with double the values.

2. just like you said there may be a bad join that you may have to look at.

is there a way you can post a sample app or may be the script here?

this post may help to make sure your client's data integrity is in tact without divulging any meaningful information - http://community.qlik.com/docs/DOC-4032

Report Inappropriate Content · ‎2015-02-26

I'm not quite sure what any of this means. I'm so new to Qlikview, and they want my team to take over the handling of the data and loading of QVDs. Nobody on my side knows nor understands how this all works. That being said, how am I supposed to fix their issue, then?

I'm either going to recommend that we get away from Qlikview and into something I understand or we're going to have to hire a Qlikview consultant to come in here and figure out what we're doing. Because nobody seems to know, and since I'm the new guy, I definitely don't know. We need some help with better knowledge, I think.

Report Inappropriate Content · ‎2015-02-27

Was it working before you created the new fact table ?

You'll need to examine the script in the QVW that produces the QVD file (Ctrl + E once you've opened it) and see where the import against the database table is happening. It may well be that the fact table you created, is already being calculated within the QVD before being imported to the main application making the fact table redundant and causing the double count.

There will be another qlikview application that produces the qvd being sucked into the main reporting application - so dig around for that and you'll probably quickly see in the script what the join is.

Anonymous · ‎2015-02-27

Hi Ave,

Check if you are loading same table twice. use 'Noconcatenate' keyword else will end up with a concatenated table , which results in duplicated values.

Drop unneccessary tables at end of the script.

Copy your script here ,so can help.

Regards

Neetha

kamalqlik · ‎2015-02-27

Hi Ave ,

This can be happen in case you are using the table twice and not using the no concatenate

or

it may be the due to join that are using.

We cant tell you like this ....

So please press Ctrl +T and take the screen-shot of your model and please paste the image here so we can look after it.

Regards

Kamal

Report Inappropriate Content · ‎2015-02-27

Hi Ave,

Happened to me when Dimension tables had duplicate IDs.

Going to Table view to see how the tables join to see if anything unusual has happened there such as synthetic joins then check dimension tables to see if there are duplicates in there which could cause 'doubling' up.

Useful Steve Dark post on inspecting data with Data Profiling.

Anonymous · ‎2015-02-27

i can certainly understand your position. however, for us to actually help troubleshoot your issue, we will need something to look at. there are some very good QV experts here who can point out the issue and if it is simple enough, you can fix it yourself with their help and if not, you can go with either of your two options. one thing to note though, if you move away from QV, you still have to learn the new software and start all over on your dashboard. just my 2 cents. good luck!