Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
No1:
SQL SELECT assetno,
assetshortdesc,
"org_date",
"orig_priority",
originator,
"plan_priority",
wo,
"work_type"
FROM MainSaver11.dbo.wkaw;
store No1 into No1.qvd(qvd);
drop table No1;Directory;
LOAD assetno,
assetshortdesc,
date (org_date) as org_date,
orig_priority,
upper (originator) as originator,
plan_priority,
wo,
work_type
FROM
No1.qvd
(qvd)
WHERE(org_date >= '01/01/2013')
and left (wo,1)<>'P' and left (wo,1)<>'T';No2:
SQL SELECT "login_id",
wo
FROM MainSaver11.dbo.wkaws;
store No2 into No2.qvd(qvd);
drop table No2;Directory;
LOAD login_id,
wo
FROM
No2.qvd
(qvd);
Hi,
I am very new to Qlikview, so please be patient
I have loaded my data into Qlkiview (see above), but have just come up against a problem with duplication of records.
I know why this is, but I am unsure how to to go about fixing it.
I have loaded data from a call logging system and for every call logged a unique reference number is created.
When a call is logged the system logs the users LOGIN ID name details. Then for every time a user makes a change to the call (for example completes or closes the call) the system logs the users LOGIN ID name again.
Qlikview is currently showing me (for example) x3 of each unique reference number and a different LOGIN ID for each time a change was made.
How do I get Qlkiview to only show me the first initial record of the LOGIN ID on creation of the job, not the each individual change?
I hope this makes sense.
Please let me know if there is anything else I can attach to help you answer my question.
FYI - I have attached an image of both tables I am using.
Thanks
Susan,
Now we can do one of a thousand things, all of them with limited chance of success. And the fact that I have no access to any of your data, applications or scripts makes it very time-consuming to debug your QlikView app, as you can see from the size of this thread.
Would it be possible to post or email a complete or partial WKAWS.qvd? IMHO the problem is still situated in the code that handles wo's and login_id's from this table.
Peter