Skip to main content
Announcements
Global Transformation Awards! Applications are now open. Submit Entry
cancel
Showing results for 
Search instead for 
Did you mean: 
cataldop
Contributor
Contributor

Differences in data displayed between Qlik Sense & QlikView from the same source and scripts?

We have migrated a Qlikview app to QlikSense and are using the same scripts and source data, however when we retrieve specific data in this QlikSense app some of the products are missing (not showing) in the app.

I created a separate app just for the products table and can see that they exist in the table.

Is there are setting or something different about the behavior of Qlik Sense that would cause some values to be hidden?

Thanks in advance

Paul

 

Labels (1)
3 Replies
henrikalmen
Specialist II
Specialist II

Basically: no, there should be no difference.

But it's kind of impossible to say why you experience differences. Either you haven't actually loaded the exact same data (start by comparing number of rows in each backend table in QlikView and QlikSense), or maybe you have written frontend expressions differently.

Muthukumar_77
Contributor III
Contributor III

Hi,

Are you using section access?

Thanks Regards,
Muthukumar P
Qlik Developer
lashworth
Luminary
Luminary

We have recently found that there is a profiling difference from QlikView to Qlik Sense.  This is happening to us with 2 types of fields dates (mainly Oracle) and fields that in the database may be defined as a String but contain only numbers.  In QlikView it profiled the actual data and interpreted appropriately where as Qlik Sense takes what the DB says it should be.

This causes issues down the line when joining tables that may have an ID field defined as a number in one DB table (or Excel spreadsheet) and the other was defined as a string.

Even saving to QVDs does not solve this issue.  So you have to know your data well and make sure you are converting to Num or Text to ensure consistency when bringing into your data model that are going to join or needs to be presented the same in the interface.

I'll be curious to know if you find the same issue here.