Do Qlik apps work same on QSEoW and Qlik Cloud?

[mgranillo]

Has anyone noticed discrepancies in functionality when migrating an app to the cloud? Does the app function the same after migrating? What testing would be good to ensure the apps are exactly the same between on-prem and the cloud? Do extensions need to be tested? Are there feature discrepancies that have caused confusion for the end-user when switching to the cloud.  That's a lot of questions rolled into one post but I haven't seen much on what happens post migration of content. 

[marksouzacosta · Accepted solution]

Users are usually very comfortable moving from on-prem to Cloud. The user experience change is smooth and slowly the user will start noticing the advantages and the extra features provided by Qlik Cloud platform. The Qlik Sense Application is the same, the features provided by Qlik Cloud that are different, like Alerts, Subscription, Collections, Notes, etc.

Extensions can be a problem, so it is better to test them in advance.

[Lech_Miszkiewicz · Accepted solution]

There are few considerations:

1. One thing which you need to consider is use of reference to Now() or Today() functions as those are based on UTC time which then you may need to convert to your local time using functions like this one: https://help.qlik.com/en-US/qlikview/May2024/Subsystems/Client/Content/QV_QlikView/Scripting/DateAnd...
2. Section Access - If you use section access you may need to review it and potentially change it
3. Size of the apps - that is just to make sure you are not hitting ceiling with Memory usage.

Those would be my top 3

Cheers

Lech

[mgranillo]

Thanks to the both of you for providing some ideas and things to consider

[mgranillo]

I came across an issue with extensions that's worth mentioning. Some of our extensions have broken due to case sensitivity when referencing files.  We had to rename some of the supporting files in the extension so the file gets referenced correctly. We also had an extension just not work at all but it was okay because Qlik has added out-of-the-box features to replace the need for the extension. In our case we were able to replace the extension with a button object.