Qlik Sense does not show rows with exactly the same data

[vaisgaard]

Hi,

Today I discovered an odd thing in Qlik Sense.

I have a dataset where there are some rows that are exactly the same. All columns and data are the same for two rows. The dataset consists only of one table and no data modelling is done.

If I do a table with only dimensions (no aggregation), I only get one row of two. If I sum the data (amount paid), I get the sum of both rows.

I have checked the app in 3 different environments (prod, test and desktop) - all with the same result. 

Can anyone of you explain this, and more importantly how can I fix this behaviour?

Thank you.

P.S. I can't share the dataset, as it is highly sensitive.

[mikaelsc]

qlik will only show unique values. 

add a differentiating field to your model and your table... you'll get what you want 

(for example rowno() as UniqueRecID, )

[vaisgaard]

Thank you @mikaelsc 

Do you know if this is a feature in Qlik Sense? Can it be found in the documentation?

I am asking because I think it is odd to create this behaviour. I do not like when a programme "hides" data without me asking it to do so.

---

[marcus_sommer · Accepted solution]

It's one of the main-features of Qlik that only distinct values are displayed in objects. It has nothing to do with hiding data else the data are intentionally stored in this way because Qlik follows no SQL-like row-based storing else it's a column-based storing and this leads to a significantly better performance.

If there is any reason to validate the data against the source-data (usually only during the development) it's useful to follow the suggestion from @mikaelsc to add recno() and/or rowno() to the loads - but after that they won't be needed respectively they become a disadvantage.

- Marcus

[kgordis]

I **bleep** near lost my mind because of this issue. Starting screaming because I wanted to pre filtered the data and knew I had two rows but it was only showing one and blanking out cells 

I ended up joining two columns so names would be unique. Not ideal but solved problem.

Program A + Event 1

Problem  A + Event 2.

So Annoying. Rather just have Probram and Event on separate columns. 

[marcus_sommer]

Like above already mentioned it's not an issue else it's the target. The main-purpose of a BI tool is to show insights and pattern on consolidated data and not displaying them on a record-level. That the views display aggregated data make it very obvious that there are more or less duplicates underlying.

In regard to your shown concatenation of two fields you would get the same view if you use both fields as dimensions within the charts.