Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
krishna20
Specialist II
Specialist II

How to Remove Duplicate Names

Hi Folks,

I'm having Employee_ID which is Identical but Employee_Name getting duplicates from Database itself.I need to restrict it in the Qlikview script .how can we achieve it? Please anyone suggest me. Please find the attached image.

Regards

Krishna

14 Replies
jonathandienst
Partner - Champion III
Partner - Champion III

It looks like EmployeeID is not the correct key to use for your dataset. Either the key must be a composite of several fields, or you could use the PersonID field, although that is better, it is still not unique. Anyway, I don't think your problem is the technical one of removing duplicates, it is rather the business question of what is the key and how is the data being extracted from the source system.

So you can muck about all you like trying to remove the duplicates, but you are solving the wrong problem.

Logic will get you from a to b. Imagination will take you everywhere. - A Einstein
krishna20
Specialist II
Specialist II
Author

Hi Jonathan,

Thank you very much me to think on dates. Exactly there is  dates mistake in the database.This Employee has resigned in the past and Joined again .So the Names are repeating but Employee_ID is the Distinct. This is a Instance Database of oracle.

Regards

Krishna

krishna20
Specialist II
Specialist II
Author

Hi Jonathan,

I'm not using Employee_ID as a key.I'm using Person _ID as a key.

jonathandienst
Partner - Champion III
Partner - Champion III

Person_ID is better, but is still not unique. I think you need an extract from your source system that does not produces these duplicate values. If you filter on EmployeeStatus = 'ACTIVE', does that produce unique records for PersonID?

I would examine the SQL query extracting the data. I suspect that there is a bad join in this somewhere. Focus on getting good source data from your source and then you will have less problems with loading and reporting.

Logic will get you from a to b. Imagination will take you everywhere. - A Einstein
krishna20
Specialist II
Specialist II
Author

Yes exactly Jonathan, There is a bad join which executed by oracle team in my company. I raised ticket regarding this. They have given a view which is exiting with duplicate data and not a unique Person_ID. Thank you once again Jonathan.