Skip to main content
Announcements
See what Drew Clarke has to say about the Qlik Talend Cloud launch! READ THE BLOG
cancel
Showing results for 
Search instead for 
Did you mean: 
RoyBatty
Contributor III
Contributor III

Can different users work on (change) the same application?

Hi,

 

We are using Qlik Sense August 2023 Patch 2 - 14.139.6 on Windows Server.

 

In the beginning, we had only one "administrator" user with the "RootAdmin" role, who created various applications.

 

I recently joined the team and a new user was created for me with all possible admin roles: AuditAdmin, ContentAdmin, DeploymentAdmin, HubAdmin, RootAdmin and SecurityAdmin.

 

However, we have the following problem: When I log in to the Hub, I don't see all the applications previously created by the "administrator". Actually, I only see published applications.

 

What we want is the following: The possibility that different users can change the same application. For example, if the administrator created an app called "Test", then I, with my account, can modify it (for example, change the Load Scripts in that "Test" app, or fix the expressions, etc.)

 

Is this possible (if yes, what should we do to achieve that)? (Most likely not, because on this page we found that it says: “Unpublished apps can only be opened if you are the app owner.but we just want to confirm this).

 

If it is not possible, how would you approach this problem (several different people want to work on (change) the same application)?

 

Thanks in advance!

Labels (2)
1 Solution

Accepted Solutions
anderseriksson
Partner - Specialist
Partner - Specialist

Yes you can, only it takes a little work (not complicated).
I consider the published app to be the Master.
Don't keep a copy in my Workplace other than when I'm doing updates to it.

When going to make a change take a fresh copy of the published app from it's stream.
If you are the owner of the app you can do this directly in the Hub by right clicking and duplicate.
Other users would need to make the copy through the Apps section in QMC.
For this reason it is best if the person doing the most changes/updates owns the app.

When duplicated you have a personal copy in your Workplace, do whatever it is you are going to do and verify the changes there.
After that you publish that application again and select replace in the publishing dialog.
Again if you own the published app you can do this directly in Hub, if not you must do it through QMC Apps section.
Note that you must not publish the app during a reload or else the server will overwrite your update and it will get lost.
If different people have copies of the app in their Workplace any changes done to the app after the Workplace copy was made will not migrate to the others copies. Whoever makes the last publish will replace anything others have done with their copy.
That is the reason I always recommend to have the published app as the Master and always work from that.
And always synchronize with your team if you are several people working in the same system.

After publishing the update I usually delete my Workspace copy to avoid that I by accident work from that in the future. If I need to adjust something I make a new copy again.
Also I recommend exporting a copy of the application each time an update is made, that way you always have the possibility to revert any changes by importing an older copy and republish that.
Export has to be done in the QMC Apps section. Also in the QMC Apps section you can change the owner of an application. If you change the owner of an unpublished app you will in effect move that app from one persons Workspace to the other person. Thus you could take control of the other persons work copy. That could be one way of ensuring that only one person at the time is working on the app, but then you must be stringent about no-one making copies of the published app.

View solution in original post

1 Reply
anderseriksson
Partner - Specialist
Partner - Specialist

Yes you can, only it takes a little work (not complicated).
I consider the published app to be the Master.
Don't keep a copy in my Workplace other than when I'm doing updates to it.

When going to make a change take a fresh copy of the published app from it's stream.
If you are the owner of the app you can do this directly in the Hub by right clicking and duplicate.
Other users would need to make the copy through the Apps section in QMC.
For this reason it is best if the person doing the most changes/updates owns the app.

When duplicated you have a personal copy in your Workplace, do whatever it is you are going to do and verify the changes there.
After that you publish that application again and select replace in the publishing dialog.
Again if you own the published app you can do this directly in Hub, if not you must do it through QMC Apps section.
Note that you must not publish the app during a reload or else the server will overwrite your update and it will get lost.
If different people have copies of the app in their Workplace any changes done to the app after the Workplace copy was made will not migrate to the others copies. Whoever makes the last publish will replace anything others have done with their copy.
That is the reason I always recommend to have the published app as the Master and always work from that.
And always synchronize with your team if you are several people working in the same system.

After publishing the update I usually delete my Workspace copy to avoid that I by accident work from that in the future. If I need to adjust something I make a new copy again.
Also I recommend exporting a copy of the application each time an update is made, that way you always have the possibility to revert any changes by importing an older copy and republish that.
Export has to be done in the QMC Apps section. Also in the QMC Apps section you can change the owner of an application. If you change the owner of an unpublished app you will in effect move that app from one persons Workspace to the other person. Thus you could take control of the other persons work copy. That could be one way of ensuring that only one person at the time is working on the app, but then you must be stringent about no-one making copies of the published app.