We have also faced similar issue and one of my team member posted this in forum with heading
We were able to resolve this issue using trim() function.
However we also thought it should be fixed from QS with the next release.
Hope this helps.
Any news about optimized load with Where Exists() from QVDs created with Qlik Sense?
For some reason it stopped working with QVDs created with Qlikview.
Hi Karl, sorry for the delay.
I checked our tracking system and it shows that this has been fixed in our next release, due out this summer.
Let me know if you have any other questions.
Good news, hope it's early summer rather than late summer
I've been working in Qlik Sense Server for a while and have alot of suggestions for improvment. Which is the right way to submit those suggestions?
One perferomances improvement that annoys me right now is that you can't limit a dimension with the first records only top or bottom. When working with straight tables with multiple dimensions and measures it would be very useful, so the user can sort on the different columns but only show the first number of rows, like you could in Qlikview.
Hi Karl - this is great information. I just added the "Ideas" section content to the forumclick this link ->) New to Qlik Sense - let me know if you can "Create an idea" - with the information you described. I will make sure it gets in the proper hands.
Update me as soon as you have done so, or if you have an issue.
It's seems to be fixed in 2.0 Release Preview.
Now it says the load is optimized from a row-based qvd. I think it said columnar in 1.1. I'm posting a question about that.
Does it mean that you now get an optimized load also when using the where exists() function?
I can't find it any where in the release notes though.