Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I've loaded data into a QVD file and the fields I need show up in the table viewer. When I go to load the data from the QVD file into a QVW report file, I get the "Field Not Found" error. So, I started removing the fields until I had none left - each and every field is not found by the file.
I am new to this company. Surprisingly, the people whom have been using and developing with Qlikview for the past couple of years don't seem to understand how it works. That leaves me, New Guy, to figure it out. Here's their process for getting data into the files:
I'm assuming this is how most companies to do this (?).
Here's the thing - when I examine the contents of the QVD files I see the fields I need in the QVD files and they are there. I do this by opening the QVW file and taking a look at the table viewer. I do not understand, if they are in the QVD, why the QVW file i'm trying to import them into says that they do not exist?
Here is the very simple script i'm using just to test and get this figured out:
LOAD
gp_ref_number
,gp_referral_amount
FROM $(Path)qv_metrics(qvd)
And here is the error i'm getting:
Field not found - <gp_ref_number>
LOAD
gp_ref_number
,gp_referral_amount
FROM .\qvd\current\qv_metrics.qvd(qvd)
So, what the heck could be causing this issue? It's very irritating and i'm hoping it's simple.
Hey All,
Thanks for the replies. We seem to have figured this out, and I think it's just related to how they have their QVD files set up.
Here's what's going on (in case someone else might have this problem):
When creating a new SQL view to pull data from the server into Qlikview, the team was creating a new QVD for that specific view - they call it a CREATOR_<metricname>.qvd. In our case there are 10 different CREATOR QVDs, each for a specific SQL view. I created a new CREATOR QVD to call the new view which I also created on SQL Server, then I added the new fields to each corresponding CREATOR QVD.txt file. The problem occurred when I didn't do a reload of ALL TEN CREATOR QVD files, instead I just did a reload of the new file. This caused the new fields to not return in the QVW report file.
Confusing, I know, and i'm not sure if their Qlikview environment is architected correctly or optimally. My next move is to figure out the best way of doing this
Thanks for the help.
It looks that you either stored the qvd not correct or your load-statement isn't quite right. It should look like:
store table into filename.qvd (qvd);
and
Load * From filename.qvd (qvd);
Important is the (qvd) as file-format.
- Marcus
Try a load * of the qvd and double check what field names that brings in.
Do you have use relative path selected?
Check your Path variable. It probably needs two dots at the beginning.
Hey All,
Thanks for the replies. We seem to have figured this out, and I think it's just related to how they have their QVD files set up.
Here's what's going on (in case someone else might have this problem):
When creating a new SQL view to pull data from the server into Qlikview, the team was creating a new QVD for that specific view - they call it a CREATOR_<metricname>.qvd. In our case there are 10 different CREATOR QVDs, each for a specific SQL view. I created a new CREATOR QVD to call the new view which I also created on SQL Server, then I added the new fields to each corresponding CREATOR QVD.txt file. The problem occurred when I didn't do a reload of ALL TEN CREATOR QVD files, instead I just did a reload of the new file. This caused the new fields to not return in the QVW report file.
Confusing, I know, and i'm not sure if their Qlikview environment is architected correctly or optimally. My next move is to figure out the best way of doing this
Thanks for the help.