On this page
Qlik
Prepare Qlik inputs for a data estate, collect the relevant dependencies, and verify the scope represented in Understand.
modernAIze supports Qlik as a data estate source platform. The input for analysis is the load script that prepares the application’s data. Collect the text of that script and its dependencies. A dashboard image, data extract, or application container does not substitute for the load logic.
Inputs to prepare
Qlik load scripts in .qvs or .txt files, with the included script source needed for the selected flow. .xlsx workbooks can provide supporting context.
Upload supporting .xlsx workbooks through Files or Folder, separately
from ZIP archives. Keep native source alongside the workbook; see
upload batches.
Native assets and what to collect
| Asset | Material to supply | What it contributes |
|---|---|---|
| Load script | .qvs or .txt script text | LOAD and SELECT processing, joins, resident loads, mappings, and stores |
| Included script | The text files referenced by include directives | Shared initialization and processing |
| Variables and subroutines | Their definitions in the supplied scripts | Parameterized expressions and reusable script behavior |
| Source and connection context | Relevant path and connection references in the script, with approved explanatory context | Identification of external files, QVDs, and database inputs |
| Supporting workbook | .xlsx, where appropriate | Additional metadata or context |
A QVD reference identifies a data dependency. It does not supply the upstream load script that built the QVD. Likewise, QVW/QVF application containers and screenshots of sheets are not substitutes for exported script text. A chart expression that is not part of the supplied material should not be assumed to have been analyzed with the load script.
How to collect the inputs
Use the application’s script editor or the team’s source repository to obtain
the complete load-script text, including all relevant script sections. Save it
as .qvs or .txt and collect any included files from their controlled source
locations. This is manual source collection or a native script export; no
separate modernAIze collection program is needed for this route.
Record what runtime variables and connection aliases mean. Keep upstream QVD production outside the assessed boundary only when that boundary is deliberate.
Prepare the source
- Export or collect the load-script text for the application and revision being assessed.
- Include shared script files, subroutines, and definitions referenced by the selected flow.
- Identify the meaning of variables, paths, and connection references needed to understand the sources without sharing credentials.
- Record external data sources and QVD dependencies whose preparation is outside the package.
Investigate the analysis
Follow data loads and subsequent processing to understand how the final structures are formed. Examine resident processing, joins, mappings, and calculated fields where they contribute to the output. Investigate shared script logic when several reporting areas use the same preparation.
Start with Briefing for the system-level explanation, then use the appropriate Landscape view and available Detail links to investigate the relevant processing. Keep the question tied to the supplied source revision.
Example review question
The following example is synthetic.
For monthly revenue, start with the loads for orders and exchange rates. Locate conversion and monthly aggregation, then investigate whether the rate preparation is shared with other reporting outputs.
Verify the scope
Compare the expected loads and output structures with the represented assets and relationships. A reference to an external QVD identifies an input boundary; it does not include the script that produced that QVD. Obtain the upstream script when its behavior matters to the assessment.