Output structure and app naming
QV2QS organizes batch output into a directory hierarchy and provides flexible app naming for Qlik Cloud deployment. This topic covers directory layout options, settings recommendations, and naming templates.
Single-project mode also creates a per-project subfolder under the output root. For details, see How conversion works.
Output structure
By default, QV2QS mirrors the source directory hierarchy under the output root. Each project produces a subfolder containing the build output, reports, and logs.
Preserve hierarchy (default)
<outputDir>/
<RelativePath>/
<ProjectName>/
build/
images/
reports/
logs/
Flatten hierarchy (--batchFlatOutput)
<outputDir>/
<ProjectName>/
build/
images/
reports/
logs/
Preserving the hierarchy is useful when the source folder structure reflects organizational groupings (by department, region, or business unit) and the output should mirror that structure. Flattening the hierarchy is useful when the folder structure is not meaningful or when a flat list is easier to work with downstream.
If two projects produce the same output folder name (for example, two projects named Sales in different subdirectories), QV2QS appends _2, _3, and subsequent numbers to avoid collisions.
Settings in batch mode
All conversion settings apply uniformly to every project in the batch. There is no mechanism for per-project overrides. The fixed canvas scale, object scale, size constraints, crop dimensions, layout shrink, background handling, and every other setting are applied identically to every app in the run.
This uniform application has an important practical implication: group similar applications together when running batch conversions. Applications that share similar screen resolutions, background image layouts, and object sizing work well in a single batch. Applications with significantly different layouts or design patterns benefit from separate batch runs with different settings.
Recommended workflow for batch conversion:
- Copy all source QVW and QVF files to a local working folder. Do not run batch conversions against production directories or network shares.
- Identify groups of QlikView applications that share similar layout characteristics (resolution, background images, object density).
- Load a representative application from each group in single-project mode.
- Open Mockup Studio and experiment with fixed canvas, scaling, crop, and size constraint settings until the layout is satisfactory.
- Note the settings that produce the best result for that group.
- Switch to batch mode, point to the folder containing that group, and apply the same settings.
- Repeat for each group of applications.
This approach avoids the common mistake of running a large batch with generic settings and then spending time manually adjusting individual apps afterward. A few minutes of testing in Mockup Studio with a representative sample can save significant effort across a large batch.
Start with a small batch of 3 to 5 applications to validate the settings before scaling up to the full set.
App naming in batch mode
When deploying batch conversions to Qlik Cloud, --qsAppName controls how each app is named:
- Not specified — Each app is named after the project (
<Name>). - Plain text — The value is used as a prefix:
<prefix> - <Name>. - Template with placeholders — The value is treated as a format string.
The following placeholders are available in template strings.
| Placeholder | Description |
|---|---|
{name}
|
Project name |
{rel}
|
Relative directory path from the scan root |
{index}
|
Sequential project number (starting at 1) |
For example, --qsAppName "Migrated {name} ({rel})" produces app names like Migrated Sales (region1/finance).