Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
slihp67
Contributor
Contributor

Duplicate rows being grouped

Hi 

New to qlik technology so forgive if I'm being a bit dumb. I've scripted a table into my model and want to display the fields in a table object. the table coming in is basically a list of users account codes. Some account codes can appear more than once but qlik sense is grouping these duplicates automatically which can be seen by the row count values. In this particular model, I don't want this behaviour, is there away to get sense to display all the values in a table including duplicates as if you were querying a database on the field?

 

thanks.

1 Solution

Accepted Solutions
rubenmarin

Teh first option is to create another field.

About the dual: Yes, it's to be created directly in the table. If you have a table you should have added some fields, this fields can be a dimension (segmentates data, like Category, Name) and metrics (calculates values, like sum(Amount), Count(Names))... instead of add a simple field you can edit it to be an expression.  If it is done in a dimension it is called a calculated dimension.

Dual() creates a values wich first parameter is the value shown and the second parameter is the internal value so you can show the same string different times because every string has a different internal value.

View solution in original post

5 Replies
Vegar
MVP
MVP

What you are experiencing is native Qlik Sense behaviour it is not something that you can disable. You need to add an row unique dimension to your table, eg. RowID, then your duplicate account codes will display as you intend. 

 

rubenmarin

Hi, the easy way can be adding a RowNo() field in script so each row will have a different number, in LOAd sentence add:

LOAD 
  RowNo() as RowNumber,
  //List of fields
// FROM /Resident...

And add this new RowNumber field in table so each value will ahve it's row.

Another option to avoid to add a column with row number is using Dual as a calculated dimension, instead of just NameField as dimension add the expression:

Dual(NameField, RowNumber)

slihp67
Contributor
Contributor
Author

Ok looks like qlik is the same as Power BI regarding this topic. Not sure what you mean with the DUAL option? are you meaning add a calculated field within the table inside qlick but not in the script? again sorry still getting lost in the terminology and the actual workings of the interface.

rubenmarin

Teh first option is to create another field.

About the dual: Yes, it's to be created directly in the table. If you have a table you should have added some fields, this fields can be a dimension (segmentates data, like Category, Name) and metrics (calculates values, like sum(Amount), Count(Names))... instead of add a simple field you can edit it to be an expression.  If it is done in a dimension it is called a calculated dimension.

Dual() creates a values wich first parameter is the value shown and the second parameter is the internal value so you can show the same string different times because every string has a different internal value.

slihp67
Contributor
Contributor
Author

ah ok thanks pal 👍