Skip to main content

Official Support Articles

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Announcements
CUSTOMERS ONLY: Now accepting customer applications for the 2023 Luminary Program: SUBMIT NOW

Master items disappear from the exported or duplicated copies of sheets (on a published app)

cancel
Showing results for 
Search instead for 
Did you mean: 
Sonja_Bauernfeind
Digital Support
Digital Support

Master items disappear from the exported or duplicated copies of sheets (on a published app)

Master items disappear from exported or duplicated copies of sheets. This includes when a published app is duplicated or exported via the HUB or QMC.    This will result in the duplicated app. showing error(s) and a message  This linked visualization is invalid.  The master visualization has been deleted or the link to it has been broken.
 
Note: The raw application file (.QVF) can be imported directly from the shared content folder and will retain all Master items. 

Master Items please select no more than one client or.png



Environment:

 

Resolution:


Review the security rules configured in the system. A custom security rule designed to allow for Master Items to be added to a published app may exist and needs to be removed. 

For assistance with Security Rules and many more tips and tricks, connect with our active community: Security & Governance 

 

 

 

Cause:


The underlying problem is a security rule that is configured to allow for adding/creating Master Objects in an application after it has been published.   This is what will cause the visualization error when that app is duplicated or exported. 


 

Labels (1)
Comments
jpjust
Specialist
Specialist

Hi - I have a question on this.

As a root admin, I developed an app directly on the stream. The app contains an master visualization.

I have an user with Developer License who has access to this app and when that user opened the app he has the following error.

Then I changed the privilege's to that user as "Root Admin", the moment I gave that developer Root Admin the visualization starts showing up.

Then I removed the privilege's to that user as "Root Admin", then the  developer was still able to see that visualization.

Do you know the reason why at first place even though that developer did have access to that app, he wasn't able to see the visualization? We can't do this exercise of adding / removing as root admin for all the users who wants to see this Master Visualization in that app.

Please advice.

Thanks

 

jpjust_0-1645034056472.png

 

 

jpjust
Specialist
Specialist

Hi Sonja - Did you get a chance to look at this? Do you think I should go-ahead and open a case?

Thanks

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @jpjust 

A case for this would be best!

ThePeterK
Creator
Creator

Was this resolved? We have an ongoing issue with August 2021 P4 that has the same scenario.

jpjust
Specialist
Specialist

I have opened a case with support and they are investigating. will let you know the results.

jeremyseipel
Partner - Contributor III
Partner - Contributor III

@jpjust  has Qlik support been able to provide you with any additional feedback on this? It seems as if this has been a known limitation for a while, based on a quick google.  I have a client running into the same issue and the workaround for importing the base qvf isn't a great option due to the number of user-created content in the app.

It seems like it's faulty logic, yet "working as designed" to some extent, since the creation of master items in published apps follows the same rules as published sheets.  Basically, anything created that isn't in your workstream isn't included when duplicating since it's not a part of the base.  If this was a community sheet, we could just move from community to base using approval.  I don't know of a way to move master items to base, which I think is the problem.

 

It seems like disabling the creation of master items in streams should be disabled by default since nothing good can come from it in the long run.  

Version history
Last update:
‎2021-05-03 03:49 AM
Updated by:
Contributors