Skip to main content
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: 
Anonymous
Not applicable

switching from QlikView 11 to QlikView 12

Hi all,

we try to switch from QlikView 11 to QlikView 12. I found out that there are some minor differences in scripting in version 11 and 12.

Some expressions on the charts which worked correctly in QlikView 11, fail to work in QlikView 12.

I will not right now give you examples because actually there are a lot of them. For us switching form version 11 to 12 means a big revision of all our applications, correcting expressions and variables.

Has someone faced the same problem? Would you recommend to spend lots of time to correct applications so that we could switch to version 12? Will version 12 bring much benefit?

Thank you in advance,

Larisa

1 Solution

Accepted Solutions
rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

Support for QV11 will end in Dec 2017. That is a reason to update to QV12.

-Rob

View solution in original post

6 Replies
rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

Support for QV11 will end in Dec 2017. That is a reason to update to QV12.

-Rob

natebrunner
Contributor III
Contributor III

yikes that's going to come up fast!

sdmech81
Specialist
Specialist

HI,

Hopefully, in general case there should not be any issue.Bcs not only qlik tech any product company from lower to higher version carry forward their existing functionalities.

But higher to lower definitely there are going to be minute problms.

Hope there wont be any ! Do test for few before moving:)

Anonymous
Not applicable
Author

Hi,

I have found a bug in QV12 which is critical for us. It appeares only in QV12.

In the file attached you can see the bug description. I've also attached an example.

Can it be fixed?

Thank you in advance,

Larisa

rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

I recommend reporting this as a bug to QT Support.

-Rob

Anonymous
Not applicable
Author

Thanks