Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Bucharest on Sept 18th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
rbartley
Specialist II
Specialist II

Default app selection not always transferred to server

Hi everyone,

 

We recently upgraded to Qlik Sense November 2018 and I created an app, made a bookmark and then set this to the default selection for the app ("set selections as app default").  This works fine when I open the app.  When I transferred this to my internal QAP server, this was transferred and works fine, but when I migrated this app to our QAP server hosted on a azure cloud server, the default selections were not transferred.  Has anyone experienced anything similar?

Any help will be greatly appreciated.

 

Richard

Labels (1)
1 Solution

Accepted Solutions
rbartley
Specialist II
Specialist II
Author

OK, found the problem.  There seemed to have been some sort of glitch when publishing and replacing the existing app.  When I exported a fresh version and published and replaced again, it worked fine.

View solution in original post

3 Replies
rbartley
Specialist II
Specialist II
Author

When I print the selections out to the console
var objSelections=selState.selections;
console.log('objSelections',objSelections);
I see an array of 2 selections on the internal QAP server and and empty array on our azure cloud server.

rbartley
Specialist II
Specialist II
Author

Some more information that might help:

In my code, I re-write the URL and also read selections from the URL.  When I post the URL including the selections on the internal QAP server, there are no errors, but when I do the same on the azure cloud server, I get a message in the console:

 

WebSocket connection to 'wss://servername/app/fe877f84-f1ff-40d2-9ed2-ea86b0721122/identity/846900927?reloadUri=https%3A%2F%2Fagridata.ec.europa.eu%2Fextensions%2FDashboardTaxud%2FTaxudWeekly.html%3Fselections%3DSECTOR-BEEF%24Unit-Product%2520Weight' failed: Error during WebSocket handshake: Unexpected response code: 403

 

Any ideas?

rbartley
Specialist II
Specialist II
Author

OK, found the problem.  There seemed to have been some sort of glitch when publishing and replacing the existing app.  When I exported a fresh version and published and replaced again, it worked fine.