CopyApp method
Overview
Copies an app that is in the Qlik Sense repository.
The engine copies the app into an app entity that was previously created by the repository. See the QRS API (REST API) help for more information.
Parameters
Name | Description | Type |
---|---|---|
qTargetAppId |
Identifier (GUID) of the app entity in the Qlik Sense repository. The app entity must have been previously created by the repository (via the REST API). This parameter is mandatory. |
String |
qSrcAppId |
Identifier (GUID) of the source app in the Qlik Sense repository. This parameter is mandatory. |
String |
qIds |
Array of QRS identifiers. The list of all the objects in the app to be copied must be given. This list must contain the GUIDs of all these objects. If the list of the QRS identifiers is empty, the method CopyApp copies only the data and the objects necessary to open the app. The objects that were created inside the app are not copied. Script-defined variables are automatically copied when copying an app. To be able to copy variables not created via script, the GUID of each variable must be provided in the list of QRS identifiers. To get the QRS identifiers of the objects in an app, you can use the QRS API. The GET method (from the QRS API) returns the identifiers of the objects in the app. The following example returns the QRS identifiers of all the objects in a specified app: GET /qrs/app/9c3f8634-6191-4a34-a114-a39102058d13 Where 9c3f8634-6191-4a34-a114-a39102058d13 is the identifier of the app. |
Array of string |
Outputs
The following is returned in the output:
Logs
When this method is called, audit activity logs are produced to track the user activity.
In the case of errors, both audit activity logs and system services logs are produced.
The log files are named as follows:
Audit activity log | System service log |
---|---|
<MachineName>_AuditActivity_Engine.txt |
<MachineName>_Service_Engine.txt |
The log files are located in:
%ProgramData%/Qlik/Sense/Log/Engine
Learn more
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!