Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
stevejoyce
Specialist II
Specialist II

Qlik SaaS - Publish and Replace does not include Alternate States

In Qlik SaaS, I noticed when doing a publish & replace (from personal/shared space to managed space) it does not publish new alternate states.  Has anyone else been met with this limitation?

Labels (1)
  • SaaS

2 Solutions

Accepted Solutions
JanJorissen
Support
Support

@stevejoyce 

 

When you did the publish/replace, did you check the "Include data" box at the bottom left of the Publish dialog screen?

 

Alternate States.png

View solution in original post

stevejoyce
Specialist II
Specialist II
Author

Ok will do.

If anyone else hits this issue, I worked around this by using the qlik-cli to create the alternate state directly in the managed space, after publishing from shared space.  Objects automatically restore back to the new alt state that they were set to in the shared space.

 

 

qlik context use $contextName

#create alternate state
$stateName = "<statename>"
$targetAppId = "<managed app id>"

qlik app state add $stateName --app=$targetAppId

 

View solution in original post

5 Replies
JanJorissen
Support
Support

Very interesting item you brought up.

 Was this app published without data by default?
This isn't documented as a limitation, so it is potentially a defect if it is reproducible.

 

 

JanJorissen
Support
Support

@stevejoyce 

 

When you did the publish/replace, did you check the "Include data" box at the bottom left of the Publish dialog screen?

 

Alternate States.png

stevejoyce
Specialist II
Specialist II
Author

@JanJorissen I just checked and when "Including data" alternate state does publish.  Could this be a feature request to publish even if Include data is not checked?  

There are different scenarios on whether we want to include data when publishing.  It most cases the managed space has desired data, shared/personal space may have development type data.

JanJorissen
Support
Support

@stevejoyce 

At this stage, based on the findings, you can open a support case and we can raise a defect against it.

If it turns out to be intentional behavior, then yes, it would be a feature request

 

 

stevejoyce
Specialist II
Specialist II
Author

Ok will do.

If anyone else hits this issue, I worked around this by using the qlik-cli to create the alternate state directly in the managed space, after publishing from shared space.  Objects automatically restore back to the new alt state that they were set to in the shared space.

 

 

qlik context use $contextName

#create alternate state
$stateName = "<statename>"
$targetAppId = "<managed app id>"

qlik app state add $stateName --app=$targetAppId